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.by muzi - Nginx Mailing List - English
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.by muzi - Nginx Mailing List - English
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.by muzi - Nginx Mailing List - English
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 90000 to handle the load, and no logs appears in php-fpm. Can you please suggest how to got the issue ?by muzi - Nginx Mailing List - English
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 15510#0: *6853 upstream prematurely closed connection while reading response header from upstream, client: x.x.x.x, server:abc.com, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: &qby muzi - Nginx Mailing List - English