<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I don't know if this is related to my problem, but since
yesterday evening (CET), all of my virtual servers and the
masternode were down. They were pingable tho, but no ssh response.
I had to physically reboot the server this morning, now it works.</p>
<p>was there some update/upgrade this night?</p>
<p>Best regards</p>
<p>Meaulnes Legler
</p>
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td>~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~</td>
</tr>
<tr>
<td>~ <tt> <a class="moz-txt-link-abbreviated" href="http://www.WaveWeb.ch">www.WaveWeb.ch</a> </tt> ~</td>
</tr>
<tr>
<td>~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~</td>
</tr>
<tr>
<td>~ <small><tt>Zurich, Switzerland</tt></small> ~
<br>
~ <small><tt>tel: +41 44 2601660</tt></small> ~</td>
</tr>
</tbody>
</table>
<br>
<br>
<div class="moz-cite-prefix">On 13.11.17 22:19, Chris Gebhardt -
VIRTBIZ Internet wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4f4cc24a-b7fe-1f70-6693-88120a45b04c@virtbiz.com">Hi
all,
<br>
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.
<br>
<br>
Here's a bit of the way this shakes out. Service fails, so we
check the httpd error log and get this:
<br>
[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
<br>
[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
<br>
<br>
The next step is to check the service status:
<br>
# systemctl status php-fpm-7.0.service
<br>
* php-fpm-7.0.service - The PHP-7.0 FastCGI Process Manager
<br>
Loaded: loaded (/usr/lib/systemd/system/php-fpm-7.0.service;
enabled; vendor preset: disabled)
<br>
Active: failed (Result: start-limit) since Mon 2017-11-13
14:41:04 CST; 7s ago
<br>
Process: 7231 ExecStart=/home/solarspeed/php-7.0/sbin/php-fpm
--nodaemonize (code=exited, status=78)
<br>
Main PID: 7231 (code=exited, status=78)
<br>
<br>
Nov 13 14:41:32 web40 systemd[1]: Failed to start The PHP-7.0
FastCGI Process Manager.
<br>
Nov 13 14:41:32 web40 systemd[1]: Unit php-fpm-7.0.service entered
failed state.
<br>
Nov 13 14:41:32 web40 systemd[1]: php-fpm-7.0.service failed.
<br>
Nov 13 14:41:32 web40 systemd[1]: php-fpm-7.0.service holdoff time
over, scheduling restart.
<br>
Nov 13 14:41:32 web40 systemd[1]: start request repeated too
quickly for php-fpm-7.0.service
<br>
Nov 13 14:41:32 web40 systemd[1]: Failed to start The PHP-7.0
FastCGI Process Manager.
<br>
Nov 13 14:41:32 web40 systemd[1]: Unit php-fpm-7.0.service entered
failed state.
<br>
Nov 13 14:41:32 web40 systemd[1]: php-fpm-7.0.service failed.
<br>
<br>
<br>
OK, clearly it's dead. So we'll issue a restart:
<br>
<br>
# systemctl restart php-fpm-7.0.service
<br>
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.
<br>
<br>
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.
<br>
<br>
Just thought I'd report it.
<br>
<br>
</blockquote>
<br>
</body>
</html>