Not positive yet, but I think they are gone again with the unpublished 4.0.17

Nope, still there

At [28/Aug/2010:15:03:31 -0400], web server with pid=26374 received unexpected signal=15, no core file is created. A new instance of web server will be started automatically!

Click to expand...

I think the best solution to this problem is from someone from cPanel to actually provide documentation of cPanel's Apache logic. They are sending kills among other things at the Litespeed processes. Why I don't know but a lot of their Apache logic is hidden in compiled binaries now so without them providing a helping hand no one will know. It could be something as simple as them waiting 10 seconds then issuing kills at all processes still existing.

This problem showed up when cPanel released 11.25 and unfortunately still is not fixed. Soon after 11.25 was released I tried contacting them about it. Unfortunately you talk to someone active on their forums they say make a ticket. The ticket people are unable to help provide such information. So I don't know where you'd go on this I've tried and failed as I don't have the connections to cPanel team it seems.

I think the best solution to this problem is from someone from cPanel to actually provide documentation of cPanel's Apache logic. They are sending kills among other things at the Litespeed processes.

Click to expand...

If cpanel wants to survive they really need to start working with vendors that use things other than Apache. There are now a dozen Apache replacements and a few of them like litespeed are too good to pass up.

Fortunately my linux and CLI knowledge/experience has grown to the point where I might be able to give up cpanel entirely in a year or two, especially if they don't start playing nice with others.