Page 1 of 2

Passive test stale

Posted: Sat Jan 27, 2018 9:51 am
by adt7108
I have been having a strange issue with passive test going stale and then ok one min later. We have had NagiosXI in service for over 2 years and this issue has just started happening in the last few months. At first we thought it was a timing issue between the nsclient++ and the nagiosxi server but that was not the case, we raised the freshness threshold from 240sec to 900sec then 1200sec nothing has helped with this issue. The nsclient++ are set to send ever 3 mins. Any ideas as to why we are getting the stale alerts?
Screen Shot 2018-01-27 at 8.38.48 AM.png
Screen Shot 2018-01-27 at 8.37.57 AM.png
Screen Shot 2018-01-27 at 8.40.07 AM.png

Re: Passive test stale

Posted: Mon Jan 29, 2018 2:11 am
by tacolover101
could you post a system profile for us to review?

admin -> system settings -> download profile

i wonder if a template or grouping is affecting this.

Re: Passive test stale

Posted: Mon Jan 29, 2018 9:09 am
by adt7108
Yes should be attached.

Re: Passive test stale

Posted: Mon Jan 29, 2018 12:19 pm
by kyang
Thanks @tacolover101!

@adt7108, Could I ask what passive handler are you using with NSClient++? NRDP? NSCA?

Also, in the third screenshot, you sent us. Do you have any checks defined with that passive check service? Or is it blank? Or is it the check_dummy for freshness checking?

Re: Passive test stale

Posted: Mon Jan 29, 2018 2:44 pm
by adt7108
We are using NSCA with the NSCLient++. The check definition is blank. See attached:

Re: Passive test stale

Posted: Mon Jan 29, 2018 3:31 pm
by kyang
I see that under your template xiwizard_passive_service, that is your check command you are using with all other hosts that for the Memory Usage service check.

Code: Select all

check_dummy!2!"Result of the passive test is stale."
Is this the only service under host ca1-qa-green that is having this issue? How about the other 48 that you have associated with this service check?

Whats the freshness threshold at now? Are you changing this threshold under the template or the service?

Re: Passive test stale

Posted: Mon Jan 29, 2018 3:56 pm
by adt7108
The

Code: Select all

check_dummy!2!"Result of the passive test is stale."
would be default I guess, as we did not put that in there.

No we have several other service checks that are experiencing the same "stale" issue, like CPU, Services, Disk, Uptime etc. I just choose Memory Usage as an example. Also the other 48 host are having the same issue with random "stale" test.

Currently the freshness threshold in the service is 1200 and the template "xiwizard_passive_service" is set to 900.

Re: Passive test stale

Posted: Tue Jan 30, 2018 9:14 am
by adt7108
As a shot in the dark I cleared out the setting in the service level and just let it put the setting from the "xiwizard_passive_service" template and the stale test is working correctly now. I would think something has happen in the past couple releases of nagiosxi 5.4.10 or 5.4.11 and up.
Screen Shot 2018-01-30 at 8.11.00 AM.png

Re: Passive test stale

Posted: Tue Jan 30, 2018 10:10 am
by kyang
Thanks for letting me know! I was just about to ask you to try clearing it as well.

I will keep this as a reference in case I see similar cases. Then I will let everyone know. I haven't come across this on my XI. So if we do run across this, I'll be sure to let the QA team know.

Is this thread ready to be closed or would you like to keep it open just in case?

Re: Passive test stale

Posted: Tue Jan 30, 2018 10:16 am
by adt7108
Thanks @kyang we are good for now you can close this.