Hello, It can also be oomkiller killing nginx due to low resources, you should monitor & check the other logs.
2015-12-04 16:43 GMT+02:00 Maxim Dounin <[email protected]>: > Hello! > > On Fri, Dec 04, 2015 at 07:57:42AM -0500, x-man wrote: > > > last few years I using nginx on very busy websites and all time all > working > > fine, never I don`t have problem with nginx crashing but now I move my > > websites to new server and I using same settings like on old server but > now > > nginx crashing every few hours, here is nginx -V info: > > [...] > > > 2015/12/04 08:09:45 [notice] 100692#0: signal 15 (SIGTERM) received, > exiting > ... > > 2015/12/04 08:09:45 [notice] 100692#0: exiting > ... > > 2015/12/04 08:09:45 [notice] 100691#0: signal 15 (SIGTERM) received, > exiting > ... > > 2015/12/04 08:09:45 [notice] 100690#0: signal 15 (SIGTERM) received, > exiting > ... > > 2015/12/04 08:09:45 [notice] 100691#0: exiting > ... > > 2015/12/04 08:09:45 [debug] 100690#0: wake up, sigio 0 > ... > > 2015/12/04 08:09:45 [debug] 100690#0: child: 0 100691 e:0 t:0 d:0 r:1 j:0 > ... > > 2015/12/04 08:09:45 [debug] 100690#0: child: 1 100692 e:0 t:0 d:0 r:1 j:0 > > [...] > > > Where can be problem? > > As per logs, someone or something send SIGTERM to all nginx > processes, including master (pid 100690) and all workers (100691, > 100692). Check your server to find out how this happened. > Usually such things happen due to bugs in log rotation scripts or > something similar. > > -- > Maxim Dounin > http://nginx.org/ > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
