Backup successful - critical alert (similar to two other cases)

[jestertoo (Jess)]

Two similar cases that don’t seem to have a fix?

CRIT - Backup completed

Today its Thursday June 04, 2020, I got : CRIT - Backup completed, it was running for 32 m from 2020-06-03 12:00:01 till 2020-06-03 12:32:13, Size: 3.2 GB, Next run: 2020-06-04 00:00:00(!!) this should run next time on Wednesday because I set 7 backups one for every day! I configured it in wato [Screenshot 2020-06-04 08:58:43]

Check_Mk backup daily : it has succed in the backup section but the plugins says it has failed

Hello team , I have some repetitive problems (daily) and don’t know why it is happening , I have tried find in the log but no informations , totally blocked My configuration is the following ( CEE version ) : I have one master and 2 slaves in differents network zones , the master are piloting the slaves on configuration push I use the master to monitor the slaves ( I have installed the standard agent on the slaves ) , the slaves are considered a a normal host , seen in the master Problem…

I did have two NTP sources that were about 3000us apart, so I removed one of them. That doesn’t seem to be even close to the 6s that the plugin takes to run.

CMK version:
2.0.0p18.cee

OS version:
Oracle8.4 running RH compatible kernel

Error message:
Host:
Service: OMD DFW backup nightly
Event: OK → CRIT
Address: 10.xx.xx.xx
Date / Time: Fri Mar 11 00:00:00 UTC 2022
OMD Site: DFW
Host Tags: /wato/xxx/hosting/linux/ auto-piggyback cmk-agent ip-v4 ip-v4-only lan no-snmp prod site:XXX tcp
Custom Host Notes URL:
Relative Time: 0d 00:00:00
Summary: Backup completed, it was running for 4.57 s from 2022-03-10 00:00:02 till 2022-03-10 00:00:06, Size: 49.94 MB, Next run: 2022-03-11 00:00:00(!!)
Details: Backup completed\nit was running for 4.57 s from 2022-03-10 00:00:02 till 2022-03-10 00:00:06\nSize: 49.94 MB\nNext run: 2022-03-11 00:00:00(!!)
Acknowledge Author:
Acknowledge Comment:
Host Metrics:
Service Metrics: backup_duration=4.567871;;;; backup_avgspeed=3721448.733458;;;;backup_size=52367360;;;;
Custom Service Notes URL:

[MarkBpunkt]

It is quite clear that the errors occur if the service check happens to start while the backup is running. To avoid the error, you can set the rule “Check period for passive checkmk services” and exclude the period of the backup.

The backup is completed successfully despite the notification, i think.

Mark