Keep Alive piles up

meto nginx-forum at nginx.us
Fri Jun 26 17:06:36 MSD 2009


There's been a massacre at 3pm for nginx procs:
2009/06/26 14:56:35  3039#0: worker process 3040 exited on signal 11
2009/06/26 14:56:35  3039#0: worker process 3043 exited on signal 11
2009/06/26 14:56:36  3039#0: worker process 3041 exited on signal 11
2009/06/26 14:56:36  3039#0: worker process 6622 exited on signal 11
2009/06/26 14:56:36  3039#0: worker process 3042 exited on signal 11
2009/06/26 14:56:36  3039#0: worker process 6625 exited on signal 11
2009/06/26 14:56:36  3039#0: worker process 6623 exited on signal 11
2009/06/26 14:56:36  3039#0: worker process 6626 exited on signal 11
2009/06/26 14:56:36  3039#0: worker process 6627 exited on signal 11
2009/06/26 14:56:37  3039#0: worker process 6624 exited on signal 11
2009/06/26 14:56:37  3039#0: worker process 6630 exited on signal 11
2009/06/26 14:56:37  3039#0: worker process 6631 exited on signal 11
2009/06/26 14:56:37  3039#0: worker process 6632 exited on signal 11
2009/06/26 14:56:39  3039#0: worker process 6633 exited on signal 11
2009/06/26 14:56:39  3039#0: worker process 6634 exited on signal 11

That's also viewable on the graph (http://xgame.pl/nginx/), but no coredump was saved due to chmod i believe :/ So, that was a good guess with workers dieing. I'll try to provide coredumps later on.

The second question is why were there so many of them, since i've set worker numer to 4 and affinity proc/core. maybe thets the problem?

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,3374,3426#msg-3426






More information about the nginx mailing list