Edit report at https://bugs.php.net/bug.php?id=62418&edit=1
ID: 62418 Updated by: php-bugs@lists.php.net Reported by: php at scratchspace dot com Summary: php-fpm master process crashes -Status: Feedback +Status: No Feedback Type: Bug Package: FPM related Operating System: CentOS 6.2 x86_x64 PHP Version: 5.3.14 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2013-02-12 10:59:49] webmaster at jbfavre dot org Hello, We have the same problem, with PHP 5.3.21 behind Nginx 1.2.6. Happens, sometimes, at PHP-FPM reload, after updating the code. We're running a Symfony web app, on Ubuntu 10.04 Lucid with home-made PHP packages. Enabled modules --------------- amqp 1.0.9 apc 3.1.9 curl 5.3.21 gd 5.3.21 geoip 1.0.8 igbinary 1.1.1 intl 5.3.21 memcached 2.1.0 mongo 1.3.0 mysql 5.3.21 pinba 1.1.0 redis 2.2.2 Have just modified FPM configuration to use 'poll' instead of default 'epoll'. Will see what happen. 2 backtraces available (I can provide coredumps upon request) ------------------------------------------------------------ ############################### #0 0x0000444c48434749 in ?? () #1 0x0000000000761703 in fpm_event_epoll_wait (queue=0x1f270e8, timeout=3) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/events/epoll.c:143 #2 0x0000000000755e0f in fpm_event_loop (err=0) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/fpm_events.c:403 #3 0x0000000000750d67 in fpm_run (max_requests=0x7fff3704f79c) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/fpm.c:113 #4 0x000000000075872e in main (argc=3, argv=0x7fff37051908) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/fpm_main.c:1838 ############################### #0 0x00000000007558d6 in fpm_event_fire (ev=0x2ae4d78) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/fpm_events.c:459 #1 0x0000000000761703 in fpm_event_epoll_wait (queue=0x2ae4d78, timeout=3) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/events/epoll.c:143 #2 0x0000000000755e0f in fpm_event_loop (err=0) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/fpm_events.c:403 #3 0x0000000000750d67 in fpm_run (max_requests=0x7fff94e7286c) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/fpm.c:113 #4 0x000000000075872e in main (argc=3, argv=0x7fff94e749d8) at /tmp/buildd/php5-5.3.21/sapi/fpm/fpm/fpm_main.c:1838 Regards, Jean Baptiste Favre ------------------------------------------------------------------------ [2012-07-04 10:30:04] f...@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. If you were able to give us a complete and detailed stack trace it would be useful. thx ------------------------------------------------------------------------ [2012-06-27 20:10:08] ras...@php.net Not sure. Many people out there run with epoll without problems. ------------------------------------------------------------------------ [2012-06-27 18:28:14] php at scratchspace dot com We've been up and running for 24 hours with "events.mechanism = poll" and no problems. Let's give it a couple of days to be sure this workaround works. Is this issue specific to epoll and the way we have php-fpm configured (to use minimal resources), or is this is a bug in php-fpm that can ultimately be fixed? ------------------------------------------------------------------------ [2012-06-26 06:10:02] ras...@php.net Could you check if it is related to epoll? In your php-fpm.conf file, set: events.mechanism = poll to try with "poll" instead. You can also try setting it to "select" ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=62418 -- Edit this bug report at https://bugs.php.net/bug.php?id=62418&edit=1
