hammerthrow

Member
Dec 25, 2017
7
1
1
Seoul
cPanel Access Level
Root Administrator
AW Stats and Webalizer worked for my domain up until the middle of the day on May 8th, at which point everything dropped to zero as if the site vanished from the server.

in WHM: Home »Server Configuration »Statistics Software Configuration,

The error message below shows up in red:

"The server is having trouble keeping up with your statistics processing schedule. You should increase the time between statistic generation, or upgrade the server. If you have recently decreased the time between statistic generation, you may wish to wait that amount of time to see if the server will catch up before changing back."

when I click "See Specific User's Summary, and select the domain in question, the following results occur:

Analog: Stats Last Processed at:
Sat Jun 16 08:35:07 2018

AWSTATS: Bandwidth Last Processed at:
Sun Jun 10 07:02:00 2018

Webalizer: Stats Processing is Behind 6712.40 minutes

Note that all three of these Stat Programs completely stopped reporting on May 8th, despite the above messages showing action in June.

I have other domains on the same server, all of which are not experiencing these issues.

Any help is greatly appreciated.
 

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,301
363
Houston
Hi @hammerthrow

Based solely on the error message it looks like your server is having trouble completing stats processing during the times which you've allowed it to run. If you're able to access the server via SSH please let me know what is in the stats_log by running something similar to the following:

Code:
tail -100 stats_log
as well as the output of:

Code:
/scripts/runweblogs $USER
replace $USER with your user


Thanks!
 

hammerthrow

Member
Dec 25, 2017
7
1
1
Seoul
cPanel Access Level
Root Administrator
Hi @cPanelLauren

Thank you for your reply.

Via SSH,

The "tail -100 stats_log" code produces no result. It says "tail: cannot open `stats_log' for reading: No such file or directory"

The "/scripts/runweblogs $USER" command produces the following, which is has said every time I've run the same command over the past few days.

"==> cPanel Log Daemon version 26.0
[2018-06-21 02:32:40 -0400] Logs are already being processed, please try again later."


It seems the logs are perpetually processing, or stuck, or something.

It is worth noting that within WHM, there is are no longer any error when examining the stats software in "Statistics Software Configuration". The server no longer displays the original error which I posted in my original post:

"The server is having trouble keeping up with your statistics processing schedule. You should increase the time between statistic generation, or upgrade the server. If you have recently decreased the time between statistic generation, you may wish to wait that amount of time to see if the server will catch up before changing back."

It now says:

"The server currently is able to keep up with your statistics processing schedule."

However, stats still show nothing since May 8th.

It is also worth nothing that the other three domains hosted on the same server do not have any issues, and never stopped updating.
 

hammerthrow

Member
Dec 25, 2017
7
1
1
Seoul
cPanel Access Level
Root Administrator
Brief followup:

Regarding other sites on the server working fine with AWstats and Webalizer; I was wrong. The other domains appear to have stopped reporting all traffic on the 10th of June.
 

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,301
363
Houston
HI @hammerthrow


I am so sorry I failed to give you the proper path to the stats log:

Code:
tail -100 /usr/local/cpanel/logs/stats_log
This output:

Code:
"==> cPanel Log Daemon version 26.0
[2018-06-21 02:32:40 -0400] Logs are already being processed, please try again later."
Makes me think the process is stuck. Can you run the following:

Code:
/scripts/restartsrv_cpanellogd
Then check the process
Code:
ps faux |grep cpanellog[d]
And let me know the output of both?

Once that's done can you also run:
Code:
/scripts/runstatsonce
And let me know if once that process is complete you start seeing the stats update?


Thanks!