Klaus,

I had tried your first suggestion before, and it failed in exactly the
same way; however, your second suggestion did the trick.

I commented out DNSCache and DNSChildren, and stdin worked perfectly.
So, I'll make two passes in my script.  One will be as Webazolver to
build the cache file, and a second to create the report.

Thanks very much for your quick response.

Regards,
Mike




--- In webalizer@y..., Klaus Mueller <k.mueller@i...> wrote:
> >  # /usr/local/bin/webalizer < ShortTest.log
> >  Webalizer V2.01-06 (SunOS 5.8) English
> >  Using logfile STDIN (clf)
> >  DNS Lookup (30): 10 addresses in 0.13 seconds
>
> 1. Can you try:
> cat ShortTest.log| /usr/local/bin/webalizer -
>
> I have no unix box to test this.
>
> 2. What happens if you disable the DNS cache?
> Reason: The webalizer parses the log file two times if DNS lookup is
> enabled. Webalizer calls itself as webazolver (?) and use pipes to
process
> the DNS lookup. The log creation is a second step. The second step
my fail
> if running from command line because the input pipe is readed but no
log
> entries for further processing exists. This is an assumption only.
>
> Bye
> Klaus

Can you send a bug report to Bradford (brad@...) with a description
please?

Bye
Klaus

> -----Original Message-----
> From: miparke@... [mailto:miparke@...]
> Sent: Tuesday, October 02, 2001 6:51 PM
> To: webalizer@yahoogroups.com
> Subject: [webalizer] Re: Problem using stdin on Solaris 8
>
>
> Klaus,
>
> I had tried your first suggestion before, and it failed in exactly the
> same way; however, your second suggestion did the trick.
>
> I commented out DNSCache and DNSChildren, and stdin worked perfectly.
> So, I'll make two passes in my script.  One will be as Webazolver to
> build the cache file, and a second to create the report.
>
> Thanks very much for your quick response.
>
> Regards,
> Mike
>
>
>
>
> --- In webalizer@y..., Klaus Mueller <k.mueller@i...> wrote:
> > >  # /usr/local/bin/webalizer < ShortTest.log
> > >  Webalizer V2.01-06 (SunOS 5.8) English
> > >  Using logfile STDIN (clf)
> > >  DNS Lookup (30): 10 addresses in 0.13 seconds
> >
> > 1. Can you try:
> > cat ShortTest.log| /usr/local/bin/webalizer -
> >
> > I have no unix box to test this.
> >
> > 2. What happens if you disable the DNS cache?
> > Reason: The webalizer parses the log file two times if DNS lookup is
> > enabled. Webalizer calls itself as webazolver (?) and use pipes to
> process
> > the DNS lookup. The log creation is a second step. The second step
> my fail
> > if running from command line because the input pipe is readed but no
> log
> > entries for further processing exists. This is an assumption only.
> >
> > Bye
> > Klaus
>
>
> ------------------------ Yahoo! Groups Sponsor
> ---------------------~-->
> Get your FREE VeriSign guide to security solutions for your
> web site: encrypting transactions, securing intranets, and more!
> http://us.click.yahoo.com/UnN2wB/m5_CAA/yigFAA/NhFolB/TM
> --------------------------------------------------------------
> -------~->
>
> To unsubscribe from this group, send an email to:
> webalizer-unsubscribe@egroups.com
> Webalizer homepage: http://www.webalizer.org
> Webalizer for NT: http://www.medasys-lille.com/webalizer/
>
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/

Done.

Regards,
Mike


--- In webalizer@y..., Klaus Mueller <k.mueller@i...> wrote:
> Can you send a bug report to Bradford (brad@m...) with a description
> please?
>
> Bye
> Klaus
>
> > -----Original Message-----
> > From: miparke@y... [mailto:miparke@y...]
> > Sent: Tuesday, October 02, 2001 6:51 PM
> > To: webalizer@y...
> > Subject: [webalizer] Re: Problem using stdin on Solaris 8
> >
> >
> > Klaus,
> >
> > I had tried your first suggestion before, and it failed in exactly
the
> > same way; however, your second suggestion did the trick.
> >
> > I commented out DNSCache and DNSChildren, and stdin worked
perfectly.
> > So, I'll make two passes in my script.  One will be as Webazolver
to
> > build the cache file, and a second to create the report.
> >
> > Thanks very much for your quick response.
> >
> > Regards,
> > Mike
> >
> >
> >
> >
> > --- In webalizer@y..., Klaus Mueller <k.mueller@i...> wrote:
> > > >  # /usr/local/bin/webalizer < ShortTest.log
> > > >  Webalizer V2.01-06 (SunOS 5.8) English
> > > >  Using logfile STDIN (clf)
> > > >  DNS Lookup (30): 10 addresses in 0.13 seconds
> > >
> > > 1. Can you try:
> > > cat ShortTest.log| /usr/local/bin/webalizer -
> > >
> > > I have no unix box to test this.
> > >
> > > 2. What happens if you disable the DNS cache?
> > > Reason: The webalizer parses the log file two times if DNS
lookup is
> > > enabled. Webalizer calls itself as webazolver (?) and use pipes
to
> > process
> > > the DNS lookup. The log creation is a second step. The second
step
> > my fail
> > > if running from command line because the input pipe is readed
but no
> > log
> > > entries for further processing exists. This is an assumption
only.
> > >
> > > Bye
> > > Klaus
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> > ---------------------~-->
> > Get your FREE VeriSign guide to security solutions for your
> > web site: encrypting transactions, securing intranets, and more!
> > http://us.click.yahoo.com/UnN2wB/m5_CAA/yigFAA/NhFolB/TM
> > --------------------------------------------------------------
> > -------~->
> >
> > To unsubscribe from this group, send an email to:
> > webalizer-unsubscribe@egroups.com
> > Webalizer homepage: http://www.webalizer.org
> > Webalizer for NT: http://www.medasys-lille.com/webalizer/
> >
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/

I used webalizer flawlessly for at least 8 months through cron (linux
mandrake 7.2) and the past month or so i noticed the reports were not
being updated.  Now i get a segmentation fault(core dumped) error
when i run webalizer from the command line.  On some of my virtual
host logs i get this:

Warning: Truncating oversized username
Skipping bad record (574)


Any help or suggestions would be greatly appreciated.

Folks,

Just set up webalizer/win32. After finally understanding the sample.conf
file, here's what I got.

I"m running NT40/IIS40 Frontpage enabled boxes. This is my setup for IIS.

Create a folder in \Inetpub\webalizer
Unzip the webalizer-w32 into that folder.

open sample.conf into Notepad and Save As webalizer.conf
open Notepad again and create a xxxxxx.txt file.
You can name it whatever you like. I choose listserv.txt

If your hosted domain folders are, for example:

  C:\Inetpub\wwwroot\domainname-folder

create a new directory named "usage", as in,

C:\Inetpub\wwwroot\domainname-folder\usage

Open MMC and find the domain you are working with. Right click the
domain name and select properties.
Select Enable Logging and "USE" NSCA Common Log File Format. Then select
the Advanced button and get the W3svc number.

OK out and back to the webalizer.conf file.

As a base setup, you only need four lines of information.

Logging
FolderLog
ExtentionLog
ServerList

Default NT/IIS installs Logs @ \winnt\system32\LogFiles\W3svc*
So in this case you would have,

Logging CFL ( this is for the NCSA Apache style logging and best bet)
FolderLog     C:\winnt\system32\Logfiles\ ( no need to specify the W3svc
folder)
ExtentionLog    log (obvious)
ServerList    you'retextfile.txt  (listserv.txt)

OK, To the listserv.txt file. This is where webalizer looks to find and
then create the proper logs and then where to put them.

The sample file is very correct.
Here is a sample based upon the selected information above:

wa001 C:\winnt\system32\Logfiles\W3svc*
C:\Inetpub\wwwroot\foldernameofdomain\usage
wa001.domainname.com;www.domainname.com

To add a second domain :

wa002 C:\winnt\system32\Logfiles\W3svc*
C:\Inetpub\wwwroot\foldernameofdomain\usage
wa002.domainname.com;www.domainname.com

ad infinitum.....

How it breaks out.

wa001 is just a pointer to let webalizer put "multple" domains in some
order.
C:\winnt\system32\Logfiles\W3svc* = path to absolute logfile for this domain
C:\Inetpub\wwwroot\foldername\usage = absolute path to the domain folder
wa001.domainname.com = heres the flag
www.domainname.com = this is printed in the resulting html page at the top.

The asterik in the W3svc* is determined by IIS. So be sure you have this
correct.

After y ou have all your settings, run webalizer.exe.
Webalizer will parse the webalizer.conf file, which you told to go look
at listserv.txt.
Webalizer will go right down the list as you have it.

If you receive error messages, then you can figure you log file is
trashed.  Webalizer cannot interpret, http requests made by code red
worm, blue worm or nimda or any other IIS attack.
Check your log files for the these request, they stand out like a sore
thumb.

Dump the logs and start fresh. Hope this helps the NT folks.

Later

lcjones@...
seit - noc

Are you still looking, I'm a RaQ3 & 4i owner/user and have webalizer
2.01 installed.
PG (RaQ35)


--- In webalizer@y..., yahoo@c... wrote:
> I'm looking to hire someone to install webalizer on my Cobalt
> RaQ 3 server.
>
>                             leah@c...
>
>                             I'm new at administering the RaQ 3 and
am in
> too much of a hurry to mess up the installation

Dear Webalizer Enthusiasts,

I've been using webalizer for about 18 months on my site
gimp-savvy.com without a single problem.  Using a cron job I do a log
rotate every day at midnight and run webalizer in incremental mode
using the command:

webalizer -Q -C 100 -p -l 9 access_log_url

However, suddenly, two days ago, the stats on my site ceased to be
updated (see http://gimp-savvy.com/STATS).  I assembled the necessary
files to run a test with debugging turned on, and the output is:

Webalizer V1.30-04 (Linux 2.2.12-20) English
Using logfile /home/cbunks/TEST/access
Creating output in /home/cbunks/TEST/STATS/
Hostname for reports is 'etoile'
Reading history file... webalizer.hist
Reading previous run data.. webalizer.current
209048 records (209048 ignored) in 21.80 seconds, 9589/sec

With all the records ignored, I suspected a problem with the time
stamp, so I looked in the webalizer.current file, and the top two
lines of this file contain:

# Webalizer V1.30-04 Incremental Data - 10/04/2001 23:58:50
2001 10 4 23 58 50

This (2001 10 4 23 58 50) looks like the time stamp to me, so I also
look in the first access_log that no longer is analyzed, and the first
line of the file is:

216.16.23.88 - - [05/Oct/2001:00:00:27 -0400] "GET /BOOK/node41.html
HTTP/1.1" 200 8656 "http://gimp-savvy.com/BOOK/Grokking_the_GIMP.html"
"Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)"

all the others lines have later dates, so the time stamp problem
hypothesis seems false.  I've diddled around with a few other
possibilities, but I haven't found the solution to my problem.  Can
anyone suggest a test or tell me what I'm doing wrong?

Anyone suggestions would be welcome.

Cheers,

Carey Bunks

=============================
Carey Bunks
author of "Grokking the GIMP"
maintainer of Gimp-Savvy.com
email:  careybunks@...
=============================

I am having the exact replica of Carey's problem described in the
post before me. (Different servers of course). We have the exact same
setup (same for over 1 yr) and it died on the 4th of october. Why?
and what is the fix? I know if I remove the webalizer.history it is
fixed but i dont want to loose all of my prior data.

Thanks!

James R. Clark II
Nethosters, Inc.
http://www.nethosters.com

-----Original Message-----
From: jic_99@... [mailto:jic_99@...]
Sent: maandag 8 oktober 2001 9:10
To: webalizer@yahoogroups.com
Subject: [webalizer] Problem with Incremental Update also

I am having the exact replica of Carey's problem described in the
post before me. (Different servers of course). We have the exact same
setup (same for over 1 yr) and it died on the 4th of october. Why?
and what is the fix? I know if I remove the webalizer.history it is
fixed but i dont want to loose all of my prior data.

Thanks!

James R. Clark II
Nethosters, Inc.
http://www.nethosters.com



To unsubscribe from this group, send an email to:
webalizer-unsubscribe@egroups.com
Webalizer homepage: http://www.webalizer.org
Webalizer for NT: http://www.medasys-lille.com/webalizer/




Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Nick,

I am positive that when I removed webalizer.current /
webalizer.history it fixed it. I have a crontab setup so that each
domain only has 1 log and when the log is analyzed it is tarred up
into a larger .tar file with all of the old logs in it.

JC

--- In webalizer@y..., "Nick Heinemans" <spam@h...> wrote:
> Hi all,
>
> Are you sure the problem will be fixed if you remove
webalizer.history? I
> experienced this kind of problem on a win2k IIS webserver, and it
turned out
> webalizer cannot analyze more than 250 log files in one directory.
I'm not
> sure if it's the same for the *nix flavours of webalizer, but it
could be
> the case.
>
> I solved my problem by merging the older logfiles into one logfile.
This
> decreased the number of files, so solved the problem. I already had
cygwin
> installed, so I could easily do a "cat log1.log >> biglog.log" "cat
log2.log
> >> biglog.log".
>
> Nick
>   -----Original Message-----
>   From: jic_99@y... [mailto:jic_99@y...]
>   Sent: maandag 8 oktober 2001 9:10
>   To: webalizer@y...
>   Subject: [webalizer] Problem with Incremental Update also
>
>
>   I am having the exact replica of Carey's problem described in the
>   post before me. (Different servers of course). We have the exact
same
>   setup (same for over 1 yr) and it died on the 4th of october. Why?
>   and what is the fix? I know if I remove the webalizer.history it
is
>   fixed but i dont want to loose all of my prior data.
>
>   Thanks!
>
>   James R. Clark II
>   Nethosters, Inc.
>   http://www.nethosters.com
>
>
>         Yahoo! Groups Sponsor
>
>
>
>   To unsubscribe from this group, send an email to:
>   webalizer-unsubscribe@egroups.com
>   Webalizer homepage: http://www.webalizer.org
>   Webalizer for NT: http://www.medasys-lille.com/webalizer/
>
>
>
>
>   Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.

On Mon, Oct 08, 2001 at 07:09:35AM -0000, jic_99@... wrote:

> I am having the exact replica of Carey's problem described in the
> post before me. (Different servers of course). We have the exact same
> setup (same for over 1 yr) and it died on the 4th of october. Why?
> and what is the fix? I know if I remove the webalizer.history it is
> fixed but i dont want to loose all of my prior data.

I have the same problem, and perhaps it  is in the date
itself. I have tried to start the data from 1st of october, and the problem
persists.


I'm using version 1.3x. Anybody knows a bug with specific dates ?

--
-----BEGIN GEEK CODE BLOCK-----
Version: 4.0
GCS/IT/S d- s+++:+++ a-- C++++ UL++++$ PL++ E- W+@ N- o?
k? w O+@ M-- V? PS++@ PE--(-) Y+(++) PGP t(+) 5++ X++++
R-() tv- b+++(++++) DID++ G++ e h! r++(+++) z+>+++
------END GEEK CODE BLOCK------
? quieres saber qui es el geek code ? http://www.geekcode.com

I haven't had the problem, Webalizer has run fine the past week. I'm using
it on a Win2k server with IIS logs, so maybe it's a "platform-local"
problem?

- Carsten


----- Original Message -----
From: "Hilario Ortigosa Monteoliva" <sonicrave@...>
To: <webalizer@yahoogroups.com>
Sent: Monday, October 08, 2001 9:54 AM
Subject: Re: [webalizer] Problem with Incremental Update also


> On Mon, Oct 08, 2001 at 07:09:35AM -0000, jic_99@... wrote:
>
> > I am having the exact replica of Carey's problem described in the
> > post before me. (Different servers of course). We have the exact same
> > setup (same for over 1 yr) and it died on the 4th of october. Why?
> > and what is the fix? I know if I remove the webalizer.history it is
> > fixed but i dont want to loose all of my prior data.
>
> I have the same problem, and perhaps it  is in the date
> itself. I have tried to start the data from 1st of october, and the
problem
> persists.
>
>
> I'm using version 1.3x. Anybody knows a bug with specific dates ?
>
> --
> -----BEGIN GEEK CODE BLOCK-----
> Version: 4.0
> GCS/IT/S d- s+++:+++ a-- C++++ UL++++$ PL++ E- W+@ N- o?
> k? w O+@ M-- V? PS++@ PE--(-) Y+(++) PGP t(+) 5++ X++++
> R-() tv- b+++(++++) DID++ G++ e h! r++(+++) z+>+++
> ------END GEEK CODE BLOCK------
> ? quieres saber qui es el geek code ? http://www.geekcode.com
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> webalizer-unsubscribe@egroups.com
> Webalizer homepage: http://www.webalizer.org
> Webalizer for NT: http://www.medasys-lille.com/webalizer/
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>

I have the same problem, too. According to run time message, all data after
Oct. 4 are not processed. The screen says 17538 records (21378 ignored) in
5.0 seconds....
However, if I process data after Oct. 4 dedicatedly, it works normally. Ot
just cannot accept log file containing data before Oct. 4 and after. Why?
Weird!

Shiann-Liang Chern

----- Original Message -----
From: "Hilario Ortigosa Monteoliva" <sonicrave@...>
To: <webalizer@yahoogroups.com>
Sent: Monday, October 08, 2001 3:54 PM
Subject: Re: [webalizer] Problem with Incremental Update also


> On Mon, Oct 08, 2001 at 07:09:35AM -0000, jic_99@... wrote:
>
> > I am having the exact replica of Carey's problem described in the
> > post before me. (Different servers of course). We have the exact same
> > setup (same for over 1 yr) and it died on the 4th of october. Why?
> > and what is the fix? I know if I remove the webalizer.history it is
> > fixed but i dont want to loose all of my prior data.
>
> I have the same problem, and perhaps it  is in the date
> itself. I have tried to start the data from 1st of october, and the
problem
> persists.
>
>
> I'm using version 1.3x. Anybody knows a bug with specific dates ?
>
> --
> -----BEGIN GEEK CODE BLOCK-----
> Version: 4.0
> GCS/IT/S d- s+++:+++ a-- C++++ UL++++$ PL++ E- W+@ N- o?
> k? w O+@ M-- V? PS++@ PE--(-) Y+(++) PGP t(+) 5++ X++++
> R-() tv- b+++(++++) DID++ G++ e h! r++(+++) z+>+++
> ------END GEEK CODE BLOCK------
> ? quieres saber qui es el geek code ? http://www.geekcode.com
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> webalizer-unsubscribe@egroups.com
> Webalizer homepage: http://www.webalizer.org
> Webalizer for NT: http://www.medasys-lille.com/webalizer/
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

I just checked a brand new server with a fresh install of webalizer
(15-20 days old). Its stats died on the 4th of October.

hello

I make some work on webalizer,
i'm shure there is bug on kernel 1.3 of webalizer, somes systems have this
trouble but in new release, i think all work fine.

check version of webalizer, and upgrade if you can to 2.XX version

good luck to all
regards

-----Message d'origine-----
De : Hilario Ortigosa Monteoliva [mailto:sonicrave@...]
Envoye : lundi 8 octobre 2001 09:54
A : webalizer@yahoogroups.com
Objet : Re: [webalizer] Problem with Incremental Update also


On Mon, Oct 08, 2001 at 07:09:35AM -0000, jic_99@... wrote:

> I am having the exact replica of Carey's problem described in the
> post before me. (Different servers of course). We have the exact same
> setup (same for over 1 yr) and it died on the 4th of october. Why?
> and what is the fix? I know if I remove the webalizer.history it is
> fixed but i dont want to loose all of my prior data.

I have the same problem, and perhaps it  is in the date
itself. I have tried to start the data from 1st of october, and the problem
persists.


I'm using version 1.3x. Anybody knows a bug with specific dates ?

--
-----BEGIN GEEK CODE BLOCK-----
Version: 4.0
GCS/IT/S d- s+++:+++ a-- C++++ UL++++$ PL++ E- W+@ N- o?
k? w O+@ M-- V? PS++@ PE--(-) Y+(++) PGP t(+) 5++ X++++
R-() tv- b+++(++++) DID++ G++ e h! r++(+++) z+>+++
------END GEEK CODE BLOCK------
? quieres saber qui es el geek code ? http://www.geekcode.com





To unsubscribe from this group, send an email to:
webalizer-unsubscribe@egroups.com
Webalizer homepage: http://www.webalizer.org
Webalizer for NT: http://www.medasys-lille.com/webalizer/




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

I am running 2.01 and I have the problem. I have also searched
for 'webalizer' on google and found that all of the systems that came
up have the exact same prob.

Webalizer V2.00-12 (FreeBSD 4.1-RELEASE) English





--- In webalizer@y..., "Jean-Noel HAYART" <jnhayart@n...> wrote:
> hello
>
> I make some work on webalizer,
> i'm shure there is bug on kernel 1.3 of webalizer, somes systems
have this
> trouble but in new release, i think all work fine.
>
> check version of webalizer, and upgrade if you can to 2.XX version
>
> good luck to all
> regards
>
> -----Message d'origine-----
> De : Hilario Ortigosa Monteoliva [mailto:sonicrave@o...]
> Envoye : lundi 8 octobre 2001 09:54
> A : webalizer@y...
> Objet : Re: [webalizer] Problem with Incremental Update also
>
>
> On Mon, Oct 08, 2001 at 07:09:35AM -0000, jic_99@y... wrote:
>
> > I am having the exact replica of Carey's problem described in the
> > post before me. (Different servers of course). We have the exact
same
> > setup (same for over 1 yr) and it died on the 4th of october. Why?
> > and what is the fix? I know if I remove the webalizer.history it
is
> > fixed but i dont want to loose all of my prior data.
>
> I have the same problem, and perhaps it  is in the date
> itself. I have tried to start the data from 1st of october, and the
problem
> persists.
>
>
> I'm using version 1.3x. Anybody knows a bug with specific dates ?
>
> --
> -----BEGIN GEEK CODE BLOCK-----
> Version: 4.0
> GCS/IT/S d- s+++:+++ a-- C++++ UL++++$ PL++ E- W+@ N- o?
> k? w O+@ M-- V? PS++@ PE--(-) Y+(++) PGP t(+) 5++ X++++
> R-() tv- b+++(++++) DID++ G++ e h! r++(+++) z+>+++
> ------END GEEK CODE BLOCK------
> ? quieres saber qui es el geek code ? http://www.geekcode.com
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> webalizer-unsubscribe@egroups.com
> Webalizer homepage: http://www.webalizer.org
> Webalizer for NT: http://www.medasys-lille.com/webalizer/
>
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/

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

Okay, cool, I get to respond to my own message ;-)

After writing to Bradford (Mr Unix) Barrett, the creator of the
Webalizer, I recieved the following response:

-- 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

I hope this is of some help to the others who have had the same
problem as myself.

Cheers,

Carey



--- In webalizer@y..., careybunks@y... wrote:
> Dear Webalizer Enthusiasts,
>
> I've been using webalizer for about 18 months on my site
> gimp-savvy.com without a single problem.  Using a cron job I do a
log
> rotate every day at midnight and run webalizer in incremental mode
> using the command:
>
> webalizer -Q -C 100 -p -l 9 access_log_url
>
> However, suddenly, two days ago, the stats on my site ceased to be
> updated (see http://gimp-savvy.com/STATS).  I assembled the
necessary
> files to run a test with debugging turned on, and the output is:
>
> Webalizer V1.30-04 (Linux 2.2.12-20) English
> Using logfile /home/cbunks/TEST/access
> Creating output in /home/cbunks/TEST/STATS/
> Hostname for reports is 'etoile'
> Reading history file... webalizer.hist
> Reading previous run data.. webalizer.current
> 209048 records (209048 ignored) in 21.80 seconds, 9589/sec
>
> With all the records ignored, I suspected a problem with the time
> stamp, so I looked in the webalizer.current file, and the top two
> lines of this file contain:
>
> # Webalizer V1.30-04 Incremental Data - 10/04/2001 23:58:50
> 2001 10 4 23 58 50
>
> This (2001 10 4 23 58 50) looks like the time stamp to me, so I also
> look in the first access_log that no longer is analyzed, and the
first
> line of the file is:
>
> 216.16.23.88 - - [05/Oct/2001:00:00:27 -0400] "GET /BOOK/node41.html
> HTTP/1.1" 200 8656 "http://gimp-
savvy.com/BOOK/Grokking_the_GIMP.html"
> "Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)"
>
> all the others lines have later dates, so the time stamp problem
> hypothesis seems false.  I've diddled around with a few other
> possibilities, but I haven't found the solution to my problem.  Can
> anyone suggest a test or tell me what I'm doing wrong?
>
> Anyone suggestions would be welcome.
>
> Cheers,
>
> Carey Bunks
>
> =============================
> Carey Bunks
> author of "Grokking the GIMP"
> maintainer of Gimp-Savvy.com
> email:  careybunks@y...
> =============================

Jean-Noel HAYART wrote:
> I make some work on webalizer,
> i'm shure there is bug on kernel 1.3 of webalizer, somes systems have this
> trouble but in new release, i think all work fine.
>
> check version of webalizer, and upgrade if you can to 2.XX version

I´m using V2.00 Windows Version for more than a year - I´ve got the same
Probs with logs after 4th of Oct.

:-(

Bye Lars

A curiosity question for those using the Win32 version of Webalizer
and are using the reverse DNS lookups. How big are your DNS files? I
would think these files get pretty big as they are text, but was
curious how big they got in a live environment.

Many thanks,

Gareth

-----Original Message-----
From: gisaac@... [mailto:gisaac@...]
Sent: dinsdag 9 oktober 2001 4:50
To: webalizer@yahoogroups.com
Subject: [webalizer] Question for Win32 Webalizer users?

A curiosity question for those using the Win32 version of Webalizer
and are using the reverse DNS lookups. How big are your DNS files? I
would think these files get pretty big as they are text, but was
curious how big they got in a live environment.

Many thanks,

Gareth



To unsubscribe from this group, send an email to:
webalizer-unsubscribe@egroups.com
Webalizer homepage: http://www.webalizer.org
Webalizer for NT: http://www.medasys-lille.com/webalizer/




Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Thanks,

That is interesting as I was wondering whether or not it was worth
compressing either the DNS files or the 'webalizer.current' file.

Actually I have good news and bad news for you! I ported the UNIX
version to Windows just a test to see how close I could keep them. It
basically ported very well and easily, I then worked on the DNS part
which didnt compile in by default.

And I have a multithreaded DNS lookup mechanism that uses a
configurable thread pool (dnschildren) to perform the lookups (max 64
concurrent threads). In fact this turned out to be reasonably simple.
However at that time I didnt have access to the Win32 port, so while
I did things in a similar way as the current Win32 version it is not
a drop in replacement.

So in essence the threaded DNS code exists, and I am going to release
a modified version of Webalizer with a couple of new features:

* Multi-threaded DNS pool
* IIS W3C parsing no longer requires the date to be used
* 404 error report
* Denied URL report
* Squid proxy status (HITS vs MISSES vs DENIED etc)

-- The following are work in progress

* Ensure all changes are portable to Linux
* Additional data collection for 304's
* and a couple of other Squid related reports.
* Combine the languages into a single executable
* Potentially compressing 'webalizer.current' to save space on the
server

However the release wont be for a month or two.

I have a particular interest in parsing Squid logs at the moment. If
someone wants to reintegrate in the multithreaded DNS code into the
offical Win32 version I can email them a copy. It shouldnt be too
hard.

Also do you have any information on the webtrends addin? I havnt seen
this one before. Do you have a URL for it?

Thanks,

Gareth

--- In webalizer@y..., "Nick Heinemans" <spam@h...> wrote:
> Well, that what I thought when I first setup webalizer. I'm running
several
> servers with Webalizer, some of them have 200+ sites running. These
sites
> all create separate logs in separate directories. I'm running
multiple
> instances of Webalizer in order to have the stats updated every
night. At
> first I setup all these webalizers to use the same dns.db file, for
I
> thought it would speed things up (no duplicate DNS lookups). I
noticed the
> dns.db file never grew very big, sometime it was around 2MB, but
never much
> bigger. Sometimes is was 100-200KB. So I got the impression at some
point in
> the webalizer process, the dns.db is rebuilt, discarding existing
> information. So then I figured it would be better to have a
separate dns.db
> for each webalizer. This doesn't seem to have a big impact on the
speed.
>
> I really would like to see some sort of a multi-threaded reverse DNS
> function in win32 Webalizer, since this is the most time consuming
part of
> the whole webalizer process. Is it so much different from Unix,
where there
> is some sort of a webazolver running?
>
> Did anybody try the IIS log plug-in from Webtrends, which logs DNS
names
> instead of IP adresses in the normal IIS extended logfiles? This
could speed
> up webalizer, but I can imagine it results in a bigger load on the
server
> since it has to do real-time reverse DNS. I haven't had time to try
this
> plug-in in a real environment, but I hope to do so soon.
>
> Nick
>   -----Original Message-----
>   From: gisaac@m... [mailto:gisaac@m...]
>   Sent: dinsdag 9 oktober 2001 4:50
>   To: webalizer@y...
>   Subject: [webalizer] Question for Win32 Webalizer users?
>
>
>   A curiosity question for those using the Win32 version of
Webalizer
>   and are using the reverse DNS lookups. How big are your DNS
files? I
>   would think these files get pretty big as they are text, but was
>   curious how big they got in a live environment.
>
>   Many thanks,
>
>   Gareth
>
>
>         Yahoo! Groups Sponsor
>
>
>
>   To unsubscribe from this group, send an email to:
>   webalizer-unsubscribe@egroups.com
>   Webalizer homepage: http://www.webalizer.org
>   Webalizer for NT: http://www.medasys-lille.com/webalizer/
>
>
>
>
>   Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.

I am currently running ver 2.0 of Webalizer in incremental mode. Thanks to
everyone here, I noticed that I have the same issue with Oct 4.

The instructions are a little confusing regarding the upgrade to ver 2.01.
First it says that 2.01 (in incremental mode) uses a data format that is
incomaptable with earlier releases, but then says that ver 2.00 should be a
drop in replacement for non-incremental mode. Is it 2.0 that uses a
different format, or 2.01? Either way, what is the best way for a *nix
novice to upgrade? I'm on Redhat 6.2. Thanks in advance for any and all
help.

Barry

I have now installed webalizer 2.01 from 1.3
My Crond run-parts /etc/cron.daily email message

has a different content over 1.3 with the following lines added to my
email
<<Snip>>
[new_snode] Warning: String exceeds storage size (118)
[new_snode] Warning: String exceeds storage size (94)
db_put fail!
db_put fail!
<<Snip>>

I have searched the archive, how would I stop this error, what does
it mean

Regards
John Hedges

-----Original Message-----
From: gisaac@... [mailto:gisaac@...]
Sent: dinsdag 9 oktober 2001 19:07
To: webalizer@yahoogroups.com
Subject: [webalizer] Re: Question for Win32 Webalizer users?

Thanks,

That is interesting as I was wondering whether or not it was worth
compressing either the DNS files or the 'webalizer.current' file.

Actually I have good news and bad news for you! I ported the UNIX
version to Windows just a test to see how close I could keep them. It
basically ported very well and easily, I then worked on the DNS part
which didnt compile in by default.

And I have a multithreaded DNS lookup mechanism that uses a
configurable thread pool (dnschildren) to perform the lookups (max 64
concurrent threads). In fact this turned out to be reasonably simple.
However at that time I didnt have access to the Win32 port, so while
I did things in a similar way as the current Win32 version it is not
a drop in replacement.

So in essence the threaded DNS code exists, and I am going to release
a modified version of Webalizer with a couple of new features:

* Multi-threaded DNS pool
* IIS W3C parsing no longer requires the date to be used
* 404 error report
* Denied URL report
* Squid proxy status (HITS vs MISSES vs DENIED etc)

-- The following are work in progress

* Ensure all changes are portable to Linux
* Additional data collection for 304's
* and a couple of other Squid related reports.
* Combine the languages into a single executable
* Potentially compressing 'webalizer.current' to save space on the
server

However the release wont be for a month or two.

I have a particular interest in parsing Squid logs at the moment. If
someone wants to reintegrate in the multithreaded DNS code into the
offical Win32 version I can email them a copy. It shouldnt be too
hard.

Also do you have any information on the webtrends addin? I havnt seen
this one before. Do you have a URL for it?

Thanks,

Gareth

--- In webalizer@y..., "Nick Heinemans" <spam@h...> wrote:
> Well, that what I thought when I first setup webalizer. I'm running
several
> servers with Webalizer, some of them have 200+ sites running. These
sites
> all create separate logs in separate directories. I'm running
multiple
> instances of Webalizer in order to have the stats updated every
night. At
> first I setup all these webalizers to use the same dns.db file, for
I
> thought it would speed things up (no duplicate DNS lookups). I
noticed the
> dns.db file never grew very big, sometime it was around 2MB, but
never much
> bigger. Sometimes is was 100-200KB. So I got the impression at some
point in
> the webalizer process, the dns.db is rebuilt, discarding existing
> information. So then I figured it would be better to have a
separate dns.db
> for each webalizer. This doesn't seem to have a big impact on the
speed.
>
> I really would like to see some sort of a multi-threaded reverse DNS
> function in win32 Webalizer, since this is the most time consuming
part of
> the whole webalizer process. Is it so much different from Unix,
where there
> is some sort of a webazolver running?
>
> Did anybody try the IIS log plug-in from Webtrends, which logs DNS
names
> instead of IP adresses in the normal IIS extended logfiles? This
could speed
> up webalizer, but I can imagine it results in a bigger load on the
server
> since it has to do real-time reverse DNS. I haven't had time to try
this
> plug-in in a real environment, but I hope to do so soon.
>
> Nick
>   -----Original Message-----
>   From: gisaac@m... [mailto:gisaac@m...]
>   Sent: dinsdag 9 oktober 2001 4:50
>   To: webalizer@y...
>   Subject: [webalizer] Question for Win32 Webalizer users?
>
>
>   A curiosity question for those using the Win32 version of
Webalizer
>   and are using the reverse DNS lookups. How big are your DNS
files? I
>   would think these files get pretty big as they are text, but was
>   curious how big they got in a live environment.
>
>   Many thanks,
>
>   Gareth
>
>
>         Yahoo! Groups Sponsor
>
>
>
>   To unsubscribe from this group, send an email to:
>   webalizer-unsubscribe@egroups.com
>   Webalizer homepage: http://www.webalizer.org
>   Webalizer for NT: http://www.medasys-lille.com/webalizer/
>
>
>
>
>   Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.



To unsubscribe from this group, send an email to:
webalizer-unsubscribe@egroups.com
Webalizer homepage: http://www.webalizer.org
Webalizer for NT: http://www.medasys-lille.com/webalizer/




Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

hello,

I am delighted by learn that you have working on webalizer win 32 version, i
can if you want add your Multi-threaded code to current port.

You can also download source of this port :

http://www.medasys-lille.com/webalizer/VersionR04/default.htm

I send all my code to Brad somes months ago.
I think that the win32 release is not its priority.

regards

-----Message d'origine-----
De : gisaac@... [mailto:gisaac@...]
Envoye : mardi 9 octobre 2001 19:07


A : webalizer@yahoogroups.com
Objet : [webalizer] Re: Question for Win32 Webalizer users?


Thanks,

That is interesting as I was wondering whether or not it was worth
compressing either the DNS files or the 'webalizer.current' file.

Actually I have good news and bad news for you! I ported the UNIX
version to Windows just a test to see how close I could keep them. It
basically ported very well and easily, I then worked on the DNS part
which didnt compile in by default.

And I have a multithreaded DNS lookup mechanism that uses a
configurable thread pool (dnschildren) to perform the lookups (max 64
concurrent threads). In fact this turned out to be reasonably simple.
However at that time I didnt have access to the Win32 port, so while
I did things in a similar way as the current Win32 version it is not
a drop in replacement.

So in essence the threaded DNS code exists, and I am going to release
a modified version of Webalizer with a couple of new features:

* Multi-threaded DNS pool
* IIS W3C parsing no longer requires the date to be used
* 404 error report
* Denied URL report
* Squid proxy status (HITS vs MISSES vs DENIED etc)

-- The following are work in progress

* Ensure all changes are portable to Linux
* Additional data collection for 304's
* and a couple of other Squid related reports.
* Combine the languages into a single executable
* Potentially compressing 'webalizer.current' to save space on the
server

However the release wont be for a month or two.

I have a particular interest in parsing Squid logs at the moment. If
someone wants to reintegrate in the multithreaded DNS code into the
offical Win32 version I can email them a copy. It shouldnt be too
hard.

Also do you have any information on the webtrends addin? I havnt seen
this one before. Do you have a URL for it?

Thanks,

Gareth

--- In webalizer@y..., "Nick Heinemans" <spam@h...> wrote:
> Well, that what I thought when I first setup webalizer. I'm running
several
> servers with Webalizer, some of them have 200+ sites running. These
sites
> all create separate logs in separate directories. I'm running
multiple
> instances of Webalizer in order to have the stats updated every
night. At
> first I setup all these webalizers to use the same dns.db file, for
I
> thought it would speed things up (no duplicate DNS lookups). I
noticed the
> dns.db file never grew very big, sometime it was around 2MB, but
never much
> bigger. Sometimes is was 100-200KB. So I got the impression at some
point in
> the webalizer process, the dns.db is rebuilt, discarding existing
> information. So then I figured it would be better to have a
separate dns.db
> for each webalizer. This doesn't seem to have a big impact on the
speed.
>
> I really would like to see some sort of a multi-threaded reverse DNS
> function in win32 Webalizer, since this is the most time consuming
part of
> the whole webalizer process. Is it so much different from Unix,
where there
> is some sort of a webazolver running?
>
> Did anybody try the IIS log plug-in from Webtrends, which logs DNS
names
> instead of IP adresses in the normal IIS extended logfiles? This
could speed
> up webalizer, but I can imagine it results in a bigger load on the
server
> since it has to do real-time reverse DNS. I haven't had time to try
this
> plug-in in a real environment, but I hope to do so soon.
>
> Nick
>   -----Original Message-----
>   From: gisaac@m... [mailto:gisaac@m...]
>   Sent: dinsdag 9 oktober 2001 4:50
>   To: webalizer@y...
>   Subject: [webalizer] Question for Win32 Webalizer users?
>
>
>   A curiosity question for those using the Win32 version of
Webalizer
>   and are using the reverse DNS lookups. How big are your DNS
files? I
>   would think these files get pretty big as they are text, but was
>   curious how big they got in a live environment.
>
>   Many thanks,
>
>   Gareth
>
>
>         Yahoo! Groups Sponsor
>
>
>
>   To unsubscribe from this group, send an email to:
>   webalizer-unsubscribe@egroups.com
>   Webalizer homepage: http://www.webalizer.org
>   Webalizer for NT: http://www.medasys-lille.com/webalizer/
>
>
>
>
>   Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.



To unsubscribe from this group, send an email to:
webalizer-unsubscribe@egroups.com
Webalizer homepage: http://www.webalizer.org
Webalizer for NT: http://www.medasys-lille.com/webalizer/




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Since friday 5 Oct, webalizer not process the logs. All services, confs,
etc.. run ok, but i don´t know why webalizer not read the logs.

------

Hi,

please read the mailing list archive of the last 3 days. It's a problem of
the old version. You need to update to a new version of webalizer.

Bye
Klaus

I recently upgraded my webalizer to v2
My cron daemon now sends me the following message:
db_put fail!
db_put fail!
db_put fail!
db_put fail!
etc etc

instead of truncating oversized request field

has anyone got any ideas what db_put fail! actually is?????

Andy

I have been using Webalizer for a while now and it is great!  I
recenlty decided to add the dns option.  When I rerun configure --
enable-dns I get the following warning:

...
checking how to run the C preprocessor... (cached) gcc -E
checking whether char is unsigned... (cached) no
checking for dbopen... (cached) no
checking for library containing dbopen... (cached) no
configure: warning: You must have a V1.85 compatable DB library!
configure: warning: DNS lookup code will be disabled...
checking for socket... (cached) yes
...

What is a "V1.85 compatable DB library"?  I am running on RedHat 7
without DNS installed.  Log is pulled from Squid which is configured
for both proxy and http aceleration.

Thanks,

Darley