Apache2 php error logging

[Jasper Frumau]

On Sun, Feb 7, 2010 at 10:49 AM, Jasper Frumau <jasperfrumau at gmail.com>wrote:

> Well I found out there was logging on the cause of the white screen. It
> isn't a PHP issue anymore:
> ::1 - - [07/Feb/2010:10:42:50 +0300] "GET /img/index.php HTTP/1.1" 500 -
> WWW Consortium mentions:
> *10.5.1 500 Internal Server Error
> The server encountered an unexpected condition which prevented it from
> fulfilling the request.*
> Why is another issue.
>

Errors solved. FTP layer in Joomla's configuration.php had to be deactivated
as I have no FTP running on my Server. What FTP program do you guys
recommend?


>
> To get back to the PHP error logging issues,  I might comment out error_log
> in my php.ini and see if the error will be stored in Apache's error_log in
> /opt/local/apache2/logs/error_log ...


Will work on this some more when I have solved some other issues...


>
>
>
> >
>> > You know, I'm not sure. I always just leave the php.ini at default in
>> that setting and that is where it logs.
>> > Maybe load phpInfo(); and see if you can still see the default value.
>>
>> Yeah well that is:
>>
>>
>> error_log/var/log/php-scripts.log/var/log/php-scripts.log
>>
>> So that has already been changed by me in the php.ini .
>>
>>
>> >
>> > I believe your php logging levels, like E_* play a role here as to what
>> gets logged to screen/browser/stdout as well. More good info here:
>> > http://www.php.net/manual/en/function.error-reporting.php
>> > And also related to some of your other questions.
>> > http://php.net/manual/en/errorfunc.configuration.php
>>
>> Checked that out before. More on PHP Error functions in php scripts than
>> on real configuration.
>>
>> I checked http://php.net/log-errors and read details in php.ini itself
>>
>>
>>
>> > If you move aside you php.ini and put a copy of php.ini(development),
>> then look at your phpIfo(); output, it will tell you.
>> > I suspect the log path is just commented ou in the ini default filet.
>>
>> Yes, comment out, both in production and development inis:
>>
>> $ cat php.ini-production | grep error_log
>> ; server-specific log, STDERR, or a location specified by the error_log
>> ; Set maximum length of log_errors. In error_log information about the
>> source is
>> ;error_log = php_errors.log
>> ;error_log = syslog
>> $ cat php.ini-production | grep error_log
>> ; server-specific log, STDERR, or a location specified by the error_log
>> ; Set maximum length of log_errors. In error_log information about the
>> source is
>> ;error_log = php_errors.log
>> ;error_log = syslog
>>
>> And here as I use it:
>>
>> $ cat php.ini | grep error_log
>> ; server-specific log, STDERR, or a location specified by the error_log
>> ; Set maximum length of log_errors. In error_log information about the
>> source is
>>
>> error_log = /var/log/php-scripts.log
>> ;error_log = syslog
>>
>>
>>
>>
>> > You could skip the loading of the php.ini and if your cool with diff or
>> grep, just compare the ini sample files MacPorts installed.
>>
>> I use grep as a search tool, but have not used it to compare yet. Never
>> used diff. Will check them out asap..
>>
>> > php.ini for me, sends logging to Apache's error_log. It always has.
>>
>> Yes, well do I understand that commenting it out will send it the Apache
>> error log?
>>
>>
>> http://lists.macosforge.org/pipermail/macports-users/2007-September/005668.htmlseems to indicate that ..
>>
>> Sidenote: I still have a white screen of death in
>> opt/local/apache2/htdocs/folder/ The error reporting is turned of, logging
>> turned on but no new errors reported...
>>
>>
>>
>> > When I get back to my computer and off my phone I will confirm.
>> > --
>> > Scott
>> > (Sent from a mobile device)
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20100207/ceba37a7/attachment.html>