Host Rechecks faster than retry setting

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Host Rechecks faster than retry setting

Post by rkennedy »

I'll leave this thread open, and we will wait for your response!
Former Nagios Employee
lytxnoc
Posts: 44
Joined: Tue Aug 18, 2015 11:02 am

Re: Host Rechecks faster than retry setting

Post by lytxnoc »

I removed all of the host and service dependencies and ran into the same issue.
Attached image shows the rechecks averaging between 15-30 seconds. The Hard down is correct, so the only issue seems to be with the retry interval.
You do not have the required permissions to view the files attached to this post.
lytxnoc
Posts: 44
Joined: Tue Aug 18, 2015 11:02 am

Re: Host Rechecks faster than retry setting

Post by lytxnoc »

We experienced the same issue, even after deleting all of the host and service dependencies.
You do not have the required permissions to view the files attached to this post.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Host Rechecks faster than retry setting

Post by tgriep »

Lets check to see if there is a duplicate nagios process causing the issue. Can you run the following as root and post the output?

Code: Select all

ps -ef |grep bin/nagios
Be sure to check out our Knowledgebase for helpful articles and solutions!
lytxnoc
Posts: 44
Joined: Tue Aug 18, 2015 11:02 am

Re: Host Rechecks faster than retry setting

Post by lytxnoc »

Here is a list of processes running on the nagios server.
You do not have the required permissions to view the files attached to this post.
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: Host Rechecks faster than retry setting

Post by tmcdonald »

I'm assuming you only had dependencies and not parents, but can you address the predictive checks setting I asked about on the previous page? The ps output looks fine so it is not duplicates causing this behavior.
Former Nagios employee
Locked