massive lsws shutdown 12-2am

Discussion in 'Bug Reports' started by felosi, Mar 6, 2008.

  1. felosi

    felosi New Member

    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.
  2. felosi

    felosi New Member

    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
    Last edited: Mar 6, 2008
  3. mistwang

    mistwang LiteSpeed Staff

  4. felosi

    felosi New Member

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

    Any ideas or quick fixes?
  5. mistwang

    mistwang LiteSpeed Staff

    Are you using cPanel CURRENT release? just switch to STABLE
  6. felosi

    felosi New Member

    some were release, some were stable.
  7. mistwang

    mistwang LiteSpeed Staff

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

    felosi New Member

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

    felosi New Member

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

    mistwang LiteSpeed Staff

    Why do you think exim was doing that?
  11. felosi

    felosi New Member

    No I think that is why cpanel implemented this new stuff

    Just a theory

    George check your mail when you get a chance please.
  12. mistwang

    mistwang LiteSpeed Staff

    A simple shell script to check lshttpd and start LSWS, create a cron job.
    Code:
    #!/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
  13. felosi

    felosi New Member

    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
  14. felosi

    felosi New Member

    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 :)
  15. aww

    aww New Member

    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?
  16. vivek

    vivek New Member

    The above script is not a permanent solution.
  17. felosi

    felosi New Member

    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.
  18. vivek

    vivek New Member

    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.
  19. aww

    aww New Member

    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.
  20. felosi

    felosi New Member

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

Share This Page