<div>
I have not used it in a while, but I think on the secondary server you can set the period during which the active check is being performed. &nbsp;i.e. secondary server checks stop checking the host after a certain Time.<br />
<br />
rereading your question do you want the <br />
server A master <br />
<br />
server B secondary<br />
host A<br />
<br />
are you trying to achieve the result that if host A is down for X hours, its status will auto change to OK? <br />

</div>


<div>
It is a set of service checks that I would want to set to OK status after 24 hours.
</div>


<div>
Could you provide a complete description of what you have and what you want to achieve?<br />
Are you looking for server B to only check server A for 24 hours and then assume that it is OK?<br />
<br />
host a went down. host a recovered at 8 am, you now want server B to check host a only until 8 am the following morning?<br />
<br />
What happens during the 24 hours, does the host A being reflected as Ok or Not?
</div>


<div>
Could you provide a complete description of what you have and what you want to achieve?<br />
I have a load balancer that sends snmp traps to nagios when a server drops from a pool (critical alert) and when a server joins the pool (OK)<br />
My problem is these pools have a maintenance server that is a hot stand by, so when is gets removed from the pool, the check never recovers.<br />
I need to manually update the check to OK status. &nbsp;I want to have the check go to OK status after a few hours, probably 24 hours<br />
<br />
Are you looking for server B to only check server A for 24 hours and then assume that it is OK? No<br />
<br />
host a went down. host a recovered at 8 am, you now want server B to check host a only until 8 am the following morning? No<br />
<br />
What happens during the 24 hours, does the host A being reflected as Ok or Not? &nbsp;It is in a Critical state until I manually update it. &nbsp;They are service checks on a host.
</div>


<div>
Can you use dependencies?<br />
<br />
You have a nagios server that is sent traps by a loadbalancer.<br />
&nbsp;<br />
Does the maintenance server get added and then the actual server is removed/worked on. once the original is restored the maintenance is removed, but nagios is reflecting the absence of the maintenance server from the pool?<br />
<br />

</div>


<div>
I can use whatever will get this to work.<br />
<br />
Yes, it basically goes like this<br />
<br />
poolA: Critical &nbsp;(serverA dropped from pool)<br />
poolA: OK (maintenance server added to pool)<br />
poolA: OK (serverA added to pool)<br />
poolA: Critical (maintenance server dropped from pool)<br />
<br />
Alert stays that way until I submit a passive check though nagios.
</div>


<div>
Use dependency such that as long as serverA is in the pool maintenance server status is not important.<br />
<a href="http://nagios.sourceforge.net/docs/3_0/dependencies.html" rel="ugc">http://nagios.sourceforge.net/docs/3_0/dependencies.html</a><br />
<br />
I'm not sure what information your configuration supposed to notify you of.<br />
I can understand the event notifying you of an issue with serverA.<br />
Who knocks maintenance server from the pool?<br />
Does the loadbalancer kicks it out of the pool?
</div>


<div>
The Load Balancer kicks it out of the pool, because it is a hot stand-by that gets triggered with the servers drop from the pool and gets dropped when a server returns to the pool.
</div>


<div>
I think you can define a rule for the maintenance server that the status of the Maintenance server is of importance only when server A is out of the pool. If server A is in the pool, the status of the maintenance will be assumed as up/etc.
</div>


<div>
<div class="content wysiwyg-content">
Nagios V 3.3.1<br />
<br />
Is there a way to set a passive check's status to OK after the duration hits X hours?
</div>
</div>


Nagios V 3.3.1

Is there a way to set a passive check's status to OK after the duration hits X hours?

Nagios: Set status to OK after x Hours (passive check)

Linux is a UNIX-like open source operating system with hundreds of distinct distributions, including: Fedora, openSUSE, Ubuntu, Debian, Slackware, Gentoo, CentOS, and Arch Linux. Linux is generally associated with web and database servers, but has become popular in many niche industries and applications.