Slew of WordPress 503s Constantly with LiteSpeed
- Thread starter UWH-David
- Start date
No APC here. I am about to just scratch LiteSpeed on all of our servers if this persists.
Code:
2010-11-11 16:16:24.165 [INFO] [120.38.149.75:1450-0#APVH_sub.domain.com] connection to [/tmp/lshttpd/APVH_domain.com_Suphp.sock.371] on request #0, confirmed, 1, associated process: 16238, running: 0, error: Connection reset by peer!
2010-11-11 16:16:24.220 [INFO] [120.38.149.75:1450-0#APVH_sub.domain.com] connection to [/tmp/lshttpd/APVH_domain.com_Suphp.sock.371] on request #0, confirmed, 1, associated process: 16239, running: 1, error: Connection reset by peer!
2010-11-11 16:16:24.220 [NOTICE] [120.38.149.75:1450-0#APVH_sub.domain.com] Max retries has been reached, 503!
2010-11-11 16:16:24.220 [NOTICE] [120.38.149.75:1450-0#APVH_sub.domain.com] oops! 503 Service UnavailableThe log message shows that the PHP process crashed when processing the request.
give our staff a temp root login to check the 503 errors, there must be subtle difference between LiteSpeed PHP and Apache PHP which cause the error.
either memory limit, opcode cache or something, if it can be reliably reproduced, we can figure it out.
give our staff a temp root login to check the 503 errors, there must be subtle difference between LiteSpeed PHP and Apache PHP which cause the error.
either memory limit, opcode cache or something, if it can be reliably reproduced, we can figure it out.
For 503 errors, error log (error_log for cpanel, error.log for native lsws) should show that multiple attempts has been made to process the request, if all of them ends up with "connection reset by peer", it is likely a bug on PHP side, maybe PHP crashed.
The best way to find out why PHP crash is to let it dump core files. LSAPI_ALLOW_CORE_DUMP environment must be set for lsphp5 external app.
Run "ulimit -a" from a php test script to make sure core dump limit is high enough.
You can try crash a PHP process by manually sending "SIGBUS" signal while it is processing a test script takes long time to finish, something like calling sleep(60). make sure a core file created under the same directory where the script located. Otherwise, need to check the permission mask of that directory.
Once got the core file, can check it with GDB. Hope this is helpful.
The best way to find out why PHP crash is to let it dump core files. LSAPI_ALLOW_CORE_DUMP environment must be set for lsphp5 external app.
Run "ulimit -a" from a php test script to make sure core dump limit is high enough.
Code:
<pre>
<?php
$ulimit = `ulimit -a`;
echo "ulimit:\n".$ulimit;
?>
</pre>Once got the core file, can check it with GDB. Hope this is helpful.