[ERROR] Unexpected error inside event loop: No child processes

Mike Yo.

Active Member
#1
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?
 

Mike Yo.

Active Member
#2
My hosting company contacted you (Litespeed) and got back to me saying that the issue is fixed on version 4.2.7 and if I upgrade to this version, this will not occur again.
At least that's what my hosting company are claiming that you said.
This is strange, because my version is already the latest stable 4.2.7

Can anyone from litespeeed please respond to this thread? I am a paying customer...

Thanks
 

Michael

Well-Known Member
Staff member
#3
Howdy Mike,

This is one of LSWS's eccentricities (and advantages). We release bug fixes to the newest release constantly. If you force reinstall 4.2.7, you will get a slightly newer build of 4.2.7 with this bug fix. (You can find the force reinstall function in the version manager of our WebAdmin console or our control panel plugins.)

For 5.0, because of popular demand, we will be building in a way to see which build of a version you have and reinstall a certain build.

Cheers,

Michael
 
Top