Apache2 php error logging
jasperfrumau at gmail.com
Sat Feb 6 12:16:48 PST 2010
On Sat, Feb 6, 2010 at 10:50 PM, Scott Haneda <talklists at newgeo.com> wrote:
> You could probably nuke the script and redstart Apache, it should recreate
> itself with the correct permission.
> At least, that's exactly how my error and access logs behave. When I roll
> them I essentilly move them, sleep apache, restart apache gracefully, and
> gzip them. I've never had a log not recrete on lack of existance. Then
> again, I've always sent php errors to the error log in Apache since the
> errors often time are related, or helpful to see http data errors alongside.
I guess I could do this as well. On some other shared hosts I work with they
do the same. Do I just adjust the path in php.ini and write PHP errors to
the same error.log as Apache writes its errors to?
> And I do all that by hand because logroller has bnot Bern updated in years
> and the unbuilt Apache log piping mechanism causes Apache to crash. I filed
> a bug report but Apache seems to not take notice.
> (Sent from a mobile device)
> On Feb 6, 2010, at 6:09 AM, Jasper Frumau <jasperfrumau at gmail.com> wrote:
> When I chmod 777 the file it started logging. I guess Apache is in a
> different group.... Well all is well now and save as al is taking place
> On Sat, Feb 6, 2010 at 4:29 PM, Jasper Frumau < <jasperfrumau at gmail.com>
> jasperfrumau at gmail.com> wrote:
>> $ sudo chown root:admin php-scripts.log
>> did not help either to get the logging going. It must be something else.
>> But what?
>> On Sat, Feb 6, 2010 at 4:10 PM, Jasper Frumau < <jasperfrumau at gmail.com>
>> jasperfrumau at gmail.com> wrote:
>>> I adjusted my php.ini in opt/local/etc/php5/php.ini to log php errors to
>>> /var/log/php-scripts.log :
>>> $php -i | grep error_log
>>> error_log => /var/log/php-scripts.log => /var/log/php-scripts.log
>>> PHP Warning: Unknown: It is not safe to rely on the system's timezone
>>> settings. You are *required* to use the date.timezone setting or the
>>> date_default_timezone_set() function. In case you used any of those methods
>>> and you are still getting this warning, you most likely misspelled the
>>> timezone identifier. We selected 'Europe/Moscow' for 'MSK/3.0/no DST'
>>> instead in Unknown on line 0
>>> $ php -i | grep log_errors
>>> log_errors => On => On
>>> log_errors_max_len => 1024 => 1024
>>> And in php.ini I have error_reporting = E_ALL & ~E_STRICT
>>> $ pwd
>>> $ ls -l | grep php
>>> -rw-r--r-- 1 root wheel 0 Nov 1 12:35 php-scripts.log
>>> In a folder where I try to run a copy of Joomla! I keep on getting white
>>> screens on the index.php so I assume I get PHP errors. Apache is running and
>>> so is MYSQL (other Wordpress site is running locally)... The php-scripts.log
>>> is not populated with errors at all though. Is it ht e php-scripts/.log file
>>> permissions perhaps?
> macports-users mailing list
> macports-users at lists.macosforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-users