awstats reports missing

[stuartmcdonald]

Over the last few days, awstats hadn't ran automatically on my server, but just for one (the largest) account.

When I noticed that awstats hadn't run yesterday, I ran it manually (via the top-of-page link on the awstats page in cPanel), and it gave me the stats for that day up to when I requested it manually (about 8 hours worth), but the previous two day's worth of stats were zero.

I wrote it off as some kind of anomaly, but when I checked today, it again hadn't run, so I ran it manually and again it gave me the stats just from midnight to now, with no extra stats for the remaining 16 hours of the previous day.

It seems to be that something has gone amiss as I haven't changed anything on the server in ages and the problem just commenced on the 14th of June. awstats on all the other sites on the server are running as per normal. This is a problem with just a single account.

I'm running:
WHM 11.23.2 cPanel 11.23.3-C25533
CENTOS Enterprise 4.6 i686 on standard - WHM X v3.1.0

Any suggestions on where I should start looking to sort out this problem, would be much appreciated.

 

[stuartmcdonald]

Perhaps problem is with runweblogs

Ok, after more digging, I've found the following;

If I run /scripts/runweblogs USERNAME for the account in question, the script runs, then there's a long (like 5 minutes) pause at:

"About to fork for USERNAME [ALL DOMAINS: list of main domain plus eight sub domains]"

Then it says

"complete"

However, when I go and check awstats, I see that the stats have not updated at all. So this is suggesting the issue may be with the runweblogs script rather than awstats itself.

Is there a way to check on this further?

thanks

 

[phinsup]

awstats quit working on my largest site as well.

Would appear that it isnt monitoring bandwidth for that domain either

 

[cPanelDavidG]

I know a common issue in the past was that people wouldn't give stats enough time to completely run through the logs, making it seem like stats were never being generated, when in fact the process was working fine, it just never had the opportunity to complete.

 

[phinsup]

Mine quite working on May 18th, the last day it worked was May 17th, no idea why.

 

[cPanelDavidG]

Mine quite working on May 18th, the last day it worked was May 17th, no idea why.

You may want to have someone take a look at that for you: http://tickets.cpanel.net/submit

 

[stuartmcdonald]

I raised a ticket last night regards this and will report back with any progress.

I don't think it's a "time allowed to process logs" issue.

Oddly, in WMH, when I look at

Statistics Software Configuration >See Specific User's Statistics Summary

for the specific account in question, the output lists all the sub domain accounts, but not the main one. So assuming the main domain should be listed there, then something is amiss.

 

[vexil]

Awstats missing on some accounts

In the last month (June 2008) we've had about 5 accounts on our server which have data missing for between 3 and 14 days from the awstats reports. Webalizer has all of the data, but for awstats it says 0 visits for a consecutive period of up to 2 weeks. It then appears to start working for most in late June, but some in early July.

In 'Statistics Software configuration' it says that the server is keeping up with the processing schedule.

Our clients are going crazy asking where are their statistics and they want an explanation. I'm desperately trying to work out what happened but I can't seem to find any clues...

 

[stuartmcdonald]

I raised a ticket with cPanel about this which concluded as follows:

"It does this that this has been addressed and was pushed out as a fix in the EDGE release currently. The specific build this was fixed in was build 25662+ "

While the above didn't detail what the problem was, it hasn't happened since, but I never did get the data for those couple of days -- weird.

 

[vexil]

Could be server load

The server has 2 cpus and the load is currently 2.04, although it fluctuates between 1.7 and 2.2 but perhaps when all the stats processing is happening the cpus can't keep up. I'm going to try to reduce the server load and hopefully that will eliminate the problem.