Git“efrror:RPC失败;结果= 55,HTTP代码= 0“推动 [英] Git "efrror: RPC failed; result=55, HTTP code = 0" on push

查看:407
本文介绍了Git“efrror:RPC失败;结果= 55,HTTP代码= 0“推动的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经花了整整一天的时间,并且真的可以用一些帮助。当我尝试推送相对较大的提交时,

 写入对象:100%(21/21),908.07 KiB | 0字节/秒,完成。 
总计21(增量17),重用0(增量0)

git需要一个非常长时间回应,然后给出

 efrror:RPC failed; result = 55,HTTP code = 0 
atal :远程终端意外挂断
致命:远程终端意外挂断
一切最新

我已经搜索了这个错误代码,最可能的解决方案似乎是扩大了缓冲区大小

  git config http.postBuffer 524288000 

我试过这个解决方案没有成功。在VonC的建议后,我尝试从http切换到ssh。从ssh开始,我在同一时间得到了很长时间的挂断。最终,出现以下错误消息:

 从远程主机读取github.com:连接重置由同级
致命:The远程终端意外挂断
致命:远程终端意外挂断

这可能是路由器问题?我尝试从另一台不同网络上的另一台计算机上推送,并且能够成功完成。



我在Linux主机上远离我的Linux机器并使用可怕的poshGit Windows PowerShell界面。



任何想法

解决方案

您可以按照调试建议从到位桶文章


特别是,'结果= 55 '部分。

这是来自 libcurl ,这是与Git进行http通信时使用的底层库。从libcurl文档中,结果代码55表示:



  CURLE_SEND_ERROR(55)
发送网络数据失败。



原因




<这可能是由各种网络相关问题或甚至Bitbucket服务本身引起的。这基本上意味着连接意外中断。需要检查的事情是尝试从任何公司防火墙或代理之外的干净网络上的机器推送。检查所有代理服务器以确保它们正确地移动SSL数据并完全允许完成。



为帮助解决此问题,请尝试使用以下命令运行推送:



  GIT_CURL_VERBOSE = 1 GIT中推



解决方法




如果在检查所有连接和代理配置之后,连接仍然无法连续进行,请报告以上信息以支持。然后切换到SSH 。我们有一个指导,得到它设置为的Git在用于建立SSH Git的。如果您遇到任何配置问题而设置SSH,请参阅我们的 SSH故障排除指南



I've spent all day on this one and could really use some help. When I try to push a relatively large commit,

Writing objects: 100% (21/21), 908.07 KiB | 0 bytes/s, done.
Total 21 (delta 17), reused 0 (delta 0)

git takes a very long time to respond and then gives

"efrror: RPC failed; result=55, HTTP code = 0 
atal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date"

I have searched this error code, and the most likely solution seems to be extending the buffer size

git config http.postBuffer 524288000

I have tried this solution with no success. After VonC's suggestion, I tried switching from http to ssh. From ssh, I get a long hang up at the same point. Eventually, the following error message appears

Read from remote host github.com: Connection reset by peer
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

Could this be a router issue? I have tried pushing from a different computer on a different network and am able to do so successfully.

I am away from my Linux machine on a Windows host and using the terrible poshGit Windows PowerShell interface.

Any ideas??

解决方案

You can follow the debug advices from the BitBucket article:

Specifically, the 'result=55' portion.
This is the error code coming from libcurl, the underlying library used in http communications with Git. From the libcurl documentation, a result code of 55 means:

CURLE_SEND_ERROR (55)
    Failed sending network data.

Cause

This can be caused by a variety of network related issues or even the Bitbucket service itself. It essentially means that the connection was dropped unexpectedly. Things to check would be to attempt the push from a machine on a 'clean' network outside of any corporate firewalls or proxies. Check all proxy servers to ensure they are properly moving SSL data and are fully permitted to complete.

To help troubleshoot this issue, try running the push with the command

GIT_CURL_VERBOSE=1 git push

Workaround

If after checking all connections and proxy configurations the connection still fails consistently, please report the information above to support. Then switch to SSH. We have a guide to getting it setup for Git at Set up SSH for Git. If you should run into any configuration issues while setting up SSH, please refer to our SSH Troubleshooting guide.

这篇关于Git“efrror:RPC失败;结果= 55,HTTP代码= 0“推动的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆