Req #76225 [Fbk->Opn]: 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 Updated by: requinix@php.net Reported by: post at minhost dot no Summary: ini setting to not empty opcache when php-fpm is reloaded -Status: Feedback +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 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. Previous Comments: ------------------------------------------------------------------------ [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. ------------------------------------------------------------------------ [2018-04-16 00:16:56] post at minhost dot no Description: ------------ On shared hosting servers users can add and delete domains, and install Let's Encrypt SSL certificates, and they do many times each day, but this clears OPcache each time, because PHP-FPM is reloaded. To avoid empty OPcache for first visits to users PHP pages after each PHP-FPM reload, we have setup file cache as second level fallback OPcache. However ever since PHP 7.1.12 users are sporadic getting 503 errors when running update.php in Drupal (and PHP-FPM crashes). We have not been able to figure out what goes wrong, but it never happened in PHP 7.1.11 (we are now on PHP 7.1.16). I suspect this is related to running file cache as second level fallback OPcache and new bugs in file cache from PHP version 7.1.12 and newer. Because of this problem, we would like to stop running file cache as second level fallback OPcache, and only run OPcache in RAM. To eliminate the need of running file cache as second level fallback OPcache, we need to avoid OPcache being purged on every PHP-FPM reload. Can you please add a OPcache .ini setting that allow us to disable purging of OPcache after PHP-FPM is reloaded, so that we can stop using file cache, and only use OPcache in RAM. Or even better, can you please disable purgin of OPcache after PHP-FPM reload, and only purge OPcache when PHP-FPM is restarted? ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=76225&edit=1