NagiosXI Notification Problem

[davide.bonicelli]

yes, forcing by hand the hard state bot the Host and the Service (uptime) are sending the emails correctly

[benjaminsmith]

Hi,

Thanks for testing and this would confirm the notifications are working correctly. I would continue to monitor this service closely to make sure you receive any future notifications. I've attached a file of the state history of this service from the logs you provided to help understand the state changes and any notifications.

[davide.bonicelli]

thanks, but from the log i see that the last notification is this

Code: Select all

nagios-10-01-2020-00.log:[1601479892] SERVICE NOTIFICATION: monitoraggio-pro;NAS-BK-ARIOST2;Uptime;UNKNOWN;xi_service_notification_handler;UNKNOWN - check_nwc_health timed out after 60 seconds

but after that i see some HARD state without notifications like this:

Code: Select all

nagios-10-02-2020-00.log:[1601503200] CURRENT SERVICE STATE: NAS-BK-ARIOST2;Uptime;OK;HARD;1;OK - device is up since 6d 9h 48m 59s

[ssax]

Given that SNMP checks can sometimes take a while for the remote system to respond you may want to add -t 120 to your check_nwc_health command and make sure your /usr/local/nagios/etc/nagios.cfg file has service_check_timeout=120 set, and then apply configuration and see if that helps alleviate it as well.

[davide.bonicelli]

yep, but the problem here is to know if the system is realiable with the alerts or not

[ssax]

I apologize, not sure how I missed that.

After reviewing your logs it looks like you are hitting this open bug:

https://github.com/NagiosEnterprises/na ... issues/759

You can validate it by these entries:

Code: Select all

# Host goes down
[Wed Sep 30 17:26:01 2020] HOST ALERT: NAS-BK-ARIOST2;DOWN;SOFT;1;CRITICAL - Socket timeout

# Since the host is down it goes into a HARD state immediately (the UNKNOWN was the result of that check)
[Wed Sep 30 17:26:31 2020] SERVICE ALERT: NAS-BK-ARIOST2;Uptime;UNKNOWN;HARD;1;UNKNOWN - check_nwc_health timed out after 60 seconds

# The notification for the Uptime service goes out that you see
[Wed Sep 30 17:31:32 2020] SERVICE NOTIFICATION: monitoraggio-pro;NAS-BK-ARIOST2;Uptime;UNKNOWN;xi_service_notification_handler;UNKNOWN - check_nwc_health timed out after 60 seconds

# Service recovers
[Wed Sep 30 17:35:34 2020] SERVICE ALERT: NAS-BK-ARIOST2;Uptime;OK;SOFT;1;OK - device is up since 6d 3h 24m 48s

We see that the service recovers SOFTly (no notification would be sent) but it should have been a HARD recovery where a notification would be sent.

[davide.bonicelli]

ok..so i have to wait a future release for fixing this problem..

[ssax]

Correct, development is aware of the issue and said they are trying to get the fix in the next version released that contains an updated Nagios Core release.

[davide.bonicelli]

i see that 5.7.5 is out but i don't found anything about my problem in the change log..am i wrong?

[ssax]

No, you are correct, it was not included in that release because development did not update the backend Nagios Core in it. Not every version of XI released will have an updated Nagios Core in it for stability reasons. The backend Nagios Core in XI is generally only updated in major/minor releases and not in bugfix versions.

Looking at the bug it's still listed as open:

https://github.com/NagiosEnterprises/na ... issues/759

I confirmed with development in the last couple weeks (and have in the past) that the specific bug we're talking about is a high priority bug for the next XI release that includes a Nagios Core update (likely in 5.8 but the bug needs to be fixed/tested first).

Thank you for your patience!