Edit report at https://bugs.php.net/bug.php?id=61045&edit=1
ID: 61045
Comment by: bitmand at gmail dot com
Reported by: lxlight at gmail dot com
Summary: fpm don't send error log to fastcgi clients(nginx)
Status: Assigned
Type: Bug
Package: FPM related
Operating System: Linux
PHP Version: 5.3.10
Assigned To: fat
Block user comment: N
Private report: N
New Comment:
Same here on 5.3.9 and .10 on apache. Errors used to go to apache error log,
but
after 5.3.9 nothing gets logged.
I wonder if the change is actually by design, according to the php-fpm
documentation for "catch_workers_output" is states that "If not set, stdout and
stderr will be redirected to /dev/null according to FastCGI specs."
But it would definitely be great with and option to throw errors to stderr
again.
Previous Comments:
------------------------------------------------------------------------
[2012-03-28 14:45:25] kustodian at gmail dot com
Exact same problem on Centos 6.2 with a custom build PHP 5.3.10. I reverted
back to 5.3.8 since I need to have PHP errors in the Nginx error.log.
------------------------------------------------------------------------
[2012-03-23 15:34:49] hugo at barafranca dot com
"Me too", on FreeBSD 7.3 with nginx-1.0.14,1 and php5-5.3.10.
------------------------------------------------------------------------
[2012-03-15 06:38:22] prinbra at gmail dot com
in fact, set display_errors to On, we can still view the error message, but the
message didn't go to nginx error log when display_errors is set to Off.
test confirmed that the same setting works fine on php 5.3.8
------------------------------------------------------------------------
[2012-03-07 17:42:13] ben dot lemasurier at gmail dot com
confirmed on php v5.3.10
------------------------------------------------------------------------
[2012-03-04 18:19:04] ewgraf at gmail dot com
Add patch for 5.3.10.
It simple, not so right, because I think this functionality need move to
zlog_ex,
but it works for me.
If anybody can review it and test, would be nice.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=61045
--
Edit this bug report at https://bugs.php.net/bug.php?id=61045&edit=1
