Nginx Doesn't Log FastCGI Errors

I have recently migrated my Nginx+PHP-FPM server from a Centos 5 to a
Centos 6 server and I basically migrated the whole configuration from
the old server to the new one with minor changes. I compiled the newest
versions of Nginx (1.0.14) and PHP (5.3.10), Centos 5 had 1.0.2 and
5.3.2.

The problem is that Nginx doesn’t log FastCGI errors in its error.log,
it’s logging it’s own errors without a problem. I’m talking about the
errors which look like this:

“2012/03/28 07:56:01 [error] 14919#0: *697095886 FastCGI sent in stderr:
“CSRF state token does not match one provided” while reading response
header from upstream…”

I tried to change many things, but I can’t make the FastCGI errors to be
logged in the Nginx error.log.

nginx.conf: nginx.conf - Pastebin.com
php-fpm.conf: php-fpm.conf - Pastebin.com
php.ini loggin section: php.ini logging section - Pastebin.com

Posted at Nginx Forum:

Hello!

On Wed, Mar 28, 2012 at 07:52:37AM -0400, kustodian wrote:

“2012/03/28 07:56:01 [error] 14919#0: *697095886 FastCGI sent in stderr:
“CSRF state token does not match one provided” while reading response
header from upstream…”

I tried to change many things, but I can’t make the FastCGI errors to be
logged in the Nginx error.log.

nginx.conf: nginx.conf - Pastebin.com
php-fpm.conf: php-fpm.conf - Pastebin.com
php.ini loggin section: php.ini logging section - Pastebin.com

This is php regression, see here:

https://bugs.php.net/bug.php?id=61045

There are also reports that

catch_workers_output = yes

in php-fpm config should help, see here (in Russian):

http://mailman.nginx.org/pipermail/nginx-ru/2012-March/046217.html

Maxim D.

Thank you very much for the reply. I was trying everything, I searched
everywhere and I couldn’t find the solution.

Just to note for others, setting “catch_workers_output = yes” doesn’t
work, you can either patch php with a fix provided in the bug
PHP :: Bug #61045 :: fpm don't send error log to fastcgi clients(nginx), or use PHP 5.3.8, which I would
recommend since the patch didn’t come from the official PHP developer.

Posted at Nginx Forum: