|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #75107 opcache_reset will cause running FPM process stop with SIGKILL
Submitted: 2017-08-23 06:58 UTC Modified: 2021-08-15 04:22 UTC
Avg. Score:4.3 ± 0.9
Reproduced:5 of 5 (100.0%)
Same Version:1 (20.0%)
Same OS:2 (40.0%)
From: greatdeer at gmail dot com Assigned: cmb (profile)
Status: No Feedback Package: opcache
PHP Version: 5.6.31 OS: CentOS6.5
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: greatdeer at gmail dot com
New email:
PHP Version: OS:


 [2017-08-23 06:58 UTC] greatdeer at gmail dot com
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()?


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2018-01-01 21:02 UTC]
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
 [2021-08-06 11:13 UTC]
-Status: Open +Status: Feedback -Assigned To: +Assigned To: cmb
 [2021-08-06 11:13 UTC]
So, is/was this related to opcache.force_restart_timeout?  And
does it still happen to you with any of the actively supported PHP

[1] <>
 [2021-08-15 04:22 UTC] php-bugs at lists dot php dot net
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.
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Fri Aug 19 02:03:36 2022 UTC