cPanel 68.0.27 crashing / killing Litespeed

[MattW]

Had alerts from one of my servers shortly after the auto update to 68.0.27 that all the sites were down, and had to manually restart Litespeed. Saw another of my servers still had to update to run, so ran it manually, and that also killed off Litespeed, and didn't restart it automatically.

Last few lines of the error log prior to it going down

2018-01-22 22:52:36.454 [INFO] [51.255.71.125:19660] File not found [/home/XXX/public_html/showthread.php] 
2018-01-22 22:52:36.454 [INFO] [51.255.71.125:19660] File not found [/home/XXX/public_html/404.shtml] 
2018-01-22 22:52:36.707 [INFO] [172.68.58.8:19595] File not found [/home/XXX/public_html/404.shtml] 
2018-01-22 22:52:37.422 [INFO] [142.44.151.76:56634] connection to [uds://tmp/lshttpd/lsphp70.sock.18088] on request #0, confirmed, 1, associated process: -1, running: 0, error: Connection reset by peer!
2018-01-22 22:52:37.430 [INFO] [142.44.151.76:56634] connection to [uds://tmp/lshttpd/lsphp70.sock.18088] on request #0, confirmed, 1, associated process: -1, running: 0, error: Connection reset by peer!
2018-01-22 22:52:37.439 [INFO] [142.44.151.76:56634] connection to [uds://tmp/lshttpd/lsphp70.sock.18088] on request #0, confirmed, 1, associated process: -1, running: 0, error: Connection reset by peer!
2018-01-22 22:52:37.439 [NOTICE] [142.44.151.76:56634] Max retries has been reached, 503!
2018-01-22 22:52:37.439 [NOTICE] [142.44.151.76:56634] oops! 503 Service Unavailable
2018-01-22 22:52:37.439 [NOTICE] [142.44.151.76:56634] Content len: 0, Request line: 'GET /forum/index.php?/calendar/1-smartwatch-release-dates/week-1507421088/&k=880ea6a14ea49e853634fbdc5015a024&setlanguage=1&cal_id=1&langid=1 HTTP/1.1'
2018-01-22 22:52:37.439 [INFO] [142.44.151.76:56634] abort request..., code: 4 
2018-01-22 22:52:37.439 [INFO] [142.44.151.76:56634] File not found [/home/XXX/public_html/503.shtml] 
2018-01-22 22:52:40.023 [NOTICE] SIGTERM received, shutdown disabled, turn off fake Apache httpd.
2018-01-22 22:52:40.023 [NOTICE] [PID: 26506]: start cgid: 19381, /usr/local/lsws/bin/lscgid
2018-01-22 22:52:41.000 [NOTICE] [PID: 18088]: start cgid: 19479, /usr/local/lsws/bin/lscgid
2018-01-22 22:55:00.204 [NOTICE] Your License key will expire in 18 days
2018-01-22 22:55:00.204 [NOTICE] Loading LiteSpeed/5.2.3 Enterprise ...

Running 5.2.3 (build 10)

Not sure if this is a bug with Litespeed or cPanel, so reporting in both places.

 

[MattW]

This has just happened again as part of the update to 68.0.28.

 

[MattW]

https://forums.cpanel.net/threads/litespeed-not-restarting-automatically-after-update.620475/
5.2.2 doesn't crash during the cPanel update, so it's something specific to the 5.2.3 release.

 

[NiteWave]

5.2.4 just out yesterday : https://www.litespeedtech.com/products/litespeed-web-server/release-log
please upgrade 1 of your problem servers by

/usr/local/lsws/admin/misc/lsup.sh -f -v 5.2.4

to see if the issue still there.
also please check if wswatch.sh is running before and after you upgrade to 5.2.4

#ps -ef | grep wswatch.sh

regarding wswatch.sh, please refer https://www.litespeedtech.com/suppo...ed_wiki:cpanel:litespeed_watch_killedbycpanel

 

[MattW]

to see if the issue still there.
also please check if wswatch.sh is running before and after you upgrade to 5.2.4
regarding wswatch.sh, please refer https://www.litespeedtech.com/suppo...ed_wiki:cpanel:litespeed_watch_killedbycpanel

Thanks, this isn't running on any of the servers which I've checked. Is this something that is supposed to start manually, or are we expected to start it after each reboot?

 

[Karl]

Not sure this is specific to Litespeed. We sometime see this issue, cPanel ends up doing an orderly shutdown of Litespeed. We also saw it the other night, but we also saw it with servers still running Apache as well.