Re: nginx on high load (upstream prematurely closed connection while reading response header from upstream)

Thankyou once again Francis Daly, i am now ignoring these errors, as i not see any errors in nginx access logs and site is working on high load and see 200 response code in access logs. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,266978,267052#msg-267052 ___

Re: nginx on high load (upstream prematurely closed connection while reading response header from upstream)

Thankyou once again Francis Daly, i am now ignoring these errors, as i not see any errors in nginx access logs and site is working on high load and see 200 response code in access logs. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,266978,267051#msg-267051 ___

Re: nginx on high load (upstream prematurely closed connection while reading response header from upstream)

Thankyou once again Francis Daly, i am now ignoring these errors, as i not see any errors in nginx access logs and site is working on high load and see 200 response code in access logs. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,266978,267053#msg-267053 ___

Re: nginx on high load (upstream prematurely closed connection while reading response header from upstream)

Dear Francis Daly , thankyou for your response, upstream is php-fpm server (127.0.0.1) and its also setup to handle huge load, during above errors, i see the site is opening fine. but don't know where to catch it. PM is also set on demand and maximum childerns set to 9 to handle the load, and n

nginx on high load (upstream prematurely closed connection while reading response header from upstream)

Dear Guys, I am facing strange issue, during load test and peak load of more than 3k concurrent users, get below errors in nginx logs continuously. 2016/05/18 11:23:28 [error] 15510#0: *6853 upstream prematurely closed connection while reading response header from upstream, client: x.x.x.x, serve