I'll have to check my logs, but I was wandering if the restart wasn't a symptom instead of a cause.
Could it be PHP hitting litespeed's CPU limit ?
I upped it from the default 80% to 800% yesterday but haven't had a chance to check the logs yet.
I get a 503 error when litespeed can't access PHP. Over the last 20 times in the past two days users got 503 errors I see litespeed doing a gracefull restart then a few seconds later litespeed says it tried to access PHP 3 times and didn't get an answer so it shows a 503 error message.
I'll check later today and see if the new CPU limit has solved the 503 error messages or not