当前位置: 首页 > 知识库问答 >
问题:

nginx connect()失败(110:连接超时)

宇文温文
2023-03-14

我知道,这个问题已经在不同的论坛上被问了很多次,但我仍然无法找到一个解决方案,这解决了我的问题...情况:我们在服务器上有一个nginx、php-fpm和MySQL堆栈。服务器位于nginx反向代理之后。问题是,在上游服务器上有干净的错误日志,而在反向代理上,我得到了多条消息

连接到>上游,客户端:+++++++++++,服务器:domain.com,请求:“Get>/files/imagecache/frontbullet/blog1/dknasda.jpg http/1.1”,上游:>“http://192.168.158.142:80/files/imagecache/frontbullet/blog1/dknasda.jpg>”,主机:“somedomain.com”,连接失败(110:连接超时)

    user ++++;
worker_processes 3;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

events {
    worker_connections 1024;
    use epoll;
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                  '$status $body_bytes_sent "$http_referer" '
                  '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   60s; #keeps the connection open with the client; MS default is 60.
    types_hash_max_size 2048;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    gzip on; 
    gzip_http_version 1.1; 
    gzip_vary on; 
    gzip_comp_level 6; 
    gzip_proxied any; 
    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_buffers 16 8k; 
    gzip_disable "MSIE [1-6]\.(?!.*SV1)";

    upstream main_upstream {

        server 192.168.158.142:80 max_fails=3  fail_timeout=60s;  #       New Server. Sent to 192.168.90
#   server 192.168.158.143:80;   #       HSB
    keepalive 32;
    }

server {
    listen       80 default_server;
    listen       [::]:80 default_server;
    server_name  domain.com;

    location / {
        proxy_buffers 32 32k;
        proxy_buffer_size 64k;
        proxy_pass http://main_upstream;
        proxy_set_header    Host $host;
        proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header    X-Forwarded-Proto $scheme;
        proxy_set_header    X-Forwarded-By $server_addr:$server_port;
            proxy_set_header    X-Real-IP $remote_addr;
        proxy_connect_timeout       600s;
        proxy_send_timeout          600s;
        proxy_read_timeout          600s;
        send_timeout                600s;
        proxy_http_version 1.1;
        proxy_set_header Connection "";
        client_max_body_size                            32M;
        client_body_buffer_size                         512k;
    }
    error_page 404 /404.html;
        location = /40x.html {
    }

    error_page 500 502 503 504 /50x.html;
        location = /50x.html {
    }
}

提前谢谢你,托多

共有1个答案

孔飞翔
2023-03-14

终于找到了原因,现在已经干净了几个小时了。原来有2个重叠的问题。第一个是内核在队列满后删除请求。这里有一个关于调整内核linux内核参数的很好的手册--https://www.nginx.com/blog/tuning-nginx/

问题开始后,我们将站点迁移到一个新的服务器上,并使用DHCP来分配IP地址--这是一个很大的错误。大约每隔一个小时,dhcp就会重新启动网络接口。检查整个系统日志,我注意到网络接口的IP是定期重新分配的。这些间隔与日志中错误的爆发相吻合。因此,解决方案是回到静态IPS。

 类似资料: