Page 1 of 1
SOFT service up behavior between 4.3.4 to 4.4.1
Posted: Sat Jul 14, 2018 10:29 pm
by void64
Upgraded from 4.3.4 to 4.4.1 and started noticing we've not been getting service recovery notifications.
After researching we are seeing service recovery's enter a "SOFT" state. This has never happened before in 4.3.4. It seems to be something related with the coming feature in 5.x (enable_soft_service_recovery) ??? Did something slip not quite complete? Because now it's broken in 4.4.1 and all recovering services are now SOFT, therefore notifications are busted.
Or am I missing something?
Re: SOFT service up behavior between 4.3.4 to 4.4.1
Posted: Mon Jul 16, 2018 4:14 pm
by cdienger
We're aware of this issue and looking into it. Feel free to ping us again in a few days if we don't update you before then.
Re: SOFT service up behavior between 4.3.4 to 4.4.1
Posted: Sun Sep 09, 2018 2:56 pm
by void64
Sort of fixed in 4.4.2 but not quite.
Now we are seeing services/hosts enter a SOFT state (warning) first time, immediately followed by a HARD up. (recovery). This causes us to see RECOVERY notifications but we never see any notification from the soft state. (which is by design).
For example:
[09-09-2018 10:58:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;OK;HARD;1;SNMP OK - 5050 VAC
Service Warning
[09-09-2018 10:57:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;WARNING;SOFT;1;SNMP WARNING - *5057* VAC
Service Ok
[09-09-2018 10:53:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;OK;HARD;1;SNMP OK - 5047 VAC
Service Warning
[09-09-2018 10:52:06] SERVICE ALERT: asco-pq.alb2;NORMAL_VCA;WARNING;SOFT;1;SNMP WARNING - *5052* VAC
We get a warning which is a SOFT state, no notification. Ok...
When service recovers from SOFT state, we're getting a HARD recovery; w/ notification. (not ok)
Re: SOFT service up behavior between 4.3.4 to 4.4.1
Posted: Mon Sep 10, 2018 1:32 pm
by lmiltchev
This is a known issue - see this:
https://github.com/NagiosEnterprises/na ... issues/575
Our developers will be looking into this as soon as they can.