Re: Reload of NGinX doesnt kill some of the older worker processes

Hello! 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/dat

Re: Reload of NGinX doesnt kill some of the older worker processes

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/nginx.pid" failed (2: No such file or directory) Can the above issue ( wh

Re: Reload of NGinX doesnt kill some of the older worker processes

Hello! On Mon, May 15, 2017 at 11:37:54AM -0400, shivramg94 wrote: > Hi Maxim, > > This is what I could find in the error logs > > 2017/05/15 11:32:18 [notice] 21499#0: signal process started > 2017/05/15 11:32:19 [alert] 22030#0: sendmsg() failed (88: Socket operation > on non-socket) > 2017/0

Re: Reload of NGinX doesnt kill some of the older worker processes

At times, the error logs say 2017/05/15 11:37:01 [notice] 9#0: signal process started 2017/05/15 11:37:02 [alert] 22030#0: sendmsg() failed (32: Broken pipe) 2017/05/15 11:37:02 [alert] 22030#0: sendmsg() failed (32: Broken pipe) 2017/05/15 11:37:04 [alert] 22030#0: sendmsg() failed (9: Bad fi

Re: Reload of NGinX doesnt kill some of the older worker processes

Hi Maxim, This is what I could find in the error logs 2017/05/15 11:32:18 [notice] 21499#0: signal process started 2017/05/15 11:32:19 [alert] 22030#0: sendmsg() failed (88: Socket operation on non-socket) 2017/05/15 11:32:19 [alert] 22030#0: sendmsg() failed (32: Broken pipe) 2017/05/15 11:32:19

Re: Reload of NGinX doesnt kill some of the older worker processes

Hello! On Mon, May 15, 2017 at 06:54:47AM -0400, shivramg94 wrote: > I am facing an issue where once I issued a reload to the NGinX binary, few > of the older worker processes are not dying. They still remain orphaned. > > This is the configuration before issuing a reload : > > [poduser@ucfc2z

Reload of NGinX doesnt kill some of the older worker processes

I am facing an issue where once I issued a reload to the NGinX binary, few of the older worker processes are not dying. They still remain orphaned. This is the configuration before issuing a reload : [poduser@ucfc2z3a-1582-lb8-nginx1 logs]$ ps -ef | grep nginx poduser 12540 22030 0 06:39 ?