hi. i have been reading around and would like to have answers on situation like the subject before i switch to Master Reseller hosting to vps (as a starter). pardon me for a newbie question as indeed i am with regards to vps operation. nobody would know when a direct client or a sub-client would violate a TOS (for instance, running a high resource script or probably an underground streaming site). when this happens, since vps is RAM-limited, it'll come to a point that the script or the site would eat up all the memory resources preventing any other clients in the vps to access whm since no more left RAM to execute this cpanel. my question now: is there a way to run any command using putTy, or in any which way, to determine which high-resource contributing client is at fault. and is there a way to offline suspend the account without using WHM (like i said, there is WHM access due to high RAM). please help us i need to know this before i go deeper and buy myself a vps
Well so this is the 1 millionth thread on Digitalpoint? http://forums.digitalpoint.com/showthread.php?t=1000000
You should run the top command first to see if its mysql that is causing high memory usage, if it is, you can shut down mysql via SSH which will make access to WHM faster until you find the account using high mysql usage. I'm not too good with Linux commands but I know that on a VPS, WHM has a CPU/MySQL Usage link which will show how much CPU and memory an account has used on that day which will give you an clue. If you are looking for a VPS and dont have much experience in Linux, you're better off getting a VPS that offers some sort of management. We currently offer Semi-Managed packages which means we will help you with such problems & more.
As above, use top. The chances are, you'll see a lot of process by the name name (httpd, exim, mysql) if that's the abusive process. If its too slow to execute: service httpd stop Code (markup): (for httpd [Apache] for example), use kill: kill -9 httpd Code (markup): Just replace httpd with the bad process. This will get you into WHM where you can start the process again (or just use SSH) then investigate. Jay
use netstat -ntp | grep :80 -c to see if there is a flood or not on your port 80 you can change the port to check other port available
cPanel on a VPS isn't a good idea.. unless you have upwards of 512mb of RAM. I'd recommend lxadmin or webmin.