nginx 502出错集锦 nginx负载均衡 实战nginx nginx反向代
程序员文章站
2022-04-11 20:20:31
...
Nginx出现502 Bad Gateway 错误,
不要使用php-fpm的request_terminate_timeout,最好设成request_terminate_timeout=0;
因为这个参数会直接杀掉php进程,然后重启php进程,这样前端nginx就会返回104: Connection reset by peer。这个过程是很慢,总体感觉就是网站很卡。
查了Nginx的错误日志为:
[html] view plain copy
- 2014/08/02 16:14:31 [error] 17029#0: *17941 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 210.61.12.2, server: blog.lixiphp.com, request: “POST /api/1.0 HTTP/1.1″, upstream: “fastcgi://127.0.0.1:9000″, host: “blog.lixiphp.com”
- 2014/08/02 16:24:52 [error] 29615#0: *3 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 58.220.197.35, server: blog.lixiphp.com, request: “GET /404 HTTP/1.1″, upstream: “fastcgi://127.0.0.1:9000″, host: “blog.lixiphp.com”
不要使用php-fpm的request_terminate_timeout,最好设成request_terminate_timeout=0;
[html] view plain copy
- vi /etc/php-fpm.d/www.conf
[html] view plain copy
- ; The timeout for serving a single request after which the worker process will
- ; be killed. This option should be used when the ‘max_execution_time’ ini option
- ; does not stop script execution for some reason. A value of ’0′ means ‘off’.
- ; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
- ; Default Value: 0
- request_terminate_timeout = 0
因为这个参数会直接杀掉php进程,然后重启php进程,这样前端nginx就会返回104: Connection reset by peer。这个过程是很慢,总体感觉就是网站很卡。
以上就介绍了nginx 502出错集锦,包括了nginx,502方面的内容,希望对PHP教程有兴趣的朋友有所帮助。
推荐阅读
-
nginx反向代理tomcat实现负载均衡
-
Nginx+Tomcat 反向代理负载均衡 配置 学习(1)
-
CentOS6.7使用nginx提供静态资源服务,反向代理和负载均衡
-
实现基于nginx的tomcat负载均衡和集群配置 博客分类: 实战技术 nginxtomcatmemcached
-
前端也需要懂,负载均衡与Nginx反向代理
-
深入浅出Nginx之二【基本配置】 博客分类: Nginx/Tomcat/Jetty nginx负载均衡反向代理入门教程
-
Nginx反向代理和负载均衡实践
-
nginx系列4-负载均衡和反向代理
-
在ubuntu上面配置nginx实现反向代理和负载均衡
-
详解Nginx反向代理和负载均衡部署指南