killed child process

Alex Samad alex at
Fri May 19 01:28:05 UTC 2017


so I have lots of clients on long lived tcp connections , getting rp into 2
back end app servers

I had a line in my error log, saying one of the upstream was failed caused
it timeout -

then I got this

2017/05/18 13:30:42 [notice] 2662#2662: exiting
2017/05/18 13:30:42 [notice] 2662#2662: exit
2017/05/18 13:30:42 [notice] 2661#2661: signal 17 (SIGCHLD) received
2017/05/18 13:30:42 [notice] 2661#2661: worker process 2662 exited with
code 0
2017/05/18 13:30:42 [notice] 2661#2661: signal 29 (SIGIO) received

I am not sure what initiated this ? there are no cron jobs running at that

and it looks like a lot of my long lived tcp session where TCP-FIN'ed.

I also checked my audit logs to see what command / process run at that time
... nothing that signaled or initiated a nginx reload ...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list