765 recv() 失败(104:对等方重置连接)时从上游读取响应标头


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

2014/03/31 23:06:50 [error] 25914#0: *765 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 173.77.251.136, server: wiki.resonant-rise.com, request: "POST /index.php?title=Chisel&action=submit HTTP/1.1", upstream: "fastcgi://127.0.0.1:9016", host: "wiki.resonant-rise.com", referrer: "http://wiki.resonant-rise.com/index.php?title=Chisel&action=edit"
2014/03/31 23:06:50 [error] 25914#0: *765 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 173.77.251.136, server: wiki.resonant-rise.com, request: "POST /index.php?title=Chisel&action=submit HTTP/1.1", upstream: "fastcgi://127.0.0.1:9016", host: "wiki.resonant-rise.com", referrer: "http://wiki.resonant-rise.com/index.php?title=Chisel&action=edit"

我有一个mediawiki安装和IPB安装。他们都通过错误,但来自mediawiki的这个错误阻止我发布半大文章。我已经尝试了很多解决方案,添加catch_workers_output = 是的,调整 pm.* 设置。仍然无法解决此问题。我正在尽头试图弄清楚这一点。

PHP-FPM Conf

http://pastie.org/private/aczklc52ll9yv0uz5drcqg

PHP-FPM WWW.会议

http://pastie.org/private/wod3xipxhm8ractksw7ha

NGINX VHOST for MEDIAWIKI

http://pastie.org/private/h9co8aykbdmfzk2bd5qq

如果失败取决于页面的大小,则与操作导致多少工作量有关。我的疯狂猜测是:增加超时(您目前有send_timeout 60s;)。

一个很长的页面的解析时间很容易超过 60 秒,特别是如果你使用的是低功耗服务器,没有调整性能或启用了繁重的解析器扩展。

我而言,该项目的PHP版本与我以前的PHP版本不同