Monitoring alert -- Execution failed php-fpm

anothernas · Jul 22nd 2023

Sometimes when booting OMV I get an email with an error message "Execution failed php-fpm". This only happens with what feels like every 10th boot, but not for the first time.

Code: email

The system monitoring needs your attention.

Host:        ananas
Date:        Wed, 19 Jul 2023 08:21:43
Service:     php-fpm
Event:       Execution failed
Description: failed to start (exit status -1) -- no output

This triggered the monitoring system to: alert

—
You have received this notification because you have enabled the system monitoring on this host.

Display More

What can be the reason and what can be improved so that the system boots reliably without an error message?

macom · Jul 22nd 2023

Boot less often

You can check the logs with journalctl -u php7.4-fpm.service.

You can also try to delay the start of monit a bit. What kind of hardware are you using?

anothernas · Jul 22nd 2023

The log output is very short (and says nothing to me):

Code: uncut

root@ananas:~# journalctl -u php7.4-fpm.service
-- Journal begins at Sat 2023-06-10 01:07:48 CEST, ends at Sat 2023-07-22 11:10:04 CEST. --
Jul 17 21:11:13 ananas systemd[1]: Stopping The PHP 7.4 FastCGI Process Manager...
root@ananas:~#

Hardware is an Intel Celeron J4125 CPU with 8 GB RAM.

systemd-analyze says Startup finished in 6.647s (firmware) + 6.889s (loader) + 4.276s (kernel) + 10.654s (userspace) = 28.468s

macom · Jul 22nd 2023

Yep, not helpful.

To delay the start of monit to 30s:

Code

omv-env set OMV_MONIT_CHECK_START_DELAY 30
omv-salt stage run prepare
omv-salt deploy run monit

anothernas · Jul 29th 2023

I am not sure if it is a good idea to delay the start of services in my installation. It may end up causing other problems elsewhere.

It also doesn't help to boot less frequently - that only reduces the probability of occurrence, but doesn't fix the cause. Actually, I would expect services to be started by default in an order that does not lead to errors.

Are you sure that this is not a bug in OMV that only shows up at boot time and not always? And which has not yet been detected and fixed in the default installation, because many systems are not booted often?

macom · Jul 29th 2023

Monit is just monitoring if services are running (if it has been configured to do so). So if you delay the start of monit by 30s, you will just receive the mail 30s later (if the service is not ready, yet). If you are lucky the service is already running and you don't get a mail.

Otherwise you would have to find out why php-fpm failed to start, but succeeds later.

Soma · Jul 29th 2023

Just disable monitoring and see what happens on reboot.

anothernas · Jul 30th 2023

Quote from macom

you would have to find out why php-fpm failed to start

Since I have no idea what should normally happen in what order and triggered by what.... How do I find out the next time it happens?

macom · Jul 30th 2023

journalctl -u php7.4-fpm.service should give some hints. But when you tried earlier in this thread it did not. Maybe because the journal was already cleared after the last time it happened. But the mail was from 19th July and the journal begins at 10th June. So I have no idea.

macom · Jul 30th 2023

What is the output of

dpkg -l | grep php

Participate now!