Our zend application log file continues to be affected with "CRIT (2): PAGE_NOT_FOUND" errors.
I finally found an idea for their generation when evaluating both zend application log and also the apache access log instantly, which demonstrated synchronised results of...
Zend_Log: 2011-09-04T12:15:21-04:00 CRIT (2): PAGE_NOT_FOUND Access_Log: ::1 - - [03/Sep/2011:20:17:33 -0500] "OPTIONS * HTTP/1.0" 200 1090 (the times do not reflect matching log entries)
Searching online around the access log string lead me to:
Where, as recommended, I transformed my log format to "combined" rather than "common" which confirmed these log strings, a minimum of in access_log, were Apache "internal dummy connections"
Access_Log: ::1 - - [04/Sep/2011:08:38:42 -0500] "OPTIONS * HTTP/1.0" 200 1090 "-" "Apache/2.2.3 (CentOS) (internal dummy connection)"
As these Apache logs records were occurring in the same instance as my undesirable "PAGE_NOT_FOUND" I'm presuming the later Zend log records range from same...
Following a advice of link above I had been able stop these Apache access_log records but regrettably the Zend ones continue to come...
How do you eliminate these PAGE_NOT_FOUND records?
I have attempted using Zend_Log_Filter_Message though I doubt I'm doing the work right. I wasn't in a position to many good examples.
Is the street I have to go? If that's the case does anybody have suggestions?