I got Litespeed Enterprise 4.2.7 installed on my server.
Today it shut itself down, here is the log:
2014-03-21 07:30:56.061 [ERROR] Unexpected error inside event loop: No child processes
2014-03-21 07:30:56.061 [NOTICE] [Child: 5912] Start shutting down gracefully ...
2014-03-21 07:30:56.061 [NOTICE] New litespeed process is ready, stop listeners
2014-03-21 07:30:56.061 [INFO] Stop listener 127.0.0.1:443.
2014-03-21 07:30:56.061 [INFO] Stop listener 127.0.0.1:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [2607:fad0:32:a00:225:90ff:fe57:25d1]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [2607:fad0:32:a00:225:90ff:fe57:25d1]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [::1]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [::1]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener *:7080.
Note, I removed my IP from the above log for security reasons.
This caused a 20 minutes downtime of my server, because cPanel/WHM could not "automagically" restart litespeed, seems like it was trying to restart Apache instead, and obviously failed. Only manual restart by the hosting support restarted litespeed httpd.
2 questions:
1) What is this error and how can it be prevented?
2) How come cPanel could not restart it and tried to restart Apache? Isn't lsws supposed to be added to the monitoring list automatically upon installation?
Today it shut itself down, here is the log:
2014-03-21 07:30:56.061 [ERROR] Unexpected error inside event loop: No child processes
2014-03-21 07:30:56.061 [NOTICE] [Child: 5912] Start shutting down gracefully ...
2014-03-21 07:30:56.061 [NOTICE] New litespeed process is ready, stop listeners
2014-03-21 07:30:56.061 [INFO] Stop listener 127.0.0.1:443.
2014-03-21 07:30:56.061 [INFO] Stop listener 127.0.0.1:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [IP-REMOVED-FOR-SECURITY-REASONS]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [2607:fad0:32:a00:225:90ff:fe57:25d1]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [2607:fad0:32:a00:225:90ff:fe57:25d1]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener [::1]:443.
2014-03-21 07:30:56.061 [INFO] Stop listener [::1]:80.
2014-03-21 07:30:56.061 [INFO] Stop listener *:7080.
Note, I removed my IP from the above log for security reasons.
This caused a 20 minutes downtime of my server, because cPanel/WHM could not "automagically" restart litespeed, seems like it was trying to restart Apache instead, and obviously failed. Only manual restart by the hosting support restarted litespeed httpd.
2 questions:
1) What is this error and how can it be prevented?
2) How come cPanel could not restart it and tried to restart Apache? Isn't lsws supposed to be added to the monitoring list automatically upon installation?