php-fpm backend, sigsegv and limit_conn

Grégory Pakosz gpakosz at
Thu Apr 19 12:23:40 UTC 2012


I'm facing the situation where worker process crashes in the php-fpm
backend with SIGSEGV: [alert] 5712#0: worker process 5713 exited on signal

In such a case, what happens to the connection? is it dangling?
Crashes in the backend are random, and I have the impression that when too
many crashes happen in a row, connection stay open and eventually I'm
hitting limit_conn.

What do you think?

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

More information about the nginx mailing list