LiteSpeed Technologies
Download Download     Blog Blog     Wiki Wiki     Forum Forum     Store     Contact Contact    

Go Back   LiteSpeed Support Forums > LiteSpeed Web Server > Bug Reports > Web server received unexpected signal=9

Reply
 
Thread Tools Display Modes
  #1  
Old 04-28-2011, 02:47 AM
yculer yculer is offline
New Member
 
Join Date: Aug 2010
Posts: 9
Unhappy Web server received unexpected signal=9

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:

http://www.litespeedtech.com/support...ad.php?p=18653
http://www.litespeedtech.com/support...ead.php?t=3792

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 by yculer; 04-28-2011 at 02:54 AM..
Reply With Quote
  #2  
Old 04-28-2011, 02:50 AM
NiteWave NiteWave is offline
LiteSpeed Staff
 
Join Date: Sep 2009
Posts: 2,293
can you upgrade to 4.0.20, since there are many bug fixes and improvement since 4.0.19
Reply With Quote
  #3  
Old 04-28-2011, 02:54 AM
yculer yculer is offline
New Member
 
Join Date: Aug 2010
Posts: 9
Sorry I made a mistake when posted the tpoic.The version has already been 4.0.20.
Quote:
Originally Posted by NiteWave View Post
can you upgrade to 4.0.20, since there are many bug fixes and improvement since 4.0.19
Reply With Quote
  #4  
Old 04-28-2011, 03:13 AM
NiteWave NiteWave is offline
LiteSpeed Staff
 
Join Date: Sep 2009
Posts: 2,293
then do a Force Reinstall to 4.0.20 if not yet, to be sure it's the latest 4.0.20
Reply With Quote
  #5  
Old 04-28-2011, 04:02 AM
yculer yculer is offline
New Member
 
Join Date: Aug 2010
Posts: 9
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.
Quote:
Originally Posted by NiteWave View Post
then do a Force Reinstall to 4.0.20 if not yet, to be sure it's the latest 4.0.20
Reply With Quote
  #6  
Old 04-28-2011, 11:53 AM
webizen webizen is offline
LiteSpeed Staff
 
Join Date: Oct 2010
Posts: 2,390
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.
Reply With Quote
  #7  
Old 04-28-2011, 02:11 PM
yculer yculer is offline
New Member
 
Join Date: Aug 2010
Posts: 9
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?
Quote:
Originally Posted by webizen View Post
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.
Reply With Quote
  #8  
Old 04-29-2011, 01:43 AM
webizen webizen is offline
LiteSpeed Staff
 
Join Date: Oct 2010
Posts: 2,390
just download the latest 4.0.20 package from http://www.litespeedtech.com/litespe...downloads.html, unpack the gz file and run install.sh from the expand directory. choose U(pgrade) option during install.
Reply With Quote
  #9  
Old 05-15-2011, 05:04 AM
yculer yculer is offline
New Member
 
Join Date: Aug 2010
Posts: 9
Hi

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!


Quote:
Originally Posted by webizen View Post
just download the latest 4.0.20 package from http://www.litespeedtech.com/litespe...downloads.html, unpack the gz file and run install.sh from the expand directory. choose U(pgrade) option during install.
Reply With Quote
  #10  
Old 05-16-2011, 03:23 PM
webizen webizen is offline
LiteSpeed Staff
 
Join Date: Oct 2010
Posts: 2,390
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).
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:46 AM.



- Archive - Top
© Copyright 2003-2011 LiteSpeed Technologies, Inc. All rights reserved. Privacy Policy.