So this message can be interpreted:

> NOTICE: [pool www] child 25826 exited with code 0 after 864.048588 seconds
> from start


The code 0 means that the child exited normally 864 seconds after it had started. In other words,
it chose to die (probably after serving 800 or 2500 requests).
Now if your access.log indicates *which* php process serves a request
then you should be able to work out whether 864 seconds is a reasonable
time for it to have received the appropriate number of requests.


Monitoring nginx performance

The first thing is to configure nginx so that it logs how many milliseconds are spent building every request

See https://lincolnloop.com/blog/tracking-application-response-time-nginx/ https://lincolnloop.com/blog/tracking-application-response-time-nginx/

It’s better that you email me off-list for further discussion

Peter
peter _ booth @ me.com

Peter


> On Oct 17, 2017, at 1:48 AM, agriz <nginx-forum@forum.nginx.org> wrote:
>
> I am getting these kind of warning in php fpm log
>
> NOTICE: [pool www] child 25826 exited with code 0 after 864.048588 seconds
> from start
> NOTICE: [pool www] child 6580 started
>
> Sir, I am still looking for a way to monitor nginx performance. But i am not
> able to find the solution in internet.
> Can you please guide me how to monitor nginx?
>
> Something is still limiting the visitors from accessing the page after
> certain limit.
>
> Posted at Nginx Forum: https://forum.nginx.org/read.php?2,276892,276909#msg-276909
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx