Hello, I'm running v5.5.8, 64-bit, VM, CentOS7.
I'm trying to understand how the current state of a service can be OK, when the last registered (recent) state in the state history is critical.
The original question to me was why a recover notification was not sent.
Earl
Service state OK, state history not updated
-
Bitflogger
- Posts: 226
- Joined: Mon Oct 16, 2017 9:24 am
Service state OK, state history not updated
You do not have the required permissions to view the files attached to this post.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Service state OK, state history not updated
Your top image is only showing hard state changes, however I will note that there was a bug in version lower than 5.5.9 that could cause this behavior.
I would strongly recommend upgrading to the latest version.
I would strongly recommend upgrading to the latest version.
-
Bitflogger
- Posts: 226
- Joined: Mon Oct 16, 2017 9:24 am
Re: Service state OK, state history not updated
Hello, I see my mistake in the display.
A "soft" recovery noted, but it did not become "hard" and create a notification.
Earl
A "soft" recovery noted, but it did not become "hard" and create a notification.
Earl
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Service state OK, state history not updated
As mentioned
scottwilkerson wrote:there was a bug in version lower than 5.5.9 that could cause this behavior.
I would strongly recommend upgrading to the latest version.
-
Bitflogger
- Posts: 226
- Joined: Mon Oct 16, 2017 9:24 am
Re: Service state OK, state history not updated
OK, please lock the call.
Earl
Earl
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Service state OK, state history not updated
LockingBitflogger wrote:OK, please lock the call.
Earl