| 9:57 pm on Jun 23, 2005 (gmt 0)|
What level is the log setting at?
This should be configurable in the httpd.conf file, and may have been accidentally overwritten or changed to 0, which would cause Apache to stop logging information.
| 10:53 pm on Jun 23, 2005 (gmt 0)|
But the comment for that variable says that it applies to the error log. It shouldn't affect access log, should it?
By the way, I also have:
CustomLog /var/log/httpd-access.log combined
This has always worked in the past. I didn't change anything manually in the httpd.conf file, but I know that the PHP5 installation touched it.
I search on the word "log" and everything looks right. This one has me baffled.
| 12:37 am on Jun 24, 2005 (gmt 0)|
Maybe this page about Apache Logging commands will help find the missing commands:
| 4:36 pm on Jun 24, 2005 (gmt 0)|
Yeah, nothing in that article stands out. Like I said, everything looks normal.
The log file permissions are root/wheel -rw-r--r--. That seems pretty restrictive to me, but it matches the /var/log directory which is root/wheel -rwxr-xr-x so I suppose it's right.
| 4:48 pm on Jun 24, 2005 (gmt 0)|
I just stopped and restarted httpd, and now it's logging! #*$!?
| 5:25 pm on Jul 28, 2005 (gmt 0)|
bump with more info
It turns out that when the log rolls over every night, Apache stops logging. If I restart Apache manually, logging starts again until the nightly rollover.
I figure that this might be a permissions problem. Maybe Apache doesn't have permission to write to the newly created log file, which was actually made by the program that does the log rollover.
I'm running FreeBSD.
I don't really know how the log rollover job works, or where it is configured. The dysfunctional log is owned by root/wheel and set to 644.