massive lsws shutdown 12-2am

[felosi]

I have had litespeed servers shuttting down all night and staying down until i come in and restart them. Any idea whats going on?

Thats one thing that I defintely cant have is webservers shutting down for no reason at 12-2am in the morning.

I know its not just me cause too many servers have done it.

 

[felosi]

one of these servers I had all logs on just all of a sudden got this at:
2008-03-05 22:55:58.328 [NOTICE] [Child: 14950] Start shutting down gracefully ...
2008-03-05 22:55:58.328 [NOTICE] SIGTERM received, stop server...


Seems to be same time as other servers.


UPDATE: 3 more clients servers, same thing

 

[mistwang]

All related to this, http://www.litespeedtech.com/support/forum/showthread.php?t=1824


We are working on a solution.

 

[felosi]

ya but this just now started happening to me, I never had this problem before

Any ideas or quick fixes?

 

[mistwang]

Are you using cPanel CURRENT release? just switch to STABLE

 

[felosi]

some were release, some were stable.

 

[mistwang]

does all servers get "SIGTERM received, stop server" in the log?

 

[felosi]

looks like it

I think it may be some thing now cause exim has a bad habit of taking over port 80. I would assume they have something to kill anything running on port 80

This is the first I ever seen of it,

If we could just have some type of service monitor would be nice

 

[felosi]

just wanted to add, on mine it just shut down litespeed, did not start apache - I have apache disabled.

 

[mistwang]

I think it may be some thing now cause exim has a bad habit of taking over port 80. I would assume they have something to kill anything running on port 80

Why do you think exim was doing that?

 

[felosi]

No I think that is why cpanel implemented this new stuff

Just a theory

George check your mail when you get a chance please.

 

[mistwang]

A simple shell script to check lshttpd and start LSWS, create a cron job.

#!/bin/sh
ERR=1
if [ -f /tmp/lshttpd/lshttpd.pid ]; then
    kill -0 `cat /tmp/lshttpd/lshttpd.pid`
    ERR=$?
fi

if [ $ERR -ne 0 ]; then
    /opt/lsws/bin/lswsctrl start
    D=`date`
    echo "$D: LSWS stopped, start LSWS."
fi

 

[felosi]

Thank you very much George, I hope it all works. Cpanel does some of the gayest things sometimes. Its beyond me why they would want to kill other then httpd processes for no reason. Maybe the exim or lingering childs, who knows.

Been a hetic week.

Thanks again and sorry for the frantic emails, just had a two hour outage on the network the other day and on top of the 2-6 hour outages I had from this clients was not too happy

 

[felosi]

Ok it works, I left out one server to try and see whats going on but it seems to do this randomly at about 1-2 am. I am not sure if it is a upcp because I ran that manually yesterday and it didnt happen. So its untelling. Thanks again for this handy script, I can sleep now

 

[aww]

Does that script above take into account if lsws is manually stopped?
Or will it always attempt to restart it if it is simply not running?

 

[vivek]

The above script is not a permanent solution.

 

[felosi]

everyone just put in tickets, post on their forums, something. I have seen nothing but smartass and vague answers from their support staff in other situations. I know 2 that has put in tickets so far just to be told cpanel does not support litespeed and litespeed is NOT compatible with cpanel. What a load of shit. This has me pretty ticked off.

 

[vivek]

everyone just put in tickets, post on their forums, something. I have seen nothing but smartass and vague answers from their support staff in other situations. I know 2 that has put in tickets so far just to be told cpanel does not support litespeed and litespeed is NOT compatible with cpanel. What a load of shit. This has me pretty ticked off.

Yea, cPanel is killing litespeed just because they dont support it. Just like me , please open support ticket to them to stop these kind of works.

 

[aww]

Yea, cPanel is killing litespeed just because they dont support it. Just like me , please open support ticket to them to stop these kind of works.

Remember from cpanel's standpoint, apache is the only bundled solution. It's not like their new code looks for litespeed processes and kills them, they just did something lazy without consideration for alternative software. Cpanel could care less and their support and sales aren't going to be affected by us few complaining.

Unfortunately this is really on Litespeed's hands to work around - I just wish someone had been watching the current releases for changes like this before they happened.

I have faith though that there will be a fix soon from Litespeed, they tend to be very good about these things and few companies fix problems faster.

 

[felosi]

well now mine is doing it on account creation as well. Good thing I have that cron script