Geek Answers Handbook

Fatal: remote end unexpectedly hung libcurl = 7 result

I tried almost every answer on Stackoverflow, this is what I see

Counting objects: 134, done. Delta compression using up to 8 threads. Compressing objects: 100% (73/73), done. Writing objects: 100% (79/79), 208.38 KiB | 0 bytes/s, done. Total 79 (delta 37), reused 1 (delta 0) efrror: RPC failed; result=7, HTTP code = 401 atal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date

Important to note: I am using a TFS Git server (maybe this is my problem, LOL)

Things I tried:

  • make sure the url is right using git remote -v (all unloaded)
  • increase global http.postBuffer to 524288000

Interestingly, the error message: RPC failed; result = 7 is interesting in most cases when the stack overflows, the result was either in 50 or in the 20s, the error that I think comes from libcurl. If so, I get CURLE_COULDNT_CONNECT (7) from TFS, which I have no idea why. Has anyone else encountered this error? Or do you know how to solve the problem that I see?

Error codes for Curl are here http://curl.haxx.se/libcurl/c/libcurl-errors.html

+5
source share
2 answers

I do not think this comes from libcurl. Because...

 HTTP code = 401

... means libcurl received an HTTP response and a 401 response code. 401 means that you did not authenticate to access this resource. Invalid username or password or similar.

+2
source

error: RPC error; result = 7, HTTP code = 401

If it was before, it most likely means a temporary network problem.

See: man curl :

7 - Failed to connect to the host.

And HTTP 401 means authentication problems over HTTP transport.

This has improved since Git v1.7.1:

  * Authentication over http transport can now be made lazily, in that the request can first go to a URL without username, get a 401 response and then the client will ask for the username to use.

Please verify your credentials using the ssh command, for example:

 ssh -T -p 443 git@ssh.github.com

If you still get problems, use the SSH protocol (test by: ssh -T git@github.com ).

For further debugging of Git see: How to debug problems with git / git-shell?

0
source

More articles:


All Articles