iVersit
10-09-2001, 05:33 AM
Webalizer just quit producing new html stats on Oct. 4. Any ideas?
Here is the mail I get:
Frontpage ENABLED on /home/sites/www.****.com/web
25763 records (1788 ignored) in 3.92 seconds, 6572/sec
Frontpage NOT ENABLED on /home/sites/www.****.com/web
6786 records (265 ignored) in 2.74 seconds, 2476/sec
I've restarted apache, should i go ahead and change the order of cron.daily to run webalizer.pl before logrotate..will that fix the problem??
No, that will not fix the problem.
It's due to an overflow bug in Webalizer - so the only solution is to upgrade your Webalizer to a new version.
See www.mrunix.net/webalizer/ for more info and downloads.
Michael
10-09-2001, 11:58 AM
I just found this thread that may help you patch it:
-- Notice --
Older versions of the Webalizer (Ver 1.30 thru 2.00-12) generated
timestamps in a fashion that, on most platforms, would overflow on
October 5, 2001. The result is that statistics are generated up
until midnight of October 4th, but not after. This problem does not
exist in the current release (V2.01) of the Webalizer, which has been
available for over a year now. If you cannot upgrade or wish to
continue using the older version, there is a patch on our ftp site
that will extend the usable date range for three more years, however
will prevent logs before 1993 from being processed. It can be found
at:
ftp://ftp.mrunix.net/pub/webalizer/pre-release/v130-epoch.patch
Mike
iVersit
10-09-2001, 05:41 PM
Do I gcc compile that patch or what?
Originally posted by Orpheus1539
Do I gcc compile that patch or what?
No.
You need to download the v. 1.30 source and then run the patch command on that file above (put the patch file in the same dir as the sources).
Afterwards compile webalizer as normally.
The patch above will not work out-of-the-box with Webalizer 2.00.