fastcgi_read_timeout with PHP backend

Maxim Dounin mdounin at
Wed May 29 16:46:27 UTC 2013


On Tue, May 28, 2013 at 01:32:48PM -0400, B.R. wrote:

> Hello Maxim,
> I spent a lot of time trying to figure out what is happening.
> It seems that after some service restart, the problem sometimes disappear
> before coming back again on the following try.
> I finally managed to capture the debug log you'll find as attachment. I'll
> need your expertise on it, but it seems that the tcpdump show stuff which
> do not appear in the nginx output.
> T
> ​he archive attached is as much self-contained as possible, including :
> - Server information (uname -a)
> - Nginx information (nginx -V)​: self-compiled from sources since I needed
> to activate --with-debug
> - tcpdump between php and nginx (+ 'control' file containing the standard
> output of the tcpdump command, including interface and packet numbers
> information only)
> - nginx error_log (set on 'debug)
> - browser output (copied-pasted from source, you'll see there is no end
> tag, thus proving the output is brutally cut out)

As per debug log, nothing is seen from php after 18:48:45, and 
this results in the timeout at 18:50:45.

Unfortunately, tcpdump dump provided looks corrupted - it shows 
only first 4 packets both here and on cloudshark 

Overral I would suggest that this is just how you code behaves.  
You may want to add some debugging to your application to debug 
this further if you still think there is something wrong.

Maxim Dounin

More information about the nginx mailing list