Freshness check never fired due to non-incrementing attempts

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
dopey
Posts: 7
Joined: Wed Jan 27, 2016 6:56 pm

Re: Freshness check never fired due to non-incrementing atte

Post by dopey »

I will try setting to 5 mins over the weekend. Heres hoping for some servers going down ;)
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Freshness check never fired due to non-incrementing atte

Post by rkennedy »

How'd it go over the weekend? Did the issue go away?
Former Nagios Employee
dopey
Posts: 7
Joined: Wed Jan 27, 2016 6:56 pm

Re: Freshness check never fired due to non-incrementing atte

Post by dopey »

No, unfortunately. I bumped the freshness threshold to 300 and the attempts still get stuck at 1/X in HARD state.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Freshness check never fired due to non-incrementing atte

Post by tgriep »

Edit that service and change the following from

Code: Select all

failure_prediction_enabled     1
obsess_over_service            1
to

Code: Select all

failure_prediction_enabled     0
obsess_over_service            0
Save it out and see if that fixes it.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked