I've just had a couple of litespeed restarts because of an account going over it's CPU limit (Cloudlinux gives an error with the user's queue waiting for CPU gets too long - an error that their apache module detects and throughs a 508 serveur busy page).
At the moment I don't have many accounts on this server so it doesn't create any noticible problems (except the e-mails that are sent to inform me of the restart) but in the near future I can see this causing problems if multiple accounts get through errors and litespeed restarts every time.
Is there another way I can monitor litespeed is running and run automatic restarts instead of checking for 503 error while I'm waiting for this compatibility issue to be solved ? (like probing from a custom script run on localhost ?)
Do you have an update on if and when Litespeed will be made fully compatible with Cloudlinux's limiting system ?
I can live with increasing all the Entry Process limits to be higher than litespeed's but there would be no point in using Cloudlinux if I can't use CPU limits either…
Last edited by Monarobase; 04-21-2013 at 09:56 AM..