|
|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
[2018-02-12 10:13 UTC] 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 PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2024 The PHP GroupAll rights reserved. |
Last updated: Sat Dec 21 12:01:31 2024 UTC |
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