Major Problems

Discussion in 'LSWS 4.1 Release' started by VortMax, Jul 9, 2009.

  1. VortMax

    VortMax New Member

    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!!!!
  2. anewday

    anewday Moderator

    Which version? Try a core dump and send them to litespeed. Anything in the error_log?
  3. mistwang

    mistwang LiteSpeed Staff

    It was caused by hanging lsphp5 processes. will look into the root cause if it happen again.
  4. Doubletap

    Doubletap New Member

    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!
  5. mistwang

    mistwang LiteSpeed Staff

    From which version you upgrade from?
    What is the state of running lsphp5? parent PID? strace output?
    Are you using PHP suEXEC?
  6. VortMax

    VortMax New Member

    We had to set a cronjob to kill off the lsws processes at the end of each day to fix this problem as well. :(
  7. Doubletap

    Doubletap New Member

    Upgraded from 4.0.4

    How do I find answers to your other questions?
  8. mistwang

    mistwang LiteSpeed Staff

    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.
  9. Doubletap

    Doubletap New Member

    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.
  10. VortMax

    VortMax New Member

    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?
  11. mistwang

    mistwang LiteSpeed Staff

    Understood. You may want to go back to 4.0.6 as the 4.0.7 release may have random 503 problem.
  12. mistwang

    mistwang LiteSpeed Staff

    I don't think 4.0.9 will make difference on this, but it is recommended to upgrade to 4.0.9 .
  13. Doubletap

    Doubletap New Member

    Apparently I spoke too soon. The problem manifested itself again running 4.0.7 ... and once again I had to restore databases that were corrupted when lsphp5 consumed all server resources and caused MySQL to crash.

    I will see about setting up a temporary root account for you so that you can investigate what is happening on our server.
  14. robfrew

    robfrew New Member

    DoubleTap:

    Just curious, are you using eAccelerator with your LSWS?
    Last edited: Jul 30, 2009
  15. VortMax

    VortMax New Member

    We are using eAccelerator
  16. robfrew

    robfrew New Member

    VortMax:

    Are you having the same problems as DoubleTap? Runaway processes? Try disabling eAccelerator from php.ini and I bet it will all go away. In my other posts on the thread eAccelerator vs Xcache, I've been discussing how eAcc doesn't work with PHP 5.3 but that they released an update a few days ago that should work. So I've been testing it and what I have found is that after a few hours, my lsphp processes hang and I start seeing a load average of around 200.00. I have to use pkill -u {name of user process here} to kill all the hangs and restart. This sounds like a similar issue you are all having. I had to disable eAcc to resolve the issue. This sounds like it may not be a PHP 5.3 problem after all, it may be that the latest versions of LSWS are not working with eAccelerator any more.
    Last edited: Jul 30, 2009
  17. VortMax

    VortMax New Member

    We installed lsws on our server back in april (a new server) - we had been running it previously on another server without issues (and eAccelerator). The server was OK (except for the darn 403 errors with mod_security) until last week when the server started to slow...Had very many processes that never closed. Once we deleted them the server would OK for about a day then it lsws would stop responding...They recommended that I use a cronjob to remove them at night which I did and all has been OK but I will take your advice and see if it stops the problems.
  18. Doubletap

    Doubletap New Member

    Negative. Not running eAccelerator.
  19. Doubletap

    Doubletap New Member


    Can you give me an example of what sort of cron script you guys are running to kill your errant processes? That may be the temporary fix that we are desperately needing here.
  20. robfrew

    robfrew New Member

    DoubleTap:

    Are you running any type of opcode cache? Do you have a phpinfo page you can PM me to take a look at?

Share This Page