Archive for February, 2009


No Comments »

Cpuwatch warning emails got you down?

IMPORTANT: Do not ignore this email.
This is cPanel cpuwatch on [hostname of the server]!
While processing, the cpu has been
maxed out for more then a 6 hour period. The current load/uptime line on the server at the time of
this email is 3:14am up 18 days, 23:39, 0 users, load average: 1.13, 0.45, 0.16
You should check the server to see why the load is so high and take steps to lower the load. If you want stats to continue to run even with a high load; Edit /var/cpanel/cpanel.config and change extracpus to a number larger then 0 (run /usr/local/cpanel/startup afterwards to pickup the changes).

While this email seems ominous enough on its own in some cases it actually has to do with the way cPanel creates backups.

From shell run the command as follows:

ps aux | grep pkgacct

You will notice that the following have been running for a few days now:

root 30287 0.0 0.0 1460 380 ? SN Jan23 0:01 /usr/local/cpanel/bin/cpuwatch 4.0 /scripts/pkgacct tempacct /home/cpbackuptmp/cpbackup/daily backup
root 30288 0.0 0.5 7584 6208 ? SNs Jan23 0:06 pkgacct - tempacct - av: 3
root 30387 0.0 0.4 7584 5064 ? SN Jan23 0:00 pkgacct - tempacct - av: 3
root 15961 0.0 0.0 1600 528 ttyp0 S+ 15:41 0:00 grep pkgacct

You will want to end these processes which cPanel does present us with a nice utility available to us through Shell:

/scripts/autorepair check_hung_services

then run the upcp from either SSH or the WHM.