在Nginx错误日志中,有大量的下列信息:
Upstream timed out (110: Connection timed out) while reading response header from upstream文章源自运维生存时间-https://www.ttlsa.com/nginx/nginx-upstream-timed-out-110-connection-timed-out/
这种情况主要在厦门两种情况下发生:文章源自运维生存时间-https://www.ttlsa.com/nginx/nginx-upstream-timed-out-110-connection-timed-out/
1. nginx proxy
需要适当的调整proxy_read_timeout值。文章源自运维生存时间-https://www.ttlsa.com/nginx/nginx-upstream-timed-out-110-connection-timed-out/
location / { ... proxy_read_timeout 150; ... }
2. Nginx作为php-fpm等等其他的有上游服务
在这种情况下,适当的调整fastcgi_read_timeout选项值文章源自运维生存时间-https://www.ttlsa.com/nginx/nginx-upstream-timed-out-110-connection-timed-out/
location ~* .php$ { include fastcgi_params; fastcgi_index index.php; fastcgi_read_timeout 150; fastcgi_pass 127.0.0.1:9000; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; }文章源自运维生存时间-https://www.ttlsa.com/nginx/nginx-upstream-timed-out-110-connection-timed-out/文章源自运维生存时间-https://www.ttlsa.com/nginx/nginx-upstream-timed-out-110-connection-timed-out/
我的微信
微信公众号
扫一扫关注运维生存时间公众号,获取最新技术文章~
1F
什么时候能出一片分析思维就好了。