I have a distributed Nagios configuration in which I use NSCA for a central nagios instance to accept passive service/host checks from the remote one.
The reason I have to use NSCA and passive checks is due to the fact that my Nagios' instances are in different domains. This way, unlness there was an open port for each monitored host (which is highly unsafe) I couldn't monitor the remote subnet with my central instance.
Problem is that host_checks on the central instance are only fresh after I restart all the operating modules, afterwords they get stale.
Still, those checks keep fresh on the remote instance (the one who is performing active checks).
Furthermore, there was an issue reported by mag (and resolved by egalstad) much like this one which is troubling me (0000152: some host checks get skipped if service checks are disabled). I did not understand the solution whis was conveyed in pseudocode and suposely is in the CVS (WHERE???). That issue is under this link: http://tracker.nagios.org/view.php?id=152
----------------------------------------
With my best regargs,
sebastiaopburnay
passive host checks get stale - solved/closed
- sebastiaopburnay
- Posts: 105
- Joined: Sun Oct 31, 2010 1:40 pm
- Location: Lisbon, Portugal
passive host checks get stale - solved/closed
Last edited by sebastiaopburnay on Wed Mar 06, 2013 2:33 pm, edited 1 time in total.
- sebastiaopburnay
- Posts: 105
- Joined: Sun Oct 31, 2010 1:40 pm
- Location: Lisbon, Portugal
Re: passive host checks get stale
Hi!
In another forum, I was informed this is a version issue:
It is going in a pacific fashion with no problems up to this point.
Just updating all the path related variables, macros, config files and binarys.
I'm yet to verify if it fixes the stale host checks issue, though I'm confident it will.
Maybe in a month I will be using Icinga.
Thank you for your support. I will spread the word for this fix in the community.
In another forum, I was informed this is a version issue:
So, I'm currently migrating our nagios' servers from 3.2.1 to 3.2.3.ah issue 152 .. the one where ethan created the best bug ever in 3.2.2 ... it's fixed in 3.2.3 so getting the latest version would help resolve that. in icinga, i've put that fix into 1.2.0 iirc.
-----------------------------------------------------------------------------------------------------
Icinga 1.3 MySQL,PGSQL,Oracle and IPv6
Icinga Web http://goo.gl/3DDT
Icinga Classic http://goo.gl/3Lkp
Icinga Docs: http://docs.icinga.org
Report bugs/Feature requests http://goo.gl/eWqi
* egrep -v "^#|^$" configfile
* check https://dev.icinga.org
Join us online!
irc.freenode.net #icinga #icinga-devel
It is going in a pacific fashion with no problems up to this point.
Just updating all the path related variables, macros, config files and binarys.
I'm yet to verify if it fixes the stale host checks issue, though I'm confident it will.
Maybe in a month I will be using Icinga.
Thank you for your support. I will spread the word for this fix in the community.