Php-fpm service down
Hi,
Received email like RECOVERED : apache_php_fpm
[2024-04-22 03:13:03 +0530] OOM check ....Done
[2024-04-22 03:13:03 +0530] Service check ....
apache_php_fpm [[check command:-][check command output:(XID 6junc7) The “Apache PHP-FPM 71” service is down.
The subprocess “/usr/local/cpanel/scripts/restartsrv_apache_php_fpm” reported error number 29 when it ended.][socket connect:N/A][fail count:1]Restarting apache_php_fpm....
[notify:failed service:apache_php_fpm]]...Done
[2024-04-22 03:18:05 +0530] OOM check ....Done
[2024-04-22 03:18:05 +0530] Service check ....
apache_php_fpm [[check command:+][socket connect:N/A][notify:recovered service:apache_php_fpm]]...Done
cat /opt/cpanel/ea-php71/root/usr/var/log/php-fpm/error.log
[22-Apr-2024 03:13:05] NOTICE: using inherited socket fd=72, "/opt/cpanel/ea-php71/root/usr/var/run/php-fpm/aafe540c471953a6812f7fa78759c722d9932b67.sock"
[22-Apr-2024 03:13:05] NOTICE: fpm is running, pid 420193
[22-Apr-2024 03:13:05] NOTICE: ready to handle connections
[22-Apr-2024 03:13:05] NOTICE: systemd monitor interval set to 10000ms
[22-Apr-2024 03:13:05] NOTICE: Terminating ...
[22-Apr-2024 03:13:05] NOTICE: exiting, bye-bye!
Service was down , but there is no entry in error log, why it was down, is there any way to find out .
-
Hey there! If there isn't any additional data about the system being down in the main Apache error log at /etc/apache/logs/error_log, you may want to check the specific PHP 7.1 log as outlined here:
https://support.cpanel.net/hc/en-us/articles/360061253694-Where-are-the-global-PHP-FPM-logs-located
as I would expect that to have more information.
0 -
I already posted error from "/opt/cpanel/ea-php71/root/usr/var/log/php-fpm/error.log"
in that it shows only this at the time
~~~
[22-Apr-2024 03:13:05] NOTICE: using inherited socket fd=72, "/opt/cpanel/ea-php71/root/usr/var/run/php-fpm/aafe540c471953a6812f7fa78759c722d9932b67.sock"
[22-Apr-2024 03:13:05] NOTICE: fpm is running, pid 420193
[22-Apr-2024 03:13:05] NOTICE: ready to handle connections
[22-Apr-2024 03:13:05] NOTICE: systemd monitor interval set to 10000ms
[22-Apr-2024 03:13:05] NOTICE: Terminating ...
[22-Apr-2024 03:13:05] NOTICE: exiting, bye-bye!
~~~0 -
It's also possible the service wasn't down and was just so busy that the monitoring tool *thought* it was offline. Do you see more traffic than usual during that period?
0 -
Hello,
As it was midnight 03:13 AM, there are no high traffic at the time on server0 -
I don't have a good explanation for that behavior on my end. If you don't see anything in the logs, it might just be best to wait and see if the issue happens again at the same time. If it does, you can always reach out through a ticket.
0
Please sign in to leave a comment.
Comments
5 comments