Michael
10-09-2001, 10:23 AM
We had webalizer 1.3 stop working on one of our RaQ4s. It runs every night although on the stats it does not show information as of October 4th. I checked all the web.log files and they are current.
Does anyone know what could be wrong or how this can be fixed?
Thanks
Mike
loryans
10-09-2001, 10:45 AM
That's really odd!
We're running Webalizer 2, (upgraded from 1.3), and ours also stopped working on October 4th.
I have checked the logs and everything is current.
I have also tried to manually run it, but no luck!
Michael
10-09-2001, 10:57 AM
Ok, I found the answer to I think the problems:
-- 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
-Notice-
Anyone know how to apply the patch?
The solution is to upgrade Webalizer to 2.01, remove all your statistics and then rerun Webalizer. (You'll sadly loose the old statistics).
Another way is manully fixing the source for webalizer 2.00 to work around the date/time overflow bug.
Note to our customers:
If you have had Webalizer installed by Mermaid Consulting in the past, please email me (jens@mermaidconsulting.com) - and I'll install a patch free of charge that lets you continue to run Webalizer without loosing your old stats.
iplexx
10-10-2001, 11:15 PM
What Cobalt pkg's did you install? see thread (http://www.webhostingtalk.com/showthread.php?s=&threadid=22827)
For me, it was webalizer-1.30.04.i386.pkg (filesize: 166920 bytes) which was avaible at pkg.nl.cobalt.com before the site redesign; the current avaible pkg is called webalizer-1.3.pkg (size: 166833 bytes) - it might be interesting to know what changed and if the newer pkg already includes the fix....
iplexx
10-10-2001, 11:36 PM
This is how I tried to patch webalizer, and it seems to work :)
1.) login via ssh, su to root
2.) create temporary directory, and cd to it
3.) wget ftp://ftp.mrunix.net/pub/webalizer/pre-release/v130-epoch.patch
4.) wget ftp://ftp.mrunix.net/pub/webalizer/old/webalizer-1.30-04-src.tgz
5.) tar xvfz webalizer-1.30-04-src.tgz
6.) cd webalizer-1.30-04
7.) patch webalizer.c ../v130-epoch.patch
8.) ./configure
9.) rm webalizer
10.) rm webalizer.o
11.) rm graphs.o
12.) make
13.) cp /usr/bin/webalizer /usr/bin/webalizer.old
14.) cp webalizer /usr/bin/
15.) /etc/cron.daily/webalizer.pl
:D
edit: fixed typos
yesyes
10-11-2001, 05:25 AM
I've installed webalizer-1.3.pkg (size: 166833 bytes)
this package have also the problem.
I will try your fix, thank you very much for it.
Hi there,
My webalizer 2.01-06 doesn't seem to work either.... can I upgrade this with the patch as well?
Will this keep the existing stats?
Thanks...
-dr
I manually uninstalled my old webalizer 1.30.04-1:
#rpm -e --nodeps webalizer-1.30.04-1
#rm -f /var/lib/cobalt/webalizer-1.30.04-1.md5lst
#rm -f /var/lib/cobalt/uninstallers/webalizer-1.0.uninst
#rm /etc/cron.daily/webalizer.pl
After that I grabbed a copy of the Webalizer 2.0.1 package from http://cobalt-aid.sourceforge.net/files and installed it.
Then I tried to run /etc/cron.daily/webalizer.pl but it didn't work yet :(
So I just downloaded the Webalizer 2.0.1 tarball from www.webalizer.com, untared it and copied the file webalizer into /usr/bin/ replacing the old one.
And guess what it's working fine now :)
btw for Webalizer 2 you need the GD and PNG library, so you should install them first if don't have them yet.
jnestor
10-12-2001, 11:56 AM
Thanks iplexx - worked like a charm.
You do still have a minor typo in the instructions though. #4 should be /pub/ not /pubc/
Wish I had found this a couple days ago since those logs are lost but it's nice to have the stats back again.
inoverse
10-12-2001, 05:39 PM
Yeah, same deal here...but how do we fix it? I can't seem to find a .pkg file for version 2. Does anyone know where I can find one or how to fix the stall on version 1?