[BlueOnyx:21519] systemd php-fpm-7.0.service dies, won't restart
Chris Gebhardt - VIRTBIZ Internet
cobaltfacts at virtbiz.com
Mon Nov 13 16:19:02 -05 2017
Hi all,
I wonder if anyone else has had trouble with PHP-FPM on BlueOnyx5209R /
CentOS 7 dying and then not being able to restart? I have run into
this again today with one of our shared hosting systems. The good news
is that sites not on the particular PHP runs fine. The bad news is that
the server has to be rebooted to get the affected PHP back up and
running again.
Here's a bit of the way this shakes out. Service fails, so we check the
httpd error log and get this:
[Mon Nov 13 14:39:51.512076 2017] [proxy:error] [pid 6790]
(111)Connection refused: AH00957: FCGI: attempt to connect to
127.0.0.1:9040 (*) failed
[Mon Nov 13 14:39:51.512150 2017] [proxy_fcgi:error] [pid 6790] [client
217.182.132.187:34724] AH01079: failed to make connection to backend:
127.0.0.1
The next step is to check the service status:
# systemctl status php-fpm-7.0.service
* php-fpm-7.0.service - The PHP-7.0 FastCGI Process Manager
Loaded: loaded (/usr/lib/systemd/system/php-fpm-7.0.service;
enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Mon 2017-11-13 14:41:04
CST; 7s ago
Process: 7231 ExecStart=/home/solarspeed/php-7.0/sbin/php-fpm
--nodaemonize (code=exited, status=78)
Main PID: 7231 (code=exited, status=78)
Nov 13 14:41:32 web40 systemd[1]: Failed to start The PHP-7.0 FastCGI
Process Manager.
Nov 13 14:41:32 web40 systemd[1]: Unit php-fpm-7.0.service entered
failed state.
Nov 13 14:41:32 web40 systemd[1]: php-fpm-7.0.service failed.
Nov 13 14:41:32 web40 systemd[1]: php-fpm-7.0.service holdoff time over,
scheduling restart.
Nov 13 14:41:32 web40 systemd[1]: start request repeated too quickly for
php-fpm-7.0.service
Nov 13 14:41:32 web40 systemd[1]: Failed to start The PHP-7.0 FastCGI
Process Manager.
Nov 13 14:41:32 web40 systemd[1]: Unit php-fpm-7.0.service entered
failed state.
Nov 13 14:41:32 web40 systemd[1]: php-fpm-7.0.service failed.
OK, clearly it's dead. So we'll issue a restart:
# systemctl restart php-fpm-7.0.service
Job for php-fpm-7.0.service failed because the control process exited
with error code. See "systemctl status php-fpm-7.0.service" and
"journalctl -xe" for details.
No go. Don't have a lot of time to screw around because the server
should be in production in the middle of the day. So we reboot. And
that clears whatever the issue is.
Just thought I'd report it.
--
Chris Gebhardt
VIRTBIZ Internet Services
Access, Web Hosting, Colocation, Dedicated
www.virtbiz.com | toll-free (866) 4 VIRTBIZ
More information about the Blueonyx
mailing list