Every time you take the code from GitHub pull, always being given up to be successful, it is really annoying. Try the following solutions should be able to help you.
[A] error:
Cloning into '/opt/exploit-database'...
remote: Counting objects: 106517, done.
remote: Compressing objects: 100% (45/45), done.
error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 60
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
【problem causes】
Since large files typically caused by or submitted to pulling failure, postBuffer curl default value is too small, increasing the cache configuration like
【Solution】
git config --global http.postBuffer 1048576000
Error [two]
Git error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
【problem causes】
For errno 54 error, often http or https protocols are not properly submitted. Must instead ssh way to submit code. That is, the use of public and private key must be a way to verify the account, and submit the code.
【Solution】
Configuring SSH key in the GitHub
If no local ssh key, then ssh into Mr. information
> ssh-keygen -t rsa -C "邮箱"
You can then get id_rsa and id_rsa.pub two files in ~ / .ssh directory under the prompts continuous carriage, id_rsa.pub file storage is that we want to use key
View id_rsa.pub information, and copy
cat ~/.ssh/id_rsa.pub
Log in to GitHub, in the Accounting settingsselection SSH key, clickAdd SSH key
After configuration, test whether the configuration
> ssh -T [email protected]
Hi username! You’ve successfully authenticated, but GitHub does not provide shell access.
See the information above, it means the SSH key configuration successful.
[Three] Error:
Cloning into '/opt/exploit-database'...
remote: Counting objects: 106517, done.
remote: Compressing objects: 100% (45/45), done.
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
【problem causes】
Might find on the Internet have tried a lot of ways, was about to despair, or not. The company may be relatively slow network connection GitHub, download time always lead to pull the timeout failure.
【problem solved】
Increase the minimum speed connection time
git config --global http.lowSpeedLimit 0
git config --global http.lowSpeedTime 999999
Scan code concerns, learn more
