Closed ddrager closed 5 years ago
@ddrager is the line from error.log
you posted all there is?
If possible, what might help is getting a core dump of a worker that is stuck in shutdown.
That way, we can hopefully figure out what is going on in the workers that got stuck, by inspecting the core dump.
Yes, it is there a few times (12 to be exact) but exactly the same time/pid. I'll start it up again and wait for it to go into this state, then try to get a core dump.
Confirming this. I switched to nginx, all is fine, but ngx_pagespeed is TOTALLY UNUSABLE for now. I tried it with latest versions, 1.4.2 (stable), 1.5.3 (mainline) and also tried to compile all from source (including psol). Always same error. Nginx stops responding after second+ ab or siege test. Let's try: ab -n 1000 -c 10 http://artactivator.com/ for first time, all goes fine. 50 req/s for drupal index.php page but second time, there are timeouts, ab stops working. Ok, trying siege. Req/s slowing slowing down each test, until nginx will give 500 error
In nginx's error log I receive such errors randomly: Check failed: may_startthreads NgxBaseFetch::RequestCollection: Broken pipe
Disabling ngx_pagespeed shows about 50 req/s every stresstest on every page and nginx working fine. But it's better to recompile nginx without pagespeed support, because sometimes it's working strange when off.... I want to use it, but don't want to switch back to apache....
Closing out old issue.
On my production site nginx stops responding to connections after about 30 minutes running the pagespeed module.
Error log shows:
2013/07/12 09:55:15 [error] 7451#0: [ngx_pagespeed 1.6.29.3-3270] http://domain.com/attachment.php?attachmentid=1368177&stc=1&thumb=1&d=1349112204:0:serf_context_run error status=110 (Connection timed out)
Here is an strace from one of the processes stuck in the shutting-down state:
Some relevant settings from nginx.conf:
nginx build info:
Any thoughts or ideas how I can debug the cause of this? Turning off Pagespeed fixes the issue.