I have been receiving this email for one of my servers:

IMPORTANT: Do not ignore this email.
This is cPanel stats runner on xxx.xxx.com!
While processing the log files for user root, 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
10:15am up 19 days, 9:51, 0 users, load average: 16.29, 7.05, 5.33
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).



This is usually related to one account in particular, and I had this same problem on another server (the main reason I moved to a new server), and I'm sorry to see it pop up again. I have analog, awstats and webalizer all running (cpanel / whm)

Is there any way to fix this? is it possible to delete the logfile after each run, and if so, would my stats still keep their history?

I'm also having the same problem. Is there any CPanel expert around that can help us out? :)

Stats generation can take a huge load and that's common. In Cpanel 6, there's a setting that can limit the maximum load that the stats generation can place your server at. That should help.

Otherwise, you can always ask the user since you can identify to back up his log file, and then delete it so that it starts small again :)

Or you can also delete the logs after each stats generation (in Cpanel settings) But this is not recommended. A lot of users is not going to like it.

As sad as it sounds, I'm glad I'm not the only one.

I take it that your site is also a high traffic website? I deleted the logfile once, and it took some time for the probablem to re-appear, so that may be the ticket, I just don't want to lose any stats info.

Hmm, 3 more of these emails...

I've set the cpanel cpu limit to 12 (did it a week ago) but I'm not really sure it helps. I get the impression that if the cpu limit is set too low, the stats will never update.

I delete the log file for this account, and at that time the log was almost a gig in size. How big is too big for a logfile? The stats ran fine like that for a while, but about 3 weeks later I'm in the same situation.

If I delete the logfile after each run, will awstats and webalizer remember the history?

If I delete the logfile after each run, will awstats and webalizer remember the history?

Yes, it would if they were ran before.

You could actually include an additional cronjob as

/scripts/runlogsnow

and set it to a time which is less busy and that should do the trick. At least that works for me.

run "ps -ax" from the shell and you'll find 2-3 dead "cpbackup" processes. Just "kill -9" them.

Is there any option in CPanel to rotate the log files weekly (instead of monthly)?

Do Webalizer/Analog/AwStats keep track of the history? I mean if I delete the user log files, will it also mean some days' stats will be lost?

I deleted the logfile, and then did a "touch" to recreate it. I then ran /scprits/runweblogs and chose the problem user. Once again, the process is still running, after a couple of hours, with no update.

according to top, awstats.pl is using 65% of the memory, and the time is 227:31 ( I don't know what that is, I assume the runnning time)

If I type kill -9 awstats.pl, will that just end the awstats program?

wow, I did a kill -9 pid and killed awstats. my server immediately went from 96% memory usage to 13%.

hehe. Check out stats_log file in your /usr/local/cpanel/logs/ directory :cool:

This file is 2Gb on one server (cpanellogd was stoped) and ~1.9 - 1.5Gb on others. Then view content of the file ;)

http://forums.cpanel.net/showthread.php?s=&threadid=7850

i have the same problem
how can i fix it ?

We have had this issue on a couple servers lately and I was able to get ours jumpstarted by running /usr/local/cpanel/startup which basically restarts cpanellogd.

Simple problem, simple solution: When you have a large number of sites on a server you should always consider increasing the log process time.

In cpanel PRO you are able to do this. Also, make sure that you setup the logs to be rotated at the end of the month so you don't have large log files. Anything larger than 2GB is going to cause Apache to crash :(

I think I need to do some tweaking. Good read.