Re: Webalizer Mixing Logs
- I think I was able to track down what was causing the DNS Cache error:
I had enabled the "CustomLog logs/access_log combined" in the main
httpd.conf file for the server.
I have just disabled it again and I will wait to see what happens
tonight after crontab runs.
Thanks for the responses. They helped me to re-examine everything
that I did that might have caused the problematic behaviour.
--- In email@example.com, "Bradford L. Barrett" <brad@m...>
> > As to the truncating oversized referrer fields, do you know how to
> > locate the specific line that it is occuring on in a log file?
> > All the docs that I have seen show the error message about this
> > giving the line number in the log file, but I have not been
> > anything like that in my error messages. Just a plain "truncatingwarning,
> > oversized referrer field". Nothing else.
> The location is not specified because it's not an error.. just a
> and can be safely ignored.have
> > Also, what is with the "Unable to lock DNS Cache file" error? I
> > disabled DNS Caching in all the domains, but Webalizer stillseems to
> > be attempting to use the DNS Cache file.that
> Means just what it says.. it can't lock the file. It also means
> you obviously haven't disabled all dns lookups, as otherwise itwould
> not even bother trying to get to the cache file.
> Bradford L. Barrett brad@m...
> A free electron in a sea of neutrons DoD#1750 KD4NAW
> The only thing Micro$oft has done for society, is make people
> believe that computers are inherently unreliable.