Skip to main content

Solved: Fix for Git clone failure due to GnuTLS recv error (-9)


My devstack installation was failing with an error reported by the GnuTLS module as shown below:

$ git clone https://github.com/openstack/horizon.git /opt/stack/horizon --branch master
Cloning into '/opt/stack/horizon'...
remote: Counting objects: 154213, done.
remote: Compressing objects: 100% (11/11), done.
error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

The following Git config changes fixed the issue for me. Am hoping it will be useful for someone out there:

$ git config http.sslVerify false
$ git config --global http.postBuffer 1048576000
Labels:

Comments

Anonymous said…
Getting fatal: not in git directory
August 28, 2017 at 3:24 PM
Unknown said…
try

git config --global http.sslVerify false
October 16, 2017 at 10:52 PM
Anonymous said…
Thanks its working
October 26, 2017 at 1:02 PM
Unknown said…
Yes it working for me also
January 24, 2018 at 4:15 PM
Anonymous said…
Thanks - It did work!!
June 8, 2018 at 8:43 PM
Anonymous said…
it didnt working fr me
June 14, 2018 at 1:34 PM
Anonymous said…
Not working
December 4, 2018 at 1:45 AM
Anonymous said…
it does not work!!!!
January 6, 2020 at 8:17 PM
Unknown said…
it is working Thanks man
August 10, 2020 at 1:29 PM
Anonymous said…
Not working for me .. ubuntu 18.04
December 28, 2020 at 12:02 PM
Adriano Silva said…
Thanks - It did work!!
October 6, 2021 at 8:38 PM
Anonymous said…
Thanks, it's working
January 24, 2022 at 10:08 PM
Anonymous said…
at 99% it gave the early eof error
October 13, 2022 at 5:20 PM
Anonymous said…
getting :awk: fatal: cannot open file `/opt/stack/neutron/setup.cfg' for reading: No such file or directory
August 9, 2023 at 9:43 PM
Post a Comment

Popular posts from this blog

Openstack : Fixing Failed to create network. No tenant network is available for allocation issue.

Assumptions : You are using ML2 plugin configured to use Vlans If you try to create a network for a tenant and it fails with the following error: Error: Failed to create network "Test": 503-{u'NeutronError': {u'message': u'Unable to create the network. No tenant network is available for allocation.', u'type': u'NoNetworkAvailable', u'detail': u''}} The problem can be due to missing configuration in the below files: In /etc/neutron/plugins/ml2/ml2_conf.ini network_vlan_ranges =physnet1:1000:2999 (1000:2999 is the Vlan range allocation) In /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini bridge_mappings = physnet1:br-eth1 (in OVS we map the physical network to the OVS bridge) Note You should have created a bridge br-eth1 manually and mapped it to a port ovs-vsctl add-br br-eth1 ovs-vsctl add-port br-eth1 eth1 Once configuration is done, restart the neutron ovs agent on the compute node(s):
1 comment
Read more

QuickBite: Tap Vs Veth

Linux supports virtual networking via various artifacts such as: Soft Switches (Linux Bridge, OpenVSwitch) Virtual Network Adapters (tun, tap, veth and a few more) In this blog, we will look at the virtual network adapters tap and veth. From a practical view point, both seem to be having the same functionality and its a bit confusing as to where to use what. A quick definition of tap/veth is as follows: TAP A TAP is a simulated interface which exists only in the kernel and has no physical component associated with it. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. When a user space program (in our case the VM) gets attached to the tap interface it gets hold of a file descriptor, reading from which gives it the data being sent on the tap interface. Writing to the file descri
5 comments
Read more