Re: Webalizer weirdness
Marcin got it, There were some IPv6 entries at the beginning of the
log file that seemed to be sending it of, I have removed the offending
entries and re run webalizer since.
http://www.lloydsenergy.co.uk/webalizer/usage_200707.html#TOPSITES
http://www.lloydsenergy.co.uk/webalizer/webalizer.conf
http://www.lloydsenergy.co.uk/logs/access.log
This one is doing the same but has no IPv6 entries in the log.
Everything is on sparc
Andrew
On 31/07/07, Martin <inkubus@interalpha.co.uk> wrote:
> On Mon, 2007-07-30 at 20:16 +0100, andrew holway wrote:
> > Hi,
> >
> > I've been asking in IRC and forums for some time but no one has been
> > able to help.
> >
> > Has anyone any ideas why this?
> > http://www.moonet.co.uk/webalizer/usage_200707.html#TOPSITES
> >
> > log is here http://www.moonet.co.uk/logs/access.log
> > and config is here http://www.moonet.co.uk/webalizer/webalizer.conf
> > webalizer is Webalizer V2.01-10 (Linux 2.6.18-028stab031.dev-ovz031) English
> > floating point conversion error?
> >
> > Linux daisy.moognu.co.uk 2.6.18-028stab031.dev-ovz031 #2 SMP Wed May
> > 30 10:45:50 BST 2007 sparc64 GNU/Linux
>
> Were all of the input data files generated on sparc64? I have seen
> strange things happen when parsing floating point numbers written on x86
> machines (as ASCII). I always assumed it was something to do with the
> x86 support for 80 bit long doubles (and the sometimes iffy support for
> 64 bit doubles) verses the SPARC support of 64 bit and (nominally) 128
> bit doubles.
>
> HTH,
>
> Cheers,
> - Martin
>
>
>
Reply to: