[LSWS 4.2.1] restarts automatically to fix 503 Errors

Discussion in 'General' started by Alfa-Host, Nov 29, 2012.

  1. Alfa-Host

    Alfa-Host New Member

    Hello,

    After upgrade to 4.2.1 and rebuild php with lsapi 6.1 , within 12 hours i got 35 "restarts automatically to fix 503 Errors" mail.

    This is normal ?

    Thanks.
  2. webizen

    webizen New Member

    pls switch back to the old lsphp5 (stay with 4.2.1) and see any difference.
  3. mistwang

    mistwang LiteSpeed Staff

    Please email to bug@litespeed... or PM us a temp root access, we will take a look.
  4. Alfa-Host

    Alfa-Host New Member

    Today I encountered a downtime in my server ,the reason was not clear. after that i disabled the PHP suEXEC daemon mode and did not get any 503 fix mail ,
    3 hours later I encountered the sites is not loading problem , after checking server from cpanel I saw my server load is too high (near 200 and every second goes up) , login to ssh was not possible also i can't kill any process from cpanel process manager , i performed a hardware reboot and after that i set LVE to off and switch back to 4.1.13 , now after 7h i did not see any problem .

    OS : CloudLinux 2.6.32-379.11.1.lve1.1.9.8.2.el6.x86_64
  5. mistwang

    mistwang LiteSpeed Staff

    Please send error.log and stderr.log during the 503 problem to us, or let our staff to collect those log files from your server.
  6. Alfa-Host

    Alfa-Host New Member

    A few days ago I sent the logs to you , the files can show the problem?
  7. mistwang

    mistwang LiteSpeed Staff

    It looks like CloudLinux resource limit was hit, and causes 503 errors in your case.
    You should be careful with "PHP suEXEC max conn", if set it too high, while CageFS/LVE limit was not high enough, it will cause trouble during traffic surge.
  8. Alfa-Host

    Alfa-Host New Member

  9. webizen

    webizen New Member

  10. Alfa-Host

    Alfa-Host New Member

    I used LSWS 4.2.1 again but server crashed again :

    Message from syslogd@sv6 at Dec 5 10:42:24 ...
    kernel:[425682.950437] BUG: soft lockup - CPU#0 stuck for 67s! [lsphp5:279355]

    Message from syslogd@sv6 at Dec 5 10:42:24 ...
    kernel:[425682.956419] BUG: soft lockup - CPU#2 stuck for 67s! [lsphp5:279193]

    Message from syslogd@sv6 at Dec 5 10:42:36 ...
    kernel:[425694.925191] BUG: soft lockup - CPU#3 stuck for 67s! [lsphp5:279455]

    Message from syslogd@sv6 at Dec 5 10:42:36 ...
    kernel:[425694.928182] BUG: soft lockup - CPU#4 stuck for 67s! [lsphp5:279326]

    Message from syslogd@sv6 at Dec 5 10:42:36 ...
    kernel:[425694.935162] BUG: soft lockup - CPU#6 stuck for 67s! [lsphp5:279038]

    Server load avg goes to high and every second goes up and then server hung !
  11. NiteWave

    NiteWave Administrator

Share This Page