Req #76225 [Com]: ini setting to not empty opcache when php-fpm is reloaded

Edit report at https://bugs.php.net/bug.php?id=76225&edit=1 ID: 76225 Comment by: post at minhost dot no Reported by: post at minhost dot no Summary: ini setting to not empty opcache when php-fpm is reloaded Status: Open Type: Feature/Change Request Package: opcache Operating System: CentOS 7.4 PHP Version: 7.1.16 Block user comment: N Private report: N New Comment: I have now added a comment on this InfiniteWP/WordPress bug with backtrace of the core dumps: https://bugs.php.net/bug.php?id=76205 - I will soon create a new bug report for the crash in Drupal, wich might be related to this bug. Previous Comments: ------------------------------------------------------------------------ [2018-04-23 20:23:14] post at minhost dot no Thank you for information about SIGABRT being related to the debug build. Finally I am able to generate core dump files! On my CentOS 7.4 server it was needed to change fs.suid_dumpable from default 0 to become 1 I might need a couple of hours, then I will update my bug reports. ------------------------------------------------------------------------ [2018-04-23 19:44:48] nikic@php.net SIGABRT (most likely) indicates that an assertion failure occurred. These only happen in debug builds, so it's expected that you see a different behavior in non-debug builds. SIGABRT should also be generating core dumps. I'm not sure why this doesn't work for you. One more thing to check would be if you have the rlimit_core option specified in an fpm pool config. It should be either not present at all, or set to rlimit_core=unlimited. ------------------------------------------------------------------------ [2018-04-23 18:59:29] post at minhost dot no The crazy thing is that on the test server with a copy of the sites from production server, I only get SIGABRT in php-fpm.log when php-fpm/opcache crashes, but on the production server I get SIGSEGV in php-fpm.log when php-fpm/opcache crashes on the same sites. ------------------------------------------------------------------------ [2018-04-23 18:52:12] post at minhost dot no Please note that whenever php-fpm/opcache crash, it causes a SIGABRT in php-fpm.log like this: [23-Apr-2018 20:35:50] WARNING: [pool asle] child 949 exited on signal 6 (SIGABRT) after 169.991198 seconds from start And no core dump file is generated in /tmp - is it because it is a SIGABRT and not a SIGSEGV? Should I be able to get a core dump file on crash with SIGABRT? ------------------------------------------------------------------------ [2018-04-23 10:57:22] post at minhost dot no I was able to get one step closer to generating core dumps. It seems I needed to add the following to /etc/security/limits.conf: * soft core unlimited After doing that I was able to get a core file in /tmp when running this command: kill -s SIGSEGV $$ However when php-fpm/opcache crash, there is still not generated any core files in /tmp I have even changed PrivateTmp=true to be PrivateTmp=false - but still no luck. ------------------------------------------------------------------------ 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=76225 -- Edit this bug report at https://bugs.php.net/bug.php?id=76225&edit=1