Posted by Ben Bacarisse on 02/16/06 18:12

On Wed, 15 Feb 2006 19:46:10 -0800, lawrence k wrote:

>
> Andy Hassall wrote:
>> >Our Linux guy, Matt Clark, checked for errors. He said there were no
>> >errors in the PHP log.
>>
>> That's one log down, then. What about the others?
>>
>> Hint:
>>
>> >>>What reasons, other than the POST limit, would a large upload fail?
>> >>
>> >> Various. Almost all of which produce errors, either in the form of
>> >> PHP errors,
>> >>Apache errors or the field in $_FILES.
>
> I don't suppose you'd know what these error files are typically called, do
> you?

PHP can be told not to log errors, or if not that, to log them in various
ways (syslog, or Apache's log files, or to a specif one of your choosing).

So first look at php.ini and make sure that "log_errors = On" in there.
On my setup that is all that is needed for PHP errors to be written to
Apache's error_log file. The files called error_log.2 and so on are older
versions made when the logs get "rotated".

The logs have times in them so obviously you need to find the file that
has errors timed at the time you have provoked the error.

Elsewhere in php.ini is a setting to control where errors get logged
(error_log = ...). If you can set this to the name of a file on the
server that you can read, then you won't need to be sent the logs.
Setting it to "syslog" will make PHP error get logged to the same place as
almost everything else on the server and will just make yours very hard to
find, so make sure it is either commented out (errors go to Apache logs)
or it is set to file specifically for PHP errors (the more useful setting).

--
Ben.

[Back to original message]