Accounts over quota cause high CPU usage and more problems.
A very strange behavior, never seen with regular CentOS.
If user is over quota - in most cases if not all his page won't work, returning 500-error. Recently also one account was over quota and was trying to access IMAP - which lead to enormous load. But at the same time we suspect, that this is something wrong in configuration - because this happens on 1 of 4 servers (all running CloudLinux). Could anyone point me to the right direction? All servers have CageFS enabled. The only difference would be, that the server, that has issues - has LiteSpeed, instead of Apache.
-
If you have a hard quota and the web app (or mail) needs to write data, the app may hang because it cannot write. I generally don't use hard quotas on our systems for this reason. You may want to see if there are processes building up for the user during this condition. 0 -
That also may be something that would warrant a ticket, if its only occurring on CL w/Litespeed. If you purchased either license through us feel free to open ticket with us using the link in my signature. If not you can open a ticket with CloudLinux directly here: CloudLinux - Main | New template or Litespeed here: Support - LiteSpeed Technologies 0 -
If you have a hard quota and the web app (or mail) needs to write data, the app may hang because it cannot write. I generally don't use hard quotas on our systems for this reason. You may want to see if there are processes building up for the user during this condition.
Hm, I don't remember any setting for this inside WHM - regarding hard or soft quotas. What could be checked? @cPanelLauren - we bought LiteSpeed directly, can't find option to order it through manage2 system. Can we still open a ticket?0 -
Hm, I don't remember any setting for this inside WHM - regarding hard or soft quotas. What could be checked? @cPanelLauren - we bought LiteSpeed directly, can't find option to order it through manage2 system. Can we still open a ticket?
@anton_latvia - you can definitely open a ticket, worst case scenario we will take a look at it and let you know what's causing the issue.0
Please sign in to leave a comment.
Comments
4 comments