Hello!
About nagios XI environment
1) Linux Distribution and version? Centos7
2) 32 or 64bit? 64bit
3) VMware Image or Manual Install of XI? Manual install
4) Are there special configurations on your system, ie; is Gnome installed? Are you using a proxy? Are you using SSL? SSL
5) NagiosXI version: 5.5.9
I am experiencing again a weird case where CRITICAL notification was not sent out and only OK was sent. Something similar to a problem i had before: https://support.nagios.com/forum/viewto ... 16&t=50747
Service settings:
OK notification without critical
OK notification without critical
You do not have the required permissions to view the files attached to this post.
Last edited by atsb on Fri Feb 01, 2019 2:10 am, edited 1 time in total.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: OK notification without critical
looking at your first image, it is hard to see for sure but it looks like the host that is sending the notification start with an a and a s and the host that is logging a SERVICE ALERT starts with an o
So these aren't the same host/service combination.
So these aren't the same host/service combination.
Re: OK notification without critical
Thats incorrect, "a" and "s" are actually users(contacts) line structure is like this
SERVICE NOTIFICATION: a(user);o(server);Oracle tnsping(service);OK;xi_service_notification_handler;OK - connection established to o(server:port/DB)
SERVICE NOTIFICATION: a(user);o(server);Oracle tnsping(service);OK;xi_service_notification_handler;OK - connection established to o(server:port/DB)
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: OK notification without critical
Ok got it!
Is it possible that this was the first time this service went into an OK state since upgrading to 5.5.9?
I ask because there was a bug in previous versions that could cause this and they would not reset themselves and thing that a notification had previously been sent when it hadn't.
This actually shouldn't have sent the CRITICAL notification because it was just a soft state, but the errant recovery was part of the bug mentioned above.
Is it possible that this was the first time this service went into an OK state since upgrading to 5.5.9?
I ask because there was a bug in previous versions that could cause this and they would not reset themselves and thing that a notification had previously been sent when it hadn't.
This actually shouldn't have sent the CRITICAL notification because it was just a soft state, but the errant recovery was part of the bug mentioned above.
Re: OK notification without critical
Yes, it indeed went into CRITICAL/OK state first time after upgrade. Thank you and i will let you know if this happens again.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: OK notification without critical
Sounds good.atsb wrote:Yes, it indeed went into CRITICAL/OK state first time after upgrade. Thank you and i will let you know if this happens again.