I did this: RE: rrdcached service, running/not running, does not exist?
... but I'm still getting these alert mails on reboot...
Monitoring alerts
-
- OMV 7.x
- gelöst
- ErikDB
-
Regarding which services do you get the mails?
What is the time difference between pressing the ON button and the reception of the mails?
-
-
What is the time difference between pressing the ON button and the reception of the mails?
3 minutes:
Coderoot@NASLG2:~# date Fri Apr 5 18:37:01 CEST 2024 root@NASLG2:~# reboot root@NASLG2:~# Connection to 192.168.1.10 closed by remote host. Connection to 192.168.1.10 closed.Regarding which services do you get the mails?
collectd
nginx
rrdcached
Code
Alles anzeigenThe system monitoring needs your attention. Host: NASLG2 Date: Fri, 05 Apr 2024 18:39:07 Service: collectd Event: Does not exist Description: process is not running This triggered the monitoring system to: restart — You have received this notification because you have enabled the system monitoring on this host. To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.Code
Alles anzeigenThe system monitoring needs your attention. Host: NASLG2 Date: Fri, 05 Apr 2024 18:39:07 Service: nginx Event: Execution failed Description: failed to start (exit status -1) -- Program '/bin/systemctl start nginx' timed out after 30 s This triggered the monitoring system to: alert — You have received this notification because you have enabled the system monitoring on this host. To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.Etc
-
What is the output of
journalctl -u nginx?
as example
-
What is the output of
journalctl -u nginx?
as example
Coderoot@NASLG2:~# journalctl -u nginx Mar 30 05:41:21 NASLG2 systemd[1]: Stopping nginx.service - A high performance web server and a reverse proxy server... Mar 30 05:41:21 NASLG2 systemd[1]: nginx.service: Deactivated successfully. Mar 30 05:41:21 NASLG2 systemd[1]: Stopped nginx.service - A high performance web server and a reverse proxy server. Mar 30 05:41:21 NASLG2 systemd[1]: nginx.service: Consumed 40.507s CPU time. -- Boot 6fc0889755404259a302a7bd08e19e21 -- Apr 01 07:36:49 NASLG2 systemd[1]: Stopping nginx.service - A high performance web server and a reverse proxy server... Apr 01 07:36:50 NASLG2 systemd[1]: nginx.service: Deactivated successfully. Apr 01 07:36:50 NASLG2 systemd[1]: Stopped nginx.service - A high performance web server and a reverse proxy server. Apr 01 07:36:50 NASLG2 systemd[1]: nginx.service: Consumed 1.541s CPU time. -
-
Strange. After the boot there should be a "Starting nginx.service..."
Here one example from my system
Code-- Boot 1c9a134eb29e47718c97b8de765a1f2b -- Mar 25 18:20:58 omv7 systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server... Mar 25 18:20:59 omv7 systemd[1]: Started nginx.service - A high performance web server and a reverse proxy server. Mar 25 18:22:23 omv7 systemd[1]: Stopping nginx.service - A high performance web server and a reverse proxy server... Mar 25 18:22:23 omv7 systemd[1]: nginx.service: Deactivated successfully. Mar 25 18:22:23 omv7 systemd[1]: Stopped nginx.service - A high performance web server and a reverse proxy server. -- Boot 0cd24d712f434c418ff31cda541c1311 --What is the output of systemctl status nginx?
-
What is the output of systemctl status nginx?
Code
Alles anzeigenroot@NASLG2:~# systemctl status nginx ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enabled) Active: active (running) since Fri 2024-04-05 18:39:35 CEST; 18h ago Docs: man:nginx(8) Process: 1681 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Process: 1699 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Main PID: 1703 (nginx) Tasks: 5 (limit: 4509) Memory: 11.7M CPU: 485ms CGroup: /system.slice/nginx.service ├─1703 "nginx: master process /usr/sbin/nginx -g daemon on; master_process on;" ├─1704 "nginx: worker process" ├─1705 "nginx: worker process" ├─1706 "nginx: worker process" └─1707 "nginx: worker process" -
Mhm, looks ok. I have no idea right now. Hopefully somebody else has an idea.
-
-
No other takers?
-
I just had to reboot, so I got all these mails again...
Maybe gurus like KM0201, ryecoaaron or votdev (moderators I randomly saw being around) know more? Apologies for the spam.
-
-
This still happens, by the way...
Just disable the "Proccess Monitoring" and get rid of it for good.
These are probably triggered by delays on the boot proccess and emails are being generated before everything is running.
I came from a Pi4 system (then CM4) and the excess monitoring only gives a "false sense that things are failing" (IMHO)
Now on a x64 system, I just keep it the same way:
-
ErikDB
Hat das Label gelöst hinzugefügt.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
