Reload of NGinX doesnt kill some of the older worker processes

Maxim Dounin mdounin at
Mon May 15 16:58:57 UTC 2017


On Mon, May 15, 2017 at 12:41:37PM -0400, shivramg94 wrote:

> Earlier, it says the pid file doesn't exist even though the master and
> worker processes were running.
> 2017/05/12 15:35:41 [notice] 19042#0: signal process started
> 2017/05/12 15:35:41 [error] 19042#0: open() "/u01/data/logs/"
> failed (2: No such file or directory)
> Can the above issue ( where the file went missing) and the
> communication break up between the master and the worker processes be
> correlated?

This message is from signal process, 19042, and indicate only that 
"nginx -s" was used incorrectly (likely with wrong configuration).  
And not, this is not something that can break master / worker 
communication.  Look for 'alert' and 'crit' messages.

Maxim Dounin

More information about the nginx mailing list