Page 1 of 1

Nagios generating HARD critical trap at first attempt itself

Posted: Thu May 27, 2021 5:42 am
by deek
Hi

We are facing some issue with the HARD and OK traps with critical plugin timeout.

When a service is having critcal - plugin timeout issue , we are seeing HARD critical trap at first attempt though we have 5 attempts to check before sending an HARD trap and post that once the service comes up and OK traps is in SOFT state and not HARD state. So the event is open and not closed by HARD ok trap. Attached the snapshot for reference. Where to do the changes from the backend to make it send HARD critical at 5th attempt and OK HARD alert instead of OK SOFT.

HARD_trap.JPG
Thanks
Deek

Re: Nagios generating HARD critical trap at first attempt it

Posted: Thu May 27, 2021 5:34 pm
by ssax
What XI version are you using? This looks like a bug. Was the host down? If so, you are likely hitting this:

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

Re: Nagios generating HARD critical trap at first attempt it

Posted: Fri May 28, 2021 3:50 am
by deek
We are using Nagios 5.67. Yes the host was down.

And in the document that you have mentioned, there was a question if this is fixed in version 5.8.1
We do see this plainly as a bug and atleast we are looking for any solution that we can do it from the backend like making changes to the confugration files.

Thanks
Deek.

Re: Nagios generating HARD critical trap at first attempt it

Posted: Fri May 28, 2021 5:20 pm
by ssax
I am currently unable to provide a solution, I talked with development on this recently and they said that they consider that a high priority bug for the next XI release that contains a Core update in it (not every XI release gets a Core release in it) but the bug hasn't been fixed yet as it's still listed as open.

Re: Nagios generating HARD critical trap at first attempt it

Posted: Sat May 29, 2021 1:18 am
by deek
Thanks for the update sax. Much appreciated.

Re: Nagios generating HARD critical trap at first attempt it

Posted: Tue Jun 01, 2021 2:02 pm
by ssax
No problem, I know multiple customers are waiting on the resolution but the recent NDO3 issues have taken priority.