Bug #75107 [Fbk->NoF]: opcache_reset will cause running FPM process stop with SIGKILL

Edit report at https://bugs.php.net/bug.php?id=75107&edit=1 ID: 75107 Updated by: php-bugs@lists.php.net Reported by: greatdeer at gmail dot com Summary: opcache_reset will cause running FPM process stop with SIGKILL -Status: Feedback +Status: No Feedback Type: Bug Package: opcache Operating System: CentOS6.5 PHP Version: 5.6.31 Assigned To: cmb Private report: N 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 "Re-Opened". Thank you. Previous Comments: ------------------------------------------------------------------------ [2021-08-06 11:13:16] cmb@php.net So, is/was this related to opcache.force_restart_timeout? And does it still happen to you with any of the actively supported PHP versions[1]? [1] <https://www.php.net/supported-versions.php> ------------------------------------------------------------------------ [2018-01-01 21:02:24] nikic@php.net opcache_reset() triggers an opcache restart. If a process holds onto an SHM lock for more than opcache.force_restart_timeout seconds after the restart is initiated, it will be killed. See also http://php.net/manual/en/opcache.configuration.php#ini.opcache.force-restart-timeout. ------------------------------------------------------------------------ [2017-08-23 06:58:53] greatdeer at gmail dot com Description: ------------ I use Nginx and PHP-FPM, Occasionally, php-fpm.log will report SIGKILL ("WARNING: [pool www] child 12197 exited on signal 9 (SIGKILL) after 2046.724398 seconds from start") with no more messages. I look for the reason for a long time, and finally I found it. It was opcache_reset. When I update the php codes, opcache_reset() will be triggered to make the codes validate immediately. And sometimes some scripts were executing just the same time and would crash. Is it a bug? or I should avoid useing opcache_reset()? ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=75107&edit=1