There's been a massacre at 3pm for nginx procs:
2009/06/26 14:56:35 [alert] 3039#0: worker process 3040 exited on signal 11
2009/06/26 14:56:35 [alert] 3039#0: worker process 3043 exited on signal 11
2009/06/26 14:56:36 [alert] 3039#0: worker process 3041 exited on signal 11
2009/06/26 14:56:36 [alert] 3039#0: worker process 6622 exited on signal 11
2009/06/26 14:56:36 [alert] 3039#0: worker process 3042 exited on signal 11
2009/06/26 14:56:36 [alert] 3039#0: worker process 6625 exited on signal 11
2009/06/26 14:56:36 [alert] 3039#0: worker process 6623 exited on signal 11
2009/06/26 14:56:36 [alert] 3039#0: worker process 6626 exited on signal 11
2009/06/26 14:56:36 [alert] 3039#0: worker process 6627 exited on signal 11
2009/06/26 14:56:37 [alert] 3039#0: worker process 6624 exited on signal 11
2009/06/26 14:56:37 [alert] 3039#0: worker process 6630 exited on signal 11
2009/06/26 14:56:37 [alert] 3039#0: worker process 6631 exited on signal 11
2009/06/26 14:56:37 [alert] 3039#0: worker process 6632 exited on signal 11
2009/06/26 14:56:39 [alert] 3039#0: worker process 6633 exited on signal 11
2009/06/26 14:56:39 [alert] 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?



Edited 1 time(s). Last edit at 06/26/2009 09:07AM by meto.