Intermittent service notification problem
-
davide.bonicelli
- Posts: 134
- Joined: Thu Feb 13, 2014 5:12 am
Intermittent service notification problem
Hi, i see a notification problem on a NagiosXI 5.5.9
I noticed that some services come from Unknown state (or critical) to Ok without the mail notifications..
All the settings seems to be ok and if a test a service now i could see the critical and the ok notifications
The strange part is that on the nagios core side of the server i could see the service come to ok in the service alert history (but not in the service notifications)
Please take a look at the pics
What could i check?
Thanks
I noticed that some services come from Unknown state (or critical) to Ok without the mail notifications..
All the settings seems to be ok and if a test a service now i could see the critical and the ok notifications
The strange part is that on the nagios core side of the server i could see the service come to ok in the service alert history (but not in the service notifications)
Please take a look at the pics
What could i check?
Thanks
You do not have the required permissions to view the files attached to this post.
-
davide.bonicelli
- Posts: 134
- Joined: Thu Feb 13, 2014 5:12 am
Re: Intermittent service notification problem
another pic
You do not have the required permissions to view the files attached to this post.
Re: Intermittent service notification problem
You may be hitting a bug that was recently fixed, what version of Core are you running?
Code: Select all
/usr/local/nagios/bin/nagios -VRe: Intermittent service notification problem
Additionally, Please PM me a copy of your profile, you can download it from Admin > System Profile > Download Profile.
-
davide.bonicelli
- Posts: 134
- Joined: Thu Feb 13, 2014 5:12 am
Re: Intermittent service notification problem
Thanks, here's the version.
PM on your way..
PM on your way..
You do not have the required permissions to view the files attached to this post.
Re: Intermittent service notification problem
Ok, so after looking at this and talking with the developers and other support techs about this, it should now be working as intended (it was recently fixed), let me explain:
When the service goes into a soft problem state and then returns to an OK state it was never in a hard state so no notification would have been sent. So it technically should be a soft OK state.
Please see here at the bottom for a good explanation:
https://assets.nagios.com/downloads/nag ... types.html
When the service goes into a soft problem state and then returns to an OK state it was never in a hard state so no notification would have been sent. So it technically should be a soft OK state.
Please see here at the bottom for a good explanation:
https://assets.nagios.com/downloads/nag ... types.html
-
davide.bonicelli
- Posts: 134
- Joined: Thu Feb 13, 2014 5:12 am
Re: Intermittent service notification problem
hm, i don't think this is right.
If you look at the pic 2.jpg
at 11.09.41 there was an unknown hard state, notification sent at 11.09.41 as you could see in pic 4.jpg
but at 11.19.37 the services goes Ok, but without notification
If you look at the pic 2.jpg
at 11.09.41 there was an unknown hard state, notification sent at 11.09.41 as you could see in pic 4.jpg
but at 11.19.37 the services goes Ok, but without notification
Re: Intermittent service notification problem
Did you upgrade to 5.5.9 on the 28th though or what day did you do it? What version did you come from, do you remember? Once you upgraded if the service hadn't recovered to reset the counter (this was the bug that was fixed) it would still have the issue until it recovered. Then it would work properly thereafter so your manual testing would have worked like it did.
-
davide.bonicelli
- Posts: 134
- Joined: Thu Feb 13, 2014 5:12 am
Re: Intermittent service notification problem
uh uh..i don't remember when i updated nagios..but it's possible that i did it when i found that problem
i think i upgraded from 5.5.8
i think i upgraded from 5.5.8
Re: Intermittent service notification problem
Can you replicate the issue or see it in the logs anywhere past the 28th?