Web server received unexpected signal=9

Discussion in 'Bug Reports' started by yculer, Apr 28, 2011.

  1. yculer

    yculer Member

    Litespeed 4.0.20has problem with WHM/cpanel 11.28.87 ?

    I received an alert email like this:

    web server with pid=5469 received unexpected signal=9, a core file is created. A new instance of web server will be started automatically!

    I have already checked the posts here:


    It seems that kind of errors occur three or four times a month.And litespeed do not restart itself automatically.I had to restart httpd service myself.

    Apache is not running and that error happens at random time.
    Last edited: Apr 28, 2011
  2. NiteWave

    NiteWave Administrator

    can you upgrade to 4.0.20, since there are many bug fixes and improvement since 4.0.19
  3. yculer

    yculer Member

    Sorry I made a mistake when posted the tpoic.The version has already been 4.0.20.
  4. NiteWave

    NiteWave Administrator

    then do a Force Reinstall to 4.0.20 if not yet, to be sure it's the latest 4.0.20
  5. yculer

    yculer Member

    Well I have done a force reinstall to 4.0.20.But I am sure it's already the latest 4.0.20 since last month.
  6. webizen

    webizen Well-Known Member

    The latest 4.0.20 was updated 4/13/11 which is two weeks ago. You can do manual force install (upgrade) from command line and see if that makes any difference.
  7. yculer

    yculer Member

    I did force install from web interface but it made no difference.The same errror occurred just now.How to do an ungrade from command line?
  8. webizen

    webizen Well-Known Member

  9. yculer

    yculer Member


    I have done what you told and run litespeed 4.0.20 for a couple of days.And yesterday I still received the same error and had to restart web server manually:

    At [14/May/2011:05:16:11 +0800], web server with pid=9728 received unexpected signal=9, no core file is created. A new instance of web server will be started automatically!

  10. webizen

    webizen Well-Known Member

    Check /usr/local/cpanel/logs/safeapacherestart_log to see if "Forced restart" matches the time that lshttpd being killed.

    In addition, do not disable Apache from WHM. If disabled, cPanel would not try to start httpd after killing lsws (then you have to manually start lsws).

Share This Page