首页
学习
活动
专区
工具
TVP
发布
社区首页 >问答首页 >git推送ssh断开管道错误/ http curl ssl读取错误

git推送ssh断开管道错误/ http curl ssl读取错误
EN

Stack Overflow用户
提问于 2018-04-26 00:24:54
回答 3查看 6.4K关注 0票数 6

我使用的是MAC OS Yosemite,我想将一个17MB的文件推送到我的github-Account。我在ssh和https上都尝试过git,但都不起作用。GIT_TRACE=1 GIT_CURL_VERBOSE=1 git push -u origin master作为最后6行返回:

代码语言:javascript
复制
Counting objects: 243, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (118/118), done.
packet_write_wait: Connection to 192.30.253.113 port 22: Broken pipe
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

为了寻找问题的解决方案,我开始在各种配置脚本中设置TCPKeepAlive、ServerAlive、ClientAlive参数,最后以: in ~/.ssh/config结尾

代码语言:javascript
复制
Host github.com
   PubKeyAuthentication yes
   IdentityFile ~/.ssh/id_rsa.pub
   ServerAliveInterval 300
   TCPKeepAlive no
   #ServerAliveCountMax 2400

/etc/sshd_config

代码语言:javascript
复制
#   $OpenBSD: sshd_config,v 1.89 2013/02/06 00:20:42 dtucker Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options override the
# default value.

# See sshd_config(5) for details on setting the Port and Listen values on Mac OS X
#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# The default requires explicit activation of protocol 1
#Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
#PubkeyAuthentication yes

# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
AuthorizedKeysFile  .ssh/authorized_keys

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords both PasswordAuthentication and
# ChallengeResponseAuthentication must be set to "no".
#PasswordAuthentication no
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

# Set this to 'yes' to enable PAM authentication, account processing, 
# and session processing. If this is enabled, PAM authentication will 
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
# Also, PAM will deny null passwords by default.  If you need to allow
# null passwords, add the " nullok" option to the end of the
# securityserver.so line in /etc/pam.d/sshd.
#UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#XauthLocation xauth # Default is to search $PATH (set by launchd(8)).  It is recommended that a full path be provided.
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
TCPKeepAlive yes
#UseLogin no
UsePrivilegeSeparation sandbox      # Default for new installations.
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

# pass locale information
AcceptEnv LANG LC_*

# no default banner path
#Banner none

# override default of no subsystems
Subsystem   sftp    /usr/libexec/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#   X11Forwarding no
#   AllowTcpForwarding no
#   ForceCommand cvs server

# XAuthLocation added by XQuartz (http://xquartz.macosforge.org)
XAuthLocation /opt/X11/bin/xauth

Host *
ClientAliveCountMax 4
ClientAliveInterval 600

尽管如此,将ClientAlive参数添加到/etc/sshd_config并将ServerAlive参数添加到~/.ssh/config并不能解决我的问题。我使用以下命令重新启动了sshd服务:

代码语言:javascript
复制
sudo launchctl unload /System/Library/LaunchDaemons/ssh.plist

sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist

ssh -T git@github.com返回:您已成功通过身份验证,但GitHub不提供外壳访问。

因此,然后我尝试通过https更改为git:

代码语言:javascript
复制
git remote set-url origin https://github.com/<my username>/<my repo>

并将postBuffer大小设置为30MB:

代码语言:javascript
复制
git config --global http.postBuffer 30M

然后GIT_TRACE=1 GIT_CURL_VERBOSE=1 git push -u源站返回:

代码语言:javascript
复制
...
* Couldn't find host github.com in the .netrc file; using defaults
* NTLM-proxy picked AND auth done set, clear picked!
* Hostname github.com was found in DNS cache
*   Trying 192.30.253.113...
* Connected to github.com (192.30.253.113) port 443 (#1)
* SSL re-using session ID
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
* Server certificate: github.com
* Server certificate: DigiCert SHA2 Extended Validation Server CA
* Server certificate: DigiCert High Assurance EV Root CA
...
Host: github.com
Authorization: Basic Z3JvMW06YSooYitjKT1hKmIrYSpjTUc5MQ==
User-Agent: git/2.14.2
Accept-Encoding: gzip
Content-Type: application/x-git-receive-pack-request
Accept: application/x-git-receive-pack-result
Content-Length: 57811865

* SSLRead() return error -9820
* Closing connection 1
error: RPC failed; curl 56 SSLRead() return error -9820
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

因此,我不知道如何通过ssh或https上传我的文件。因此,如果有人能建议我怎样才能成功地将我的文件上传到Github,我会很高兴的。如果有人能告诉我问题的根本原因和解决方案,那就更好了。谢谢!

EN

回答 3

Stack Overflow用户

回答已采纳

发布于 2018-04-27 00:12:27

事实上,正如@VonC指出的那样,推送ssh的packet_write_issue和通过https推送的SSLRead() return error都是由糟糕的互联网连接造成的。在我的例子中,我通过将网线直接插入路由器来改善网络连接,而不是通过我们家里的墙壁连接。最后,这允许我将我的文件上传到github.com。

票数 3
EN

Stack Overflow用户

发布于 2018-04-26 04:44:40

首先,sshd用于在服务器端配置ssh守护进程,而您不是(您是一个客户端)

其次,您的配置不应该使用github.com作为主机条目。

使用自定义密钥,如mygithub。

并在该部分中添加User gitHostName github.com

然后,您的~/.ssh/config应为:

代码语言:javascript
复制
Host mygithub
   HostName github.com
   PubKeyAuthentication yes
   IdentityFile ~/.ssh/id_rsa
   ServerAliveInterval 300
   TCPKeepAlive no
   #ServerAliveCountMax 2400
   User git

然后更改您的URL:

代码语言:javascript
复制
git remote set-url origin mygithub:MyAccount/MyRepo.git

再试一次。

如果问题仍然存在,作为mentioned here,这是一个网络问题,并且操作员确认。

票数 4
EN

Stack Overflow用户

发布于 2019-08-30 13:46:02

当我连接到办公室互联网时,也遇到了同样的问题。在几次尝试之后,切换到个人互联网并执行"git推送“。这就像预期的一样。

如果您在将代码推送到git时注意到以下错误,请尝试切换网络。

代码语言:javascript
复制
packet_write_wait: Connection to 0.0.0.0 port 22: Broken pipe
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/50027084

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档