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: 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? Previous Comments: ------------------------------------------------------------------------ [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. ------------------------------------------------------------------------ [2018-04-16 07:46:06] post at minhost dot no PHP-FPM is reloaded after any SSL cert installation because we run DirectAdmin, and that is the behaviour. I have now contacted DirectAdmin support and asked them why this is needed. I have not yet made a bug report regarding sporadic 503 errors when running update.php in Drupal, because I am not able to reproduce the error on every run, it only happen sporadic, and it can be days between one of my customers report that it happen. Then there is no useful information in the log files, and because I am not able to reproduce the error on demand, I am not able to debug it. Do you still think I should create a bug report? ------------------------------------------------------------------------ [2018-04-16 05:12:26] requinix@php.net Has this 503 bug been reported? I did quick searches here and only found your InfiniteWP bug https://bugs.php.net/bug.php?id=76205 And pardon my ignorance but why do you have to reload php-fpm when updating the web server's SSL cert? It's separate. ------------------------------------------------------------------------ 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