I Hope somebody can shed some light on this.
I resized my boot partition and resized the /tmp folder. (via the /scripts/securetmp). I also enabled NAT since I'm running a EC2 (AWS) image.
Now since this resize, I'm getting the warning emails:
[statscheck] Stats/Server Overload on [server]
IMPORTANT: Do not ignore this email.
This is cPanel stats runner on [server]!
While processing the log files for user [userid], the cpu has been
maxed out for more than a 6 hour period. The current load/uptime line on the server at the time of
this email is
21:32:43 up 3 days, 21:09, 0 users, load average: 3.10, 3.14, 3.15
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).
If I ssh on the server and do a:
ps -aux | grep [user]
I see a few processes for the [user]. When i kill the process, the stats for the next user are run (hanging??) and its starts again. So apparently for some reason the /usr/local/cpanel/bin/logrunner can't do what it needs to do.
Anybody got a glue ?
By memory it looks fine. Also the log files being processed are pretty simple websites without a lot of traffic.
top - 22:29:14 up 3 days, 22:05, 1 user, load average: 3.62, 3.38, 3.40
Tasks: 118 total, 2 running, 114 sleeping, 1 stopped, 1 zombie
Cpu(s): 0.7%us, 6.4%sy, 0.0%ni, 0.0%id, 92.9%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 3884688k total, 3516608k used, 368080k free, 306852k buffers
Swap: 0k total, 0k used, 0k free, 2838040k cache
I resized my boot partition and resized the /tmp folder. (via the /scripts/securetmp). I also enabled NAT since I'm running a EC2 (AWS) image.
Now since this resize, I'm getting the warning emails:
[statscheck] Stats/Server Overload on [server]
IMPORTANT: Do not ignore this email.
This is cPanel stats runner on [server]!
While processing the log files for user [userid], the cpu has been
maxed out for more than a 6 hour period. The current load/uptime line on the server at the time of
this email is
21:32:43 up 3 days, 21:09, 0 users, load average: 3.10, 3.14, 3.15
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).
If I ssh on the server and do a:
ps -aux | grep [user]
I see a few processes for the [user]. When i kill the process, the stats for the next user are run (hanging??) and its starts again. So apparently for some reason the /usr/local/cpanel/bin/logrunner can't do what it needs to do.
Anybody got a glue ?
By memory it looks fine. Also the log files being processed are pretty simple websites without a lot of traffic.
top - 22:29:14 up 3 days, 22:05, 1 user, load average: 3.62, 3.38, 3.40
Tasks: 118 total, 2 running, 114 sleeping, 1 stopped, 1 zombie
Cpu(s): 0.7%us, 6.4%sy, 0.0%ni, 0.0%id, 92.9%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 3884688k total, 3516608k used, 368080k free, 306852k buffers
Swap: 0k total, 0k used, 0k free, 2838040k cache