// git 报错情况: error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.
解决方案:
Note: This solution is not just limited to codecommit but also for other Ubuntu gnults_handshake related issues.
If you have AWS cli installed in ubuntu 14.04 and working with AWS codecommit, you are likely to get “gnutls_handshake() failed” error when you try to clone a repository created in codecommit. Do not worry about it, we have a solution for it.
[Solution] Gnutls_handshake() Failed
Follow the steps given below to rectify this issue.
1. Install build-essential, fakeroot and dpkg-dev using the following command.
1
|
sudo apt-get install build-essential fakeroot dpkg-dev
|
2. Create a directory named git-rectify in the home folder using the following command.
1
|
mkdir ~/git-rectify
|
3. CD in to the get-rectify directory and get the git source files.
1
2
|
cd ~/git-rectify
apt-get source git
|
4. Install all the git dependencies.
1
|
sudo apt-get build-dep git
|
5. Install libcurl with all development files.
1
|
sudo apt-get install libcurl4-openssl-dev
|
6. Unpack all the source packages using the following command.
Note: The name “git_1.9.1-1ubuntu0.1” could vary based on the lastest version. So look in to the directory for the correct version name.
1
|
dpkg-source -x git_1.9.1-1ubuntu0.1
|
7. Cd in to “git_1.9.1” folder and open the control file located inside debian folder (git_1.9.1/debian/control) in a text editor. Replace all the occurences of “libcurl4-gnutls-dev” to “libcurl4-openssl-dev”. Also open “debian/rules” file and delete the line “TEST=test”
8. Build the package files using the following command.
1
|
sudo dpkg-buildpackage -rfakeroot -b
|
9. Install the new git package by executing the folling command.
Note: The package name is based on the system architecture. So have a look at the package name located in “git_1.9.1” (could be a different name for you) folder.
1
|
sudo dpkg -i git_1.7.9.5-1_amd64.deb
|
Thats it! Now you will be able to clone and do all the git related activities to your codecommit service. Lets us know if you are not able to rectify the issue after performing all the above mentioned steps.