php-fpm backend, sigsegv and limit_conn
Grégory Pakosz
gpakosz at yahoo.fr
Thu Apr 19 12:23:40 UTC 2012
Hello,
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
11
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?
Regards,
Gregory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120419/67585468/attachment.html>
More information about the nginx
mailing list