curl(56) Recv failure: Connection reset by peer

遇到一个奇葩问题，访问我们自己的网站接口，有的网段访问正常，有的网段访问，有时正常有时报 curl(56) Recv failure: Connection reset by peer 而且同一个网段访问也是这样。
在本机上访问一直都是报这样的错误。

服务器的防火墙关闭了，ping没有丢包，telnet 端口正常，机器也重启了，还是不行，实在找不到解决办法，只能要求换机器了。

下面是用tcpdump抓包

# tcpdump -i bond0 host ip地址

###正常数据包

listening on bond0, link-type EN10MB (Ethernet), capture size 262144 bytes
10:20:06.251835 IP shpaas-container-c2-008.14492 > 10.7.34.137.http: Flags [S], seq 3133217419, win 29200, options [mss 1460,sackOK,TS val 2884918391 ecr 0,nop,wscale 9], length 0
10:20:06.254947 IP 10.7.34.137.http > shpaas-container-c2-008.14492: Flags [S.], seq 400517749, ack 3133217420, win 4380, options [mss 1460,nop,nop,TS val 8530366 ecr 2884918391,sackOK,eol], length 0
10:20:06.254998 IP shpaas-container-c2-008.14492 > 10.7.34.137.http: Flags [.], ack 1, win 29200, options [nop,nop,TS val 2884918395 ecr 8530366], length 0
10:20:06.255064 IP shpaas-container-c2-008.14492 > 10.7.34.137.http: Flags [P.], seq 1:108, ack 1, win 29200, options [nop,nop,TS val 2884918395 ecr 8530366], length 107: HTTP: HEAD /openApi/zwdtcert/login/login.do HTTP/1.1
10:20:06.257916 IP 10.7.34.137.http > shpaas-container-c2-008.14492: Flags [.], ack 108, win 4487, options [nop,nop,TS val 8530369 ecr 2884918395], length 0
10:20:06.274944 IP 10.7.34.137.http > shpaas-container-c2-008.14492: Flags [P.], seq 1:161, ack 108, win 4487, options [nop,nop,TS val 8530386 ecr 2884918395], length 160: HTTP: HTTP/1.1 401 Unauthorized
10:20:06.274973 IP shpaas-container-c2-008.14492 > 10.7.34.137.http: Flags [.], ack 161, win 30016, options [nop,nop,TS val 2884918415 ecr 8530386], length 0
10:20:06.275207 IP shpaas-container-c2-008.14492 > 10.7.34.137.http: Flags [F.], seq 108, ack 161, win 30016, options [nop,nop,TS val 2884918415 ecr 8530386], length 0
10:20:06.278058 IP 10.7.34.137.http > shpaas-container-c2-008.14492: Flags [.], ack 109, win 4487, options [nop,nop,TS val 8530389 ecr 2884918415], length 0
10:20:06.278783 IP 10.7.34.137.http > shpaas-container-c2-008.14492: Flags [F.], seq 161, ack 109, win 4487, options [nop,nop,TS val 8530390 ecr 2884918415], length 0
10:20:06.278817 IP shpaas-container-c2-008.14492 > 10.7.34.137.http: Flags [.], ack 162, win 30016, options [nop,nop,TS val 2884918418 ecr 8530390], length 0
10:20:22.977354 IP shpaas-container-c2-008.17868 > 10.7.34.137.http: Flags [S], seq 3278439648, win 29200, options [mss 1460,sackOK,TS val 2884935117 ecr 0,nop,wscale 9], length 0
10:20:22.980484 IP 10.7.34.137.http > shpaas-container-c2-008.17868: Flags [S.], seq 763138052, ack 3278439649, win 4380, options [mss 1460,nop,nop,TS val 8547091 ecr 2884935117,sackOK,eol], length 0
10:20:22.980543 IP shpaas-container-c2-008.17868 > 10.7.34.137.http: Flags [.], ack 1, win 29200, options [nop,nop,TS val 2884935120 ecr 8547091], length 0
10:20:22.980656 IP shpaas-container-c2-008.17868 > 10.7.34.137.http: Flags [P.], seq 1:108, ack 1, win 29200, options [nop,nop,TS val 2884935120 ecr 8547091], length 107: HTTP: HEAD /openApi/zwdtcert/login/login.do HTTP/1.1
10:20:22.983543 IP 10.7.34.137.http > shpaas-container-c2-008.17868: Flags [.], ack 108, win 4487, options [nop,nop,TS val 8547094 ecr 2884935120], length 0
10:20:23.000406 IP 10.7.34.137.http > shpaas-container-c2-008.17868: Flags [P.], seq 1:161, ack 108, win 4487, options [nop,nop,TS val 8547111 ecr 2884935120], length 160: HTTP: HTTP/1.1 401 Unauthorized
10:20:23.000436 IP shpaas-container-c2-008.17868 > 10.7.34.137.http: Flags [.], ack 161, win 30016, options [nop,nop,TS val 2884935140 ecr 8547111], length 0
10:20:23.000708 IP shpaas-container-c2-008.17868 > 10.7.34.137.http: Flags [F.], seq 108, ack 161, win 30016, options [nop,nop,TS val 2884935140 ecr 8547111], length 0
10:20:23.003547 IP 10.7.34.137.http > shpaas-container-c2-008.17868: Flags [.], ack 109, win 4487, options [nop,nop,TS val 8547114 ecr 2884935140], length 0
10:20:23.003793 IP 10.7.34.137.http > shpaas-container-c2-008.17868: Flags [F.], seq 161, ack 109, win 4487, options [nop,nop,TS val 8547114 ecr 2884935140], length 0
10:20:23.003815 IP shpaas-container-c2-008.17868 > 10.7.34.137.http: Flags [.], ack 162, win 30016, options [nop,nop,TS val 2884935143 ecr 8547114], length 0

###异常数据包
10:21:27.336118 IP shpaas-container-c2-008.6987 > 10.7.34.137.http: Flags [S], seq 2469240435, win 29200, options [mss 1460,sackOK,TS val 2884999475 ecr 0,nop,wscale 9], length 0
10:21:27.339227 IP 10.7.34.137.http > shpaas-container-c2-008.6987: Flags [S.], seq 4274905813, ack 2469240436, win 4380, options [mss 1460,nop,nop,TS val 8611447 ecr 2884999475,sackOK,eol], length 0
10:21:27.339280 IP shpaas-container-c2-008.6987 > 10.7.34.137.http: Flags [.], ack 1, win 29200, options [nop,nop,TS val 2884999479 ecr 8611447], length 0
10:21:27.339389 IP shpaas-container-c2-008.6987 > 10.7.34.137.http: Flags [P.], seq 1:108, ack 1, win 29200, options [nop,nop,TS val 2884999479 ecr 8611447], length 107: HTTP: HEAD /openApi/zwdtcert/login/login.do HTTP/1.1
10:21:27.342223 IP 10.7.34.137.http > shpaas-container-c2-008.6987: Flags [.], ack 108, win 4487, options [nop,nop,TS val 8611450 ecr 2884999479], length 0
10:21:31.342331 IP 10.7.34.137.http > shpaas-container-c2-008.6987: Flags [R.], seq 1, ack 108, win 4487, length 0

原文地址：https://www.cnblogs.com/fan-gx/p/11742948.html

时间： 2025-01-13 21:02:53

curl(56) Recv failure: Connection reset by peer的相关文章

CentOS7 yum的一次报错" 14: curl#56 - "Recv failure: Connection reset by peer" "

1.故障现象 [[email protected] src]# yum update Loaded plugins: fastestmirror, langpacks Could not retrieve mirrorlist 7&arch=x86_64&repo=os&infra=stock error was 14: curl#56 - "Recv failure: Connection reset by peer" One of the configu

文件上传时报Recv failure: Connection reset by peer异常解决

以前上传文件时报这个异常没这么在意,这次网络不好时总是报这个异常,导致文件上传失败,故特意说明一下,报个异常的原因还是很多的,今日只针对我当前遇上的问题进行记录一下. 背景:平时网络好的时候,我开启线程的上传和下载都没问题,网络慢的时候就出来这个异常 Recv failure: Connection reset by peer . 异常的原因有两点:1.网络非常慢时易导致该异常:2.线程多次重复请求网络服务造成的异常,因为上次启用的线程还没断开,所以该服务一直存在,导致再次进行上传请求时异常.

recv() failed (104: Connection reset by peer) while reading response header from upstream

场景: 为了得到用户在线等信息,在客户端做了个ajax轮训: 于是问题就来了, 日志文件 [[email protected] web]# tail -f /data/log/nginx_error.log 2017/06/16 19:20:28 [error] 230555#0: *10228041 recv() failed (104: Connection reset by peer) while reading response header from upstream,client:

nginx错误分析 `104: Connection reset by peer`

故障描述应用从虚拟机环境迁移到kubernetes环境中,有些应用不定时出现请求失败的情况,且应用没有记录任何日志,而在NGINX中记录502错误.我们查看了之前虚拟机中的访问情况,没有发现该问题. 基础信息 # 请求流程 client --> nginx(nginx-ingress-controller) --> tomcat(容器) # nginx版本 $ nginx -V nginx version: nginx/1.15.5 built by gcc 8.2.0 (Debian 8.

Netty 中 IOException: Connection reset by peer 与 java.nio.channels.ClosedChannelException: null

最近发现系统中出现了很多 IOException: Connection reset by peer 与 ClosedChannelException: null 深入看了看代码, 做了些测试, 发现 Connection reset 会在客户端不知道 channel 被关闭的情况下, 触发了 eventloop 的 unsafe.read() 操作抛出而 ClosedChannelException 一般是由 Netty 主动抛出的, 在 AbstractChannel 以及 SSLHand

CentOS7使用ssh不能登录，报错：Read from socket failed: Connection reset by peer

使用xshell登录CentOS7,不能登录,使用另外一台Linux主机,telent 22端口是同的,ssh连接报以下错误: Read from socket failed: Connection reset by peer 查看不能登录主机的日志 # cat /var/log/messages Dec 15 19:38:27 localhost dbus-daemon: dbus[874]: [system] Successfully activated service 'org.freed

ssh远程报错ssh_exchange_identification: read: Connection reset by peer

ssh远程登录报错: [[email protected] ~]$ ssh 198.44.241.34 ssh_exchange_identification: read: Connection reset by peer 初步原因锁定: 1-服务器防火墙限定, 2-是否达到ssh的最大连接数,超过之后会服务器端会拒绝新的连接,直到有新的连接释放出来 3-/etc/hosts.allow和/etc/hosts.deny配置文件限定ip登录解决方案: 1 firewall-cmd --l

Connection reset by peer 的常见原因：

Connection reset by peer的常见原因: 1)服务器的并发连接数超过了其承载量,服务器会将其中一些连接关闭: 如果知道实际连接服务器的并发客户数没有超过服务器的承载量,则有可能是中了病毒或者木马,引起网络流量异常.可以使用netstat -an查看网络连接情况. 2)客户关掉了浏览器,而服务器还在给客户端发送数据: 3)浏览器端按了Stop: 这两种情况一般不会影响服务器.但是如果对异常信息没有特别处理,有可能在服务器的日志文件中,重复出现该异常,造成服务器日志文件过大,影响

ssh_exchange_identification: read: Connection reset by peer

连接SSH报错:ssh_exchange_identification: read: Connection reset by peer 查看没有使用防火墙,怀疑是在hosts.deny中设置了拦截果不其然将这一行注释,默念三声“信春哥得永生”后,问题恢复了,so easy