mickalo

Well-Known Member
Apr 16, 2002
782
5
318
N.W. Iowa
We have approximately 50 accounts, and one of the accounts stopped recording on 11/8 for all web stats, webalizer, urchin,...etc, and we've tried running the stats through the main admin, and nothing so far we've tried seems to get their stats up-to-date. It just stops at 11/8 and nothing else is recorded after that date!

I have tried going into their profile and "running the stats now" and it just hangs at "Pending 0%" and nothing happens... is it possible the log file is corrupted ??

This is the output from running the utility script "runweblogs "

Code:
/scripts/runweblogs etfdiges
Log checker loaded ok..
==> Loading Config (cpanellogd) .... Done
==> cpaneld(logger) 8.0 Starting (4 processor system).....
==> Shared RRDTOOL support enabled
Processing etfdiges...
Run Logs etfdiges,etfdigest.com,3145728000,
LANGUAGE: english /usr/local/cpanel/lang/.english
Update status for /var/cpanel/bandwidth/etfdiges-http.rrd: (266) 
Processing exim stats for etfdiges.......Done
Update status for /var/cpanel/bandwidth/etfdiges-all.rrd: (266) 
LANGUAGE: english /usr/local/cpanel/lang/.english
Archive Status: 0
------------------------------------------------------
Urchin 5.1.01 (redhat72) starting: 20031112 11:32:56
------------------------------------------------------
Processing profile: etfdigest.com

[11:32:56] Logfile: /usr/local/apache/domlogs/etfdigest.com
   data lines: 0 (0%)           
ERROR: (7008-54-489) DB file is the wrong size - run sanitizer.
DETAIL: No such file or directory


------------------------------------------------------
Urchin 5.1.01 (redhat72) finishing: 20031112 11:32:56
------------------------------------------------------
About to fork() [ALL DOMAINS: ]
Webalizer V2.01-10 (Linux 2.4.20-20.7smp) English
Using logfile /usr/local/apache/domlogs/etfdigest.com (clf)
DNS Lookup (10): 109 addresses in 16.26 seconds, 6/sec
Using DNS cache file /home/etfdiges/tmp/webalizer/dns_cache.db
Creating output in /home/etfdiges/tmp/webalizer
Hostname for reports is 'etfdigest.com'
Reading history file... webalizer.hist
Reading previous run data.. webalizer.current
Error: Unable to restore run data (12)
Update for config "/home/etfdiges/tmp/awstats/awstats.etfdigest.com.conf"
With data in log file "/usr/local/apache/domlogs/etfdigest.com"...
Warning: HostAliases parameter is not defined, awstats choose "etfdigest.com localhost 127.0.0.1".
Phase 1 : First bypass old records, searching new record...
Direct access to last remembered record has fallen on another record.
So searching new records from beginning of log file...
Phase 2 : Now process new records (Flush history on disk after 20000 hosts)...
Jumped lines in file: 0
Parsed lines in file: 6094
 Found 2 dropped records,
 Found 0 corrupted records,
 Found 0 old records,
 Found 6092 new qualifed records.
Webalizer V2.01-10 (Linux 2.4.20-20.7smp) English
Using logfile /usr/local/apache/domlogs/ftp.etfdigest.com-ftp_log (ftp)
DNS Lookup (10): None to process
Using DNS cache file /home/etfdiges/tmp/webalizerftp/dns_cache.db
Creating output in /home/etfdiges/tmp/webalizerftp
Hostname for reports is 'ftp.etfdigest.com'
Reading history file... webalizer.hist
Reading previous run data.. webalizer.current
Error: Unable to restore run data (12)
Complete
it appears there is something wrong with their db log file, nothing is being written to it. it appears to have the correct file premission settings too.

Our is there something I'm missing here ??

thx's
Mickalo
 

B12Org

Well-Known Member
Jul 15, 2003
691
1
168
Seattle Washington
cPanel Access Level
Root Administrator
If its a database file, (in mysql) then try doing a repair on the databse. There is a script you can run to reset the stats for a certain user as well, dont remember it off the top of my head, but it should be noticeable. You can always remove the stats stuff in the tweak settings, and then do an update, then put them back on and do another update and see if it works after that.

update means:
/scripts/updatenow
/scripts/sysup
/scripts/upcp
/scripts/updateuserdomains2
service cpanel stop;service cpanel start
 

mickalo

Well-Known Member
Apr 16, 2002
782
5
318
N.W. Iowa
Originally posted by B12Org
If its a database file, (in mysql) then try doing a repair on the databse. There is a script you can run to reset the stats for a certain user as well, dont remember it off the top of my head, but it should be noticeable. You can always remove the stats stuff in the tweak settings, and then do an update, then put them back on and do another update and see if it works after that.

update means:
/scripts/updatenow
/scripts/sysup
/scripts/upcp
/scripts/updateuserdomains2
service cpanel stop;service cpanel start
thx's for the feedback. after a little more digging we found that the urching scheduler had stopped, so we restarted it, hopefully that will take care of the urchin stats.

I recall there is a script to run an individual account webalizer stats to get it back up to date, I believe it's called the /scripts/runweblogs <account_username> which we did run. I hope this also brings their webalizer stats back up to speed.

thx's
Mickalo