Not easy replacement of Apache with Ngnix due to error log

[Adrian Hayter]

>
>   I just shared the thing that was happened with me. If error log was
> informative like apache then It could be the solved earlier.
>

It was informative. It told you which process was actually having the error
(FastCGI). Nginx should be expected to handle it's own error messages well,
but if the error is in another process, it only has what that process gives
back to it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120403/de3612db/attachment.html>