Page 1 of 1
Service state OK, state history not updated
Posted: Wed Feb 13, 2019 10:41 am
by Bitflogger
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
Re: Service state OK, state history not updated
Posted: Wed Feb 13, 2019 11:12 am
by scottwilkerson
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.
Re: Service state OK, state history not updated
Posted: Wed Feb 13, 2019 11:31 am
by Bitflogger
Hello, I see my mistake in the display.
A "soft" recovery noted, but it did not become "hard" and create a notification.
Earl
Re: Service state OK, state history not updated
Posted: Wed Feb 13, 2019 12:01 pm
by scottwilkerson
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.
Re: Service state OK, state history not updated
Posted: Wed Feb 13, 2019 1:22 pm
by Bitflogger
OK, please lock the call.
Earl
Re: Service state OK, state history not updated
Posted: Wed Feb 13, 2019 1:27 pm
by scottwilkerson
Bitflogger wrote:OK, please lock the call.
Earl
Locking