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

时间:2014-04-01 03:15:46

标签: nginx mediawiki php

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 = yes,调整了pm。*设置。仍然无法解决此问题。我试图想出这个问题,我的斗智斗勇。

PHP-FPM Conf

http://pastie.org/private/aczklc52ll9yv0uz5drcqg

PHP-FPM WWW.CONF

http://pastie.org/private/wod3xipxhm8ractksw7ha

NGIAX VHOST for MEDIAWIKI

http://pastie.org/private/h9co8aykbdmfzk2bd5qq

1 个答案:

答案 0 :(得分:0)

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

很长的页面的解析时间超过60秒很容易,特别是如果你在低功耗服务器上,没有tuned performance或者已经启用了大量的解析器扩展。