Welcome! Log In Create A New Profile

Advanced

killed child process

May 18, 2017 09:30PM
Hi

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
time

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 ...

Alex
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

killed child process

alexsamad May 18, 2017 09:30PM

Re: killed child process

Maxim Dounin May 19, 2017 09:12AM

Re: killed child process

alexsamad May 19, 2017 05:42PM

Re: killed child process

B.R. via nginx May 20, 2017 07:14AM

Re: killed child process

alexsamad May 20, 2017 06:08PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 76
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready