Next check: in the past!

[rdot84]

Checkmk Raw Edition 2.4.0p15

Out of hundreds of services, ~ 40 show this:

Next check: x in the past!

Can anyone explain to me why?

Some of them have ad-hoc interval and period rules
Some of them use the default interval (1m) and period (24x7)

But for all the ones I verified manually, checks are actually executed by checkmk at the correct time.

This is an example from a service that is using default interval\period values:

Looks like checkmk thinks that the next scheduled check (173m in the past) will be around the same time of “Age of the current service state” (174m ago).

This is from the same page, refreshed 7 minutes later:

[andreas-doehler (Andreas)]

This behavior depends on the type of check.
If this check is a passive check then it should look like this.

For an active check it should look like this instead

As in the top of your check is something written with “CPU utilization” i think it is a passive check where someone has triggered an active reschedule of the service.

[rdot84]

@andreas-doehler

As in the top of your check is something written with “CPU utilization” i think it is a passive check where someone has triggered an active reschedule of the service.

Do you mean manually or via a rule?

[rdot84]

And as usual, I really find it difficult to understand the checkmk logic.

E.g.

These are all services on a single dummy host that was created automatically via Setup \ Quick Setup\ [Amazon Web Services (AWS)]

How can they have different next check times?

They are all triggered by the same Check_MK service on the same host, so all of them should have the same next check time, right?