Debugging 504 Gateway Timeout and its actual cause and solution
nginx-forum at forum.nginx.org
Wed Jan 6 07:56:43 UTC 2016
Thanks Richard & itpp2015 for your response.
Further update :
There are 2 cases :
1. 504 @ 120 seconds coming with below mentioned error :
2016/01/05 03:50:54 [error] 1070#0: *201650845 upstream timed out (110:
Connection timed out) while connecting to upstream, client: 126.96.36.199,
server: x.x.x.x, request: "GET /some/url HTTP/1.1", upstream:
"fastcgi://127.0.0.1:9000", host: "example.com"
2. 504 @ 300 seconds coming with below mentioned error :
2016/01/05 00:51:43 [error] 1067#0: *200656359 upstream timed out (110:
Connection timed out) while reading response header from upstream, client:
188.8.131.52, server: 192.168.12.101, request: "GET /some/url HTTP/1.1",
upstream: "fastcgi://127.0.0.1:9000", host: "example.com"
* No errors found in php-fpm logs.
* Number of php-fpm processes were also normal. Backend doesn't look
overloaded as other requests were served out fine at the same time.
* Only one php-fpm pool is being used. One php-fpm master (parent) process
and other slave (child) processes are usually at normal range only when 5xx
are observed. There is no significant growth in number of php-fpm processes
and even if grows then server has enough capacity to fork new ones and serve
Posted at Nginx Forum: https://forum.nginx.org/read.php?2,263842,263870#msg-263870
More information about the nginx