I had the very similar problem: after install of the 2.2.4 update my server lay down (linux, centos - latest).
I knew that I should read manual first (to know how to roll back with one simple command) but instead I replaced files from autoupdate folder thinking that it would make a run. Now I know it was a bitter mistake. Since that Lshttpd fails to start without giving any notice (btw, I made chown too).
Could please drop me line, what to do. As I still do not want to reinstall litespeed due to own reasons.
Are you using a Enterprise edition, if yes, please contact our sales to address the problem with 2.2.4 release.
Nope. Nou. You may be proud, I like you - your style, and if I were a commercial customer, I would by all means build an enterpise. but I am not. And in some trivial issues you are making me amazed. Thus, Linux apps (like Ruby with gem update) may fail without reason, I don't feel depressed or opressed.
There should not be any problem with 2.2.4 standard upgrade procedure.
If there is core files under /tmp/lshttpd/bak_cores/, please send it to bug@litespeedtech.com
We can take a look at your installation if you don't mind giving us temp root access for little while.