![]() |
Major Problems
Two days ago we started getting 503 errors and all of our websites went down on our server. It happens in the afternoon and was only able to be dealt with by restarting the litespeed service. Today I got about 100 emails from the server with the message:
LiteSpeed Web server ***** on ***** restarts automatically to fix 503 Errors I had to disable litespeed and restart apache to get the websites back online. What in the heck is going on? No updates to the server recently...No new software installed etc. There are about 300+ lsphp5 processes from days/weeks/months ago that appear to still be running but not doing anything. HELP!!!! |
Which version? Try a core dump and send them to litespeed. Anything in the error_log?
|
It was caused by hanging lsphp5 processes. will look into the root cause if it happen again.
|
Since upgrading to 4.0.9 we have had several crashes due to innumerable instances of lsphp5 left running. In fact, I just came here today to see if this was a known issue.
Help! |
From which version you upgrade from?
What is the state of running lsphp5? parent PID? strace output? Are you using PHP suEXEC? |
We had to set a cronjob to kill off the lsws processes at the end of each day to fix this problem as well. :(
|
Quote:
How do I find answers to your other questions? |
Are you using control panel? or everything configured from lsws web console natively?
If possible, please PM me a temp root access, I will check what is going on. |
Well, I had to do something quick because it was causing problems with the sites that I host... so I fell back to 4.0.7 and so far, so good. I realize this doesn't help you troubleshoot but, as I said, I had to fix it ASAP and this weems to be working.
|
mistwang,
Does 4.0.9 fix issues with 4.0.6 that would cause all of the processes to not remove themselves if a script was not timing out properly? |
| All times are GMT -7. The time now is 10:13 PM. |