RE: [cobalt-users] Log/Webalizer Weirdness...

["Dee Dreslough" <dee@xxxxxxxxxxx>]

> > Oops.. I meant to mention. I am using Webalizer 2.0 - it's handling the
> one web.log.1.gz file fine...the problem seems to be more with logs
rotating
> out of existance for no real reason...
>
>
> Dee,
>     You didn't mention anything about any adjustments to your
> /etc/logrotate.d or /etc/logrotate.onboot files?

I haven't modified anything - I just intalled Webalizer, and at first,
web.log for my site2 did have data in it, and the web.log.1.gz file for that
site did have stats through July, just like the other site. Now, for some
reason, web.log for that site only is always 0 and the web.log.1.gz only
contains the data for the last few days. I've been watching it for 3 days
now, and the only explanation I can think of is that when the split_logs
script runs, it always creates a web.log for that one site that's bigger
than 10M and then rotates it into web.log.1.gz... I'll have to manually try
splitting the access file to see what it makes to verify this.

The question is, why did it then desetroy web.log.1.gz with all that lovely
data through July?  I don't want to keep restoring the data just to have it
knocked out again - I havent tried restoring it yet because I want to
understand what's happening first. Is there a size limit in some other
rotate script I don't know about for the .gzs?

Here's the web.log directory output
total 17083
drwxr-s---   2 httpd    site2        1024 Aug 22 04:03 .
drwxrwsr-x   6 httpd    site2        1024 Jul 26 01:06 ..
-rw-r--r--   1 root     site2         348 Aug 16 04:03 ftp.cache.new
-rw-r--r--   1 root     site2      653459 Aug 16 04:03 ftp.log
-rw-r--r--   1 root     site2         713 Aug 16 04:03 ftp.stats
-rw-r--r--   1 root     site2        6088 Aug 22 04:03 mail.cache.new
-rw-r--r--   1 root     site2      187048 Aug 22 04:03 mail.log
-rw-r--r--   1 root     site2       11311 Aug 22 04:03 mail.stats
-rw-r--r--   1 root     site2      225136 Aug 22 04:02 web.cache.new
-rw-r--r--   1 root     site2           0 Aug 22 04:03 web.log
-rw-r--r--   1 root     site2     1527247 Aug 22 04:02 web.log.1.gz
-rw-r--r--   1 root     site2    14664356 Aug 21 19:10 web.log.test
-rw-r--r--   1 root     site2      137311 Aug 22 04:02 web.stats

> size and rotation.... etc. of your log files.  do a man logrotate to learn
> more about them and keep in mind that the gui will not "play nice" with
> these files.

(Really, I did RTFM! I did...!) :) I did already do a man logrotate and
studied up on what it's doing, but this just doesn't make sense for this one
site.

Here's what the site2 file for Logrotate.d has for the web... As you can
see, the file is no where near 10M (in fact, it seems it's always 0):
/home/sites/site2/logs/web.log {
   missingok
   compress
   size 10M
}

Any idea why it threw out everything that had been in web.log.1.gz before?
Is there a logrotate file out there that controls the size of the .gzs?  I
can't find it yet, but I'm a bit new to logrotate...

I'm sorry if I'm asking something stupid...

-Dee Dreslough (dee@xxxxxxxxxxxxx)