Edit report at https://bugs.php.net/bug.php?id=61689&edit=1
ID: 61689 Updated by: php-bugs@lists.php.net Reported by: eugene at zhegan dot in Summary: php-fpm children crashes on exit -Status: Feedback +Status: No Feedback Type: Bug Package: FPM related Operating System: FreeBSD 9.0-RELEASE PHP Version: 5.3.10 Assigned To: fat 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: ------------------------------------------------------------------------ [2012-05-23 18:20:01] 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. I can't do anything w/o a coredump. You should check your ulimits configuration, the directory where FPM children process are in (chdir FPM parameter), the rights of this directory and ensure rlimit_core FPM parameter is not set (to use default ulimit values). ------------------------------------------------------------------------ [2012-04-10 14:54:02] eugene at zhegan dot in Description: ------------ I use an nginx + php-fpm installation. Php-fpm is installed form ports. The problem is, that php-fpm children sometimes (not always) got signal 11 when the master process attempts to rotate em: [10-Apr-2012 20:46:30.072189] DEBUG: pid 14165, fpm_got_signal(), line 72: received SIGCHLD [10-Apr-2012 20:46:30.072278] WARNING: pid 14165, fpm_children_bury(), line 252: [pool www] child 14590 exited on signal 11 (SIGSEGV) after 121.434207 seconds from start Seems like this doesn't affect the production process, but anyway this bothers me and I think you will agree that bugs should be attempted to be fixed. I would be really glad to present you a backtrace, but unfortunately I don't see any corefiles anywhere. Core dumps are enabled, even for suid/gid processes: # sysctl -a | grep core kern.corefile: %N.core kern.nodump_coredump: 0 kern.coredump: 1 kern.sugid_coredump: 1 debug.elf64_legacy_coredump: 0 debug.ncores: 5 debug.elf32_legacy_coredump: 0 But still no cores. Test script: --------------- I don't think this is relatred to some particular script. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=61689&edit=1