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: Thanks for the information. However this is new to me. I did try to see if GDB is installed, here is some output: [root@server~]# which -a gdb /usr/bin/which: no gdb in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/.local/bin:/root/bin) [root@server~]# locate -eb '\gdb' /usr/share/gdb [root@server~]# gdb -help -bash: gdb: command not found [root@server~]# gdb php-fpm /usr/local/php71/bin -bash: gdb: command not found [root@server ~]# gdb /usr/local/php71/bin -bash: gdb: command not found Any help to point me in the right direction? If not I will have to seek outside technical advice on this, wich could take several days or weeks. Previous Comments: ------------------------------------------------------------------------ [2018-04-16 11:41:54] nikic@php.net Sure, that's exactly what core dumps are for :) You need to run "gdb php-fpm path-to-core-file" and then "bt" or "bt full". It may be necessary to specify a full path to the php-fpm binary and to install debug symbols from your package manager, if they aren't installed yet. ------------------------------------------------------------------------ [2018-04-16 11:34:54] post at minhost dot no Is it possible to do after it has happened? As said it only happen sporadic. Also can you please point me to some guides for creating a backtrace from the core dumps AFTER the crash has already happened? ------------------------------------------------------------------------ [2018-04-16 11:30:15] nikic@php.net Can you please provide the backtrace(s) from the core dumps of the crashes? That may be enough to diagnose the problem. ------------------------------------------------------------------------ [2018-04-16 07:56:02] post at minhost dot no Yes I am sure! PHP-FPM is _crashed_ and will stay down until I reload PHP-FPM to get the site online again. ------------------------------------------------------------------------ [2018-04-16 07:50:15] requinix@php.net I suppose not - we'll just have to ask for more information anyways. The first thing I would ask is whether you're sure the 503 is coming from PHP/php-fpm itself and not the web server or Drupal. ------------------------------------------------------------------------ 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