php Nginx 错误 recv() failed (104: Connection reset by peer)
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/25122527/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Nginx error recv() failed (104: Connection reset by peer)
提问by Shupyrg
Since a couple of days ago, I'm getting some errors on my server. I use CentOS 6.5 with Parallels 12.0.18, Apache server to serve dynamic content and Nginx as proxy to serve static content.
从几天前开始，我的服务器出现了一些错误。我使用 CentOS 6.5 和 Parallels 12.0.18、Apache 服务器来提供动态内容和 Nginx 作为代理来提供静态内容。
At first, I was getting the following error:
起初，我收到以下错误：
[error] 29951#0: *5138862 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 89.7.24.108, server: , request: "GET /page/2/ HTTP/1.1", upstream: "http://ip:7080/page/2/", host: "domain.es", referrer: "http://domain.es/"
Then, I changed some configuration, like increasing MaxClients on my "httpd.conf" file and this lines to my /etc/nginx/conf.d/timeout.conf file:
然后，我更改了一些配置，例如在我的“httpd.conf”文件上增加 MaxClients，并将这一行添加到我的 /etc/nginx/conf.d/timeout.conf 文件中：
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;
It all seemed to be working fine until I got the same errors again, along with a new one:
一切似乎都运行良好，直到我再次遇到相同的错误以及一个新错误：
[error] 15228#0: *130292 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 89.130.25.154, server: domain.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:7080/", host: "domain.com"
I have two different websites on the same server. That's why you see two different hosts in there.
我在同一台服务器上有两个不同的网站。这就是为什么你会在那里看到两个不同的主机。
Here's the problem: when I got these errors, I got a "502 Bad Gateway" and the server becomes so slow that I can't even log in using the SSH terminal. I can only fix it temporally by resetting the httpd service.
问题是：当我收到这些错误时，我收到了“502 Bad Gateway”，服务器变得很慢，我什至无法使用 SSH 终端登录。我只能通过重置 httpd 服务来暂时修复它。
I know there are other topics similar to this one, but all I found were problems with PHP-FPM, which I don't use.
我知道还有其他类似的主题，但我发现的都是 PHP-FPM 的问题，我不使用它。
Here's my Nginx configuration file: user nginx; worker_processes 16;
这是我的 Nginx 配置文件：用户 nginx；worker_processes 16;
error_log /var/log/nginx/error.log;
events {
worker_connections 1024;
}
http {
server_names_hash_max_size 2048;
server_names_hash_bucket_size 512;
server_tokens off;
include mime.types;
default_type application/octet-stream;
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 10;
# Gzip on
gzip on;
gzip_vary on;
gzip_min_length 10240;
gzip_proxied expired no-cache no-store private auth;
gzip_buffers 4 32k;
gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript application/javascript text/x-js;
gzip_disable "MSIE [1-6]\.";
# Other configurations
ignore_invalid_headers on;
client_max_body_size 8m;
client_header_timeout 3m;
client_body_timeout 3m;
#send_timeout 3m;
connection_pool_size 256;
client_header_buffer_size 4k;
large_client_header_buffers 4 32k;
request_pool_size 4k;
output_buffers 4 32k;
postpone_output 1460;
# Cache most accessed static files
open_file_cache max=10000 inactive=10m;
open_file_cache_valid 2m;
open_file_cache_min_uses 1;
open_file_cache_errors on;
# virtual hosts includes
include "/etc/nginx/conf.d/*.conf";
}
Here's my Nginx vhost file: server { listen ip:80 default_server;
这是我的 Nginx 虚拟主机文件： server { listen ip:80 default_server;
server_name domain.es;
server_name www.domain.es;
server_name ipv4.domain.es;
client_max_body_size 128m;
root "/var/www/vhosts/domain.es/httpdocs";
access_log "/var/www/vhosts/system/domain.es/logs/proxy_access_log";
error_log "/var/www/vhosts/system/domain.es/logs/proxy_error_log";
if ($host ~* ^www.domain.es$) {
rewrite ^(.*)$ http://domain.es permanent;
}
location / {
proxy_pass http://82.194.74.41:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
access_log off;
}
location @fallback {
proxy_pass http://ip:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
access_log off;
}
location ~ ^/plesk-stat/ {
proxy_pass http://ip:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
access_log off;
}
location ~ ^/(.*\.(ac3|avi|bmp|bz2|css|cue|dat|doc|docx|dts|exe|flv|gif|gz|htm|html|ico|img|iso|jpeg|jpg|js|mkv|mp3|mp4|mpeg|mpg|ogg|pdf|png|ppt|pptx|qt|rar|rm|swf|tar|tgz|txt|wav|xls|xlsx|zip))$ {
access_log off;
expires 7d;
add_header Cache-Control public;
try_files $uri @fallback;
}
include "/var/www/vhosts/system/domain.es/conf/vhost_nginx.conf";
}
And some of the configuration vars I use with Apache (httpd.conf):
以及我与 Apache (httpd.conf) 一起使用的一些配置变量：
<IfModule prefork.c>
StartServers 14
MinSpareServers 8
MaxSpareServers 14
ServerLimit 1000
MaxClients 1000
MaxRequestsPerChild 2000
</IfModule>
Thank you very much in advance!
非常感谢您提前！
回答by Yang Yuan
It seems your Apache is more busy than your Nginx. When Nginx get some requests but Apache can't handle, you get '502 Bad Gateway', which meas Apache refused to work for Nginx.
看起来你的 Apache 比你的 Nginx 更忙。当 Nginx 收到一些请求但 Apache 无法处理时，您会收到“502 Bad Gateway”，这意味着 Apache 拒绝为 Nginx 工作。
Try decrease 'worker_connections' and 'worker_processes' in Nginx and increase 'MaxClients', 'ServerLimit'
尝试减少 Nginx 中的“worker_connections”和“worker_processes”并增加“MaxClients”、“ServerLimit”
Make sure worker_connections * worker_processes < MaxClients < ServerLimit
确保 worker_connections * worker_processes < MaxClients < ServerLimit
回答by youly
In my case, a php extension is missing, after I turned it off, it recovered! Check /var/log/messagesto see if there is any segfault.
就我而言，缺少一个 php 扩展，在我将其关闭后，它恢复了！检查/var/log/messages是否有segfault。
回答by shonky linux user
In a case I saw recently this error was being logged for 95% of requests but both the web server and the apps server were almost idle with only a few connections open. The other 5% were successful.
在我最近看到的一个案例中，95% 的请求都记录了此错误，但 Web 服务器和应用程序服务器几乎都处于空闲状态，只有几个连接打开。其他 5% 是成功的。
It turned out that our friendly networking colleagues had configured an IPS device between the web and apps server and it started clawing back and dropping connections when traffic increased because it thought there was a brute force attack happening. A false-positive. So nothing to do with Nginx or Apache, but reconfiguring the IPS fixed the issue.
事实证明，我们友好的网络同事在 Web 和应用程序服务器之间配置了一个 IPS 设备，当流量增加时，它开始收回并断开连接，因为它认为发生了蛮力攻击。一个假阳性。因此与 Nginx 或 Apache 无关，但重新配置 IPS 解决了该问题。
