|
From: John H. <web...@ew...> - 2006-11-12 00:09:31
|
Jamie Cameron wrote: > On 11/Nov/2006 12:04 John Hinton wrote .. > >> Jamie Cameron wrote: >> >>> The only other thing I can think of is deleting the webalizer.hist and >>> >> webalizer.current files before generating the report, to ensure it is totally >> re-parsed.. >> >>> Also, in your webalizer.conf file for this log (found under /etc/webmin/webalizer >>> >> or at /etc/webalizer.conf), try setting the FoldSeqErr directive to yes, >> just in case you have some out-of-order log lines. >> >>> If that doesn't work, I am out of ideas, sorry. This must be some oddity >>> >> in Webalizer itself, like the old bug that once caused it to stop parsing >> logs after some date around october 2001 ! >> >>> - Jamie >>> >>> >> Jamie, >> >> I've had what appears to be some timing issues with Webalizer/Logrotate >> using the standard Virtualmin setup. It seems that particularly on the >> first of the month.. and then particularly if the first is a Sunday... >> It seems like I set the logrotate timing back, giving Webalizer more >> time to finish. It's been a while.. a year or so since I had to mess >> with this. Just passing along some information. >> > > Was the problem that Virtualmin rotated away the log files before > Webalizer could process them? Or that both webalizer and log rotation > were running at the same time? > > - Jamie > I believe that webalizer couldn't get done before logrotate started... something that might only happen when you have a couple of hundred vhosts with a large number of visits per day. I never really paid attention to what set the timing.. the OS or Webmin/Virtualmin. John |