Webalizer needs manual start every day

[geeza@]

Hi all,
My webalizer has stopped working for all domains (I think after I applied the hotfixes for my os version). If I run

/usr/local/psa/admin/sbin/statistics

the stats for the past day will then be updated for the day. The info I get when this is run is

Creating output in /usr/local/psa/home/vhosts/exampledomain.com/statistics/webstat-ssl
Hostname for reports is 'exampledomain.com/'
History file not found...
Previous run data not found...
No valid records found!
Webalizer V2.01-10 (FreeBSD 5.3-RELEASE-p20) English
Using logfile STDIN (ftp)
Using DNS cache file /usr/local/psa/var/webalizer.cache
Creating output in /usr/local/psa/home/vhosts/exampledomain.com//statistics/anon_ftpstat
Hostname for reports is 'exampledomain.com/'
History file not found...
Previous run data not found...
No valid records found!
Webalizer V2.01-10 (FreeBSD 5.3-RELEASE-p20) English
Using logfile STDIN (ftp)
Using DNS cache file /usr/local/psa/var/webalizer.cache
Creating output in /usr/local/psa/home/vhosts/exampledomain.com/statistics/ftpstat
Hostname for reports is 'exampledomain.com'
Reading history file... webalizer.hist
Reading previous run data.. webalizer.current
No valid records found!

I get this same output for all domians and have to manually run /usr/local/psa/admin/sbin/statistics to get the previous days stats . Does anyone have any idea what is wrong here? By the way the cronjob is running everyday for statistics.

/usr/local/psa/admin/sbin/statistics >/dev/null 2>&1

Any help is much appreciated

 

[arisk2]

I have the same problem after migrating.
Have you managed to find a solution?

Any help would be appreciated.

 

[geeza@]

With my problem above there were 2 issues. I had the backup Cronjob running at virtually the same time as the statistics Cronjob accidentally. This was causing a conflict.

After fixing this by changing the Cronjob timing, I ran /usr/local/psa/admin/sbin/statistics (manually via SSH) a couple of times to put the stats back in sync (as some were a day or two behind).

By the way the 'no valid records found' is not an error. This always happens when the statistics are manually run.


Hope this helps

 

[arisk2]

Thanks

The only thing I see running that might conflict is the backupmng set for Min*/15.

Could this be conflicting?

 

[geeza@]

it doesn't look like that would cause you any problems. When you run the statistics manually do they update properly?

 

[arisk2]

As far as I can tell yes.
Through webalizer everything seems ok for the domains I have checked.

????

Any chance you know which logs I should be looking in for any info on the cron job?

 

[mlatzel]

Same problem here

Hello,

we have the same problem. Current root crontab:

        14      5       *       *       *       /usr/local/psa/bin/mysqldump.sh >/dev/null 2>&1
        7       4       *       *       *       /usr/local/psa/admin/sbin/statistics >/dev/null 2>&1
        */15    *       *       *       *       /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1

Have to manually run statistics every morning to update the log stats. Other cron jobs execute fine.

Any idea?

 

[jamesyeeoc]

To see the errors when the statistics cronjob runs, you can remove the >/dev/null, and define a MAILTO address for cron.

Or replace the /dev/null with a valid path/filename to a custom logfile name of your choosing, then you can check it for any specific output from that command running.

 

[mlatzel]

Hi jamesyeeoc,

thanks, I replaced crontab entry with

        22      10       *       *       *       /usr/local/psa/admin/sbin/statistics > /root/stats.log 2>&1

and waiting for something to happen, but - nothing! No log file is created. Also tried having the results emailed to me.

This is really weird.
Any idea?

 

[jamesyeeoc]

1. First use 'touch' from an SSH prompt to create an empty file with that name:

[b]touch /root/stats.log[/b]

2. I don't know if the space after the '>' makes a difference, I never put one, so you might try removing it.

[b]   22      10       *       *       *       /usr/local/psa/admin/sbin/statistics >/root/stats.log 2>&1[/b]

And you want this to run at 10:22am each day? At least that's what you have listed right now.

Min     H     DM     M     DW     Command

If you wanted it to run at 10:10pm, then you would have

[b]   10      22       *       *       *       /usr/local/psa/admin/sbin/statistics >/root/stats.log 2>&1[/b]

Since 10pm is 22:00hrs (just checking since I don't know too many people who run the stats in the mornings...

 

[bplinson]

I also have the same problem after upgrading to 8.0.0.

Any solution yet?

 

[bplinson]

I just noticed that this is only happening to one of my domains. Now I am really stumped.

 

[jamesyeeoc]

If it's only affecting a single domain, have you tried turning off statistics in the control panel, saving, then turning them back on and saving? Sometimes the Plesk database gets messed up and you have to toggle settings. Did I mention I hate upgrading...

 

[bplinson]

I get this error when running the statistics script manually

~snip~
'mycrappywebsite.com'
Reading history file... webalizer.hist
Reading previous run data.. webalizer.current
[new_unode] Warning: String exceeds storage size (277)
[new_unode] Warning: String exceeds storage size (276)
[new_unode] Warning: String exceeds storage size (275)
[new_unode] Warning: String exceeds storage size (274)
[new_unode] Warning: String exceeds storage size (273)
[new_unode] Warning: String exceeds storage size (272)
[new_unode] Warning: String exceeds storage size (271)
[new_unode] Warning: String exceeds storage size (270)
[new_unode] Warning: String exceeds storage size (269)
[new_unode] Warning: String exceeds storage size (268)
[new_unode] Warning: String exceeds storage size (267)
[new_unode] Warning: String exceeds storage size (266)
[new_unode] Warning: String exceeds storage size (265)
[new_unode] Warning: String exceeds storage size (264)
[new_unode] Warning: String exceeds storage size (263)
[new_unode] Warning: String exceeds storage size (262)
[new_unode] Warning: String exceeds storage size (261)
[new_unode] Warning: String exceeds storage size (260)
[new_unode] Warning: String exceeds storage size (259)
[new_unode] Warning: String exceeds storage size (258)
[new_unode] Warning: String exceeds storage size (257)
[new_unode] Warning: String exceeds storage size (256)
[new_unode] Warning: String exceeds storage size (255)
[new_unode] Warning: String exceeds storage size (254)
[new_unode] Warning: String exceeds storage size (253)
[new_unode] Warning: String exceeds storage size (252)
[new_unode] Warning: String exceeds storage size (251)
[new_unode] Warning: String exceeds storage size (250)
[new_unode] Warning: String exceeds storage size (249)
[new_unode] Warning: String exceeds storage size (248)
[new_unode] Warning: String exceeds storage size (247)
[new_unode] Warning: String exceeds storage size (246)
[new_unode] Warning: String exceeds storage size (245)
[new_unode] Warning: String exceeds storage size (244)
[new_unode] Warning: String exceeds storage size (243)
[new_unode] Warning: String exceeds storage size (242)
[new_unode] Warning: String exceeds storage size (241)
[new_unode] Warning: String exceeds storage size (240)
[new_unode] Warning: String exceeds storage size (239)
[new_unode] Warning: String exceeds storage size (238)
[new_unode] Warning: String exceeds storage size (237)
[new_unode] Warning: String exceeds storage size (236)
[new_unode] Warning: String exceeds storage size (235)
[new_unode] Warning: String exceeds storage size (234)
[new_unode] Warning: String exceeds storage size (233)
[new_unode] Warning: String exceeds storage size (232)
[new_unode] Warning: String exceeds storage size (231)
[new_unode] Warning: String exceeds storage size (230)
[new_unode] Warning: String exceeds storage size (229)
No valid records found!
Webalizer V2.01-10 (Linux 2.6.11.4-21.7-smp) English
Using logfile STDIN (clf)
DNS Lookup (15): None to process
Webalizer V2.01-10 (Linux 2.6.11.4-21.7-smp) English
Using logfile STDIN (clf)
DNS Lookup (15): None to process
Webalizer V2.01-10 (Linux 2.6.11.4-21.7-smp) English
Using logfile STDIN (ftp)
DNS Lookup (15): None to process
Webalizer V2.01-10 (Linux 2.6.11.4-21.7-smp) English
Using logfile STDIN (ftp)
DNS Lookup (15): None to process
Webalizer V2.01-10 (Linux 2.6.11.4-21.7-smp) English
Using logfile STDIN (clf)
Using DNS cache file /usr/local/psa/var/lib/webalizer/webalizer.cache
Creating output in /home/www/vhosts/the-sphincter.com/statistics/webstat
Hostname for reports is 'the-sphincter.com'
Reading history file... webalizer.hist
Reading previous run data.. webalizer.current
No valid records found!
Webalizer V2.01-10 (Linux 2.6.11.4-21.7-smp) English
Using logfile STDIN (clf)
Using DNS cache file /usr/local/psa/var/lib/webalizer/webalizer.cache
Creating output in /home/www/vhosts/the-sphincter.com/statistics/webstat-ssl
Hostname for reports is 'the-sphincter.com'
History file not found...
Previous run data not found...
No valid records found!
Webalizer V2.01-10 (Linux 2.6.11.4-21.7-smp) English
Using logfile STDIN (ftp)
Using DNS cache file /usr/local/psa/var/lib/webalizer/webalizer.cache
Creating output in /home/www/vhosts/the-sphincter.com/statistics/anon_ftpstat
Hostname for reports is 'the-sphincter.com'
History file not found...
Previous run data not found...
No valid records found!
Webalizer V2.01-10 (Linux 2.6.11.4-21.7-smp) English
Using logfile STDIN (ftp)
Using DNS cache file /usr/local/psa/var/lib/webalizer/webalizer.cache
Creating output in /home/www/vhosts/the-sphincter.com/statistics/ftpstat
Hostname for reports is 'the-sphincter.com'
Reading history file... webalizer.hist
Reading previous run data.. webalizer.current
[new_unode] Warning: String exceeds storage size (277)
[new_unode] Warning: String exceeds storage size (276)
[new_unode] Warning: String exceeds storage size (275)
[new_unode] Warning: String exceeds storage size (274)
[new_unode] Warning: String exceeds storage size (273)
No valid records found!
statistics: Unable to get database status for "v2-forumphoto": You have an error                                                                                                  in your SQL syntax; check the manual that corresponds to your MySQL server vers                                                                                                 ion for the right syntax to use near '-forumphoto' at line 1
statistics: Unable to get database status for "v2-forumphoto": You have an error                                                                                                  in your SQL syntax; check the manual that corresponds to your MySQL server vers                                                                                                 ion for the right syntax to use near '-forumphoto' at line 1
su93159:/usr/local/psa/admin/sbin # statistics: Unable to get database status for "v2-forumphoto": You have an error                                                                                                  in your SQL syntax; check the manual that corresponds to your MySQL server vers                                                                                                 ion for the right syntax to use near '-forumphoto' at line 1
bash: statistics:: command not found
bash: check: command not found
su93159:/usr/local/psa/admin/sbin # statistics: Unable to get database status for "v2-forumphoto": You have an error                                                                                                  in your SQL syntax; check the manual that corresponds to your MySQL server vers                                                                                                 ion for the right syntax to use near '-forumphoto' at line 1

I went ahead and disabled the stats for v2-forum.com since that is where I am thinking the error is but it is xlforum.net that the stats are no longer showing up one.