Hide Forgot
On my F24 server, php-fpm always fails upon boot, but if I manually start the service, it works. I've tested the following: - disabling selinux (nothing changes) - checked the php-fpm logs (all I get are notices and debug messages, and nothing when setting the log level to ERROR) Below is a snippet of what I see when checking the status of the service: Code: # systemctl status php-fpm.service ● php-fpm.service - The PHP FastCGI Process Manager Loaded: loaded (/usr/lib/systemd/system/php-fpm.service; enabled; vendor preset: disabled) Active: failed (Result: signal) since Fri 2016-10-07 11:39:53 PDT; 54s ago Process: 915 ExecStart=/usr/sbin/php-fpm --nodaemonize (code=killed, signal=KILL) Main PID: 915 (code=killed, signal=KILL) Oct 07 11:39:31 *.com systemd[1]: Starting The PHP FastCGI Process Manager... Oct 07 11:39:41 *.com systemd[1]: php-fpm.service: Start operation timed out. Terminating. Oct 07 11:39:52 *.com systemd[1]: php-fpm.service: State 'stop-final-sigterm' timed out. Killing. Oct 07 11:39:53 *.com systemd[1]: php-fpm.service: Main process exited, code=killed, status=9/KILL Oct 07 11:39:53 *.com systemd[1]: Failed to start The PHP FastCGI Process Manager. Oct 07 11:39:53 *.com systemd[1]: php-fpm.service: Unit entered failed state. Oct 07 11:39:53 *.com systemd[1]: php-fpm.service: Failed with result 'signal'. I have the same user for php-fpm and nginx (user is "nginx") Please let me know what information you need to assist with debugging this
Please try with default provided configuration (so with default "apache" user). BTW FPM doesn't need to run under nginx user, nginx user is allowed to connect to the socket, and everything should work out-of-the-box, with box nginx and php-fpm default configuration. More, packaged applications rely on this configuration.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.