servicedependencies not working
Daniel Wittenberg
daniel.wittenberg.r0ko at statefarm.com
Tue Dec 27 23:28:52 CET 2011
Adding in the hostgroups seems to get things working as I would expect. I guess this is another case where "active checks" does not include those performed by freshness checking. Even though I have execution_failure_criteria set to not run on warning and critical, it seems freshness checks are still performed. The good thing is this doesn't generate any alerts it just "clutters" up the interface so if you are looking to see what's wrong in the web gui you see lots of warnings associated with it when really the agent is just down and we were already notified of that. So it would be nice if you could have a setting that would tell it that freshness checks should be treated the same way as active checks.
Dan
-----Original Message-----
From: Andreas Ericsson [mailto:ae at op5.se]
Sent: Friday, December 23, 2011 7:09 AM
To: Nagios Users List
Cc: Daniel Wittenberg
Subject: Re: [Nagios-users] servicedependencies not working
On 12/16/2011 04:38 AM, Daniel Wittenberg wrote:
> I've started playing with making a bunch of dependencies and at first it appeared to be working, right now I've got a pretty basic test setup. I've added one service to be dependent on the other one, but it seems that the freshness might be mucking with it. Two services below:
>
>
> define service {
> service_description base_log_checks
> servicegroups base_service_group
> hostgroup_name base_windows_2003
> use generic-passive-service
> check_freshness 1
> freshness_threshold 3600
> check_command service_is_
> }
>
> define service {
> service_description nagios_cron
> servicegroups base_service_group
> hostgroup_name base_windows_2003
> use generic-passive-service
> check_freshness 1
> freshness_threshold 3000
> check_command service_is_stale
> }
>
> define servicedependency {
> service_description nagios_cron
> dependent_service_description base_log_checks
> execution_failure_criteria w,u,c
> notification_failure_criteria w,u,c
> inherits_parent 1
> }
>
> What appears to happen is that I kill nsclient so nagios_cron starts reporting "stale" at 3000 seconds, and the same for base_log_checks shortly after. Then about every hour I get more "stale" soft alerts, and then after the third try it goes to a HARD alert and I still get a ticket, though I'm not sure why it's even checking if execution should be disable when nagios_cron is in a warning state. But not only does the active checks (service_is_stale) get executed but I'm also still getting notifications sent after 3 attempts, so it doesn't really appear to be doing anything. Unfortunately right now these servers are so busy it's hard to put them in debug mode. Have I missed something obvious with these?
I must say though, with the size of your environment, it's quite possible that
just looking up the dependency takes longer than it does to just execute the
extra check. If you're looking to save time, that might well bite you in the
ass. It's something that will probably be improved til Nagios 4, but it will
require a change in Nagios' object structure, so we can't really do it without
upping the major version number :-/
--
Andreas Ericsson andreas.ericsson at op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list