One domain on my server stopped recording traffic to the Apache access log.
/usr/local/apache/domlogs/domain.com
How do I find out why traffic stopped recording?
It seems to have stopped for this one domain on the first of this month.
One domain on my server stopped recording traffic to the Apache access log.
/usr/local/apache/domlogs/domain.com
How do I find out why traffic stopped recording?
It seems to have stopped for this one domain on the first of this month.
Last edited by PDM; 01-03-2006 at 10:27 PM.
Cannot really find out as all the records are gone. Try restarting apache and that should restart the logging.
Lloyd F Tennison
When a log file gets too big, (2GB I think), it stops being written to. When that happens the file has to be emptied and apache restarted to resume logging.
This doesn't seem to be the case here.
This is a very low traffic site, 100 or so visistors per day.
The file just isn't being writte to when visitors hit the site and I'm not sure where to start looking as to why it's not.
Doesn't seem to help.Try restarting apache and that should restart the logging
Deleted the domlog file via ssh but still not logging.
Perms seem to be the same as all other domolg files.
???
Does the VirtualHost entry in httpd.conf for that domain have a line like
CustomLog domlogs/domain.com combined
Yes it looks just like other 86
Thanks
Hi,
Did you resolve this problem? We're seeing the same thing on one domain only. Log sizes are OK, CustomLog entry in httpd.conf OK and unchanged, deleted existing file, checked permissions, restarted Apache. Apache recreates file, but a tail -f shows nothing is being written to it.
Thanks.
My issue turned out to be DNS resolution hadn't pointed the domain to the new server.
Once DNS resolved to the server the logs started getting traffic recorded.