PDA

View Full Version : Error Log: "PHP 5.2.x cannot be found", but not using PHP



KenJackson
05-07-2008, 05:52 AM
I just notices a curious thing in my site's error logs:

PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at '/usr/local/Zend/lib/Optimizer-2.5.10/php-5.2.x/ZendOptimizer.so') - try reinstalling the Zend Optimizer in Unknown on line 0
[Wed May 07 05:29:33 2008] [error] [client 67.19.xxx.xxx] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
[Wed May 07 05:29:33 2008] [error] [client 67.19.xxx.xxx] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at '/usr/local/Zend/lib/Optimizer-2.5.10/php-5.2.x/ZendOptimizer.so') - try reinstalling the Zend Optimizer in Unknown on line 0
[Wed May 07 05:30:02 2008] [error] [client 69.89.22.117] File does not exist: /usr/local/apache/htdocs/wp-cron.php
[Wed May 07 05:31:16 2008] [error] [client 74.124.xxx.xxx] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
[Wed May 07 05:31:16 2008] [error] [client 74.124.xxx.xxx] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
[Wed May 07 05:31:16 2008] [error] [client 74.124.xxx.xxx] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
I think I've replaced about all of all my PHP files with HTML, but the error message doesn't even reference a specific file.

Also, the one IP address I didn't x out is the IP of the server.

Anyone recognize what's going on?

Early Out
05-07-2008, 06:00 AM
If you're seeing this in the Main Error Log, they're probably not your errors. The Main Error Log shows all errors for the server before they can be id'ed to a particular account.