<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">So this message can be interpreted:<div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><font face="Courier" color="#000000" class="">NOTICE: [pool www] child 25826 exited with </font><font face="Courier" color="#942192" class=""><b class="">code 0 </b></font><font face="Courier" color="#000000" class="">after </font><font face="Courier" color="#942192" class=""><b class="">864</b></font><font face="Courier" color="#000000" class="">.048588 seconds<br class="">from start</font></blockquote></div><div class=""><br class=""></div><div class="">The code 0 means that the child exited normally 864 seconds after it had started. In other words,</div><div class="">it chose to die (probably after serving 800 or 2500 requests).</div><div class="">Now if your access.log indicates *which* php process serves a request </div><div class="">then you should be able to work out whether 864 seconds is a reasonable </div><div class="">time for it to have received the appropriate number of requests.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><b class="">Monitoring nginx performance</b></div><div class=""><br class=""></div><div class="">The first thing is to configure nginx so that it logs how many milliseconds are spent building every request</div><div class=""><br class=""></div><div class="">See <a href="https://lincolnloop.com/blog/tracking-application-response-time-nginx/" class="">https://lincolnloop.com/blog/tracking-application-response-time-nginx/</a></div><div class=""><br class=""></div><div class="">It’s better that you email me off-list for further discussion</div><div class=""><br class=""></div><div class="">Peter</div><div class="">peter _ booth @ <a href="http://me.com" class="">me.com</a></div><div class=""><br class=""></div><div class="">Peter</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 17, 2017, at 1:48 AM, agriz <<a href="mailto:nginx-forum@forum.nginx.org" class="">nginx-forum@forum.nginx.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I am getting these kind of warning in php fpm log<br class=""><br class="">NOTICE: [pool www] child 25826 exited with code 0 after 864.048588 seconds<br class="">from start<br class="">NOTICE: [pool www] child 6580 started<br class=""><br class="">Sir, I am still looking for a way to monitor nginx performance. But i am not<br class="">able to find the solution in internet.<br class="">Can you please guide me how to monitor nginx?<br class=""><br class="">Something is still limiting the visitors from accessing the page after<br class="">certain limit.<br class=""><br class="">Posted at Nginx Forum: <a href="https://forum.nginx.org/read.php?2,276892,276909#msg-276909" class="">https://forum.nginx.org/read.php?2,276892,276909#msg-276909</a><br class=""><br class="">_______________________________________________<br class="">nginx mailing list<br class=""><a href="mailto:nginx@nginx.org" class="">nginx@nginx.org</a><br class="">http://mailman.nginx.org/mailman/listinfo/nginx<br class=""></div></div></blockquote></div><br class=""></div></body></html>