Bug #75953 [Com]: Reload signal should return error code when PHP-FPM init failed
Edit report at https://bugs.php.net/bug.php?id=75953&edit=1
ID: 75953
Comment by: pim at lemonbit dot com
Reported by: pim at lemonbit dot com
Summary: Reload signal should return error code when PHP-FPM
init failed
Status: Open
Type: Bug
Package: FPM related
Operating System: CentOS 7
PHP Version: 7.1.14
Block user comment: N
Private report: N
New Comment:
Excerpt from log (reload reports OK but php-fpm fails):
NOTICE: Reloading in progress ...
NOTICE: reloading: execvp("/opt/remi/php71/root/usr/sbin/php-fpm",
{"/opt/remi/php71/root/usr/sbin/php-fpm", "--nodaemonize"})
ERROR: An another FPM instance seems to already listen on <redacted-path>.sock
ERROR: FPM initialization failed
Previous Comments:
------------------------------------------------------------------------
[2018-02-12 10:13:45] pim at lemonbit dot com
Description:
------------
When reloading the php-fpm daemon you would expect it to return an error code when the php-fpm
initilization failed. However, we saw that the reload reported OK, but the php-fpm daemon still
failed.
Test script:
---------------
- Use a configuration that results in a failure, i.e. php-fpm pool with socket that is already in
use by another instance.
- Reload the php-fpm daemon with "kill -USR2 <pid>"
Expected result:
----------------
- Error exit code
Actual result:
--------------
- OK exit code
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=75953&edit=1
Thread (3 messages)