On 09/29/2011 09:49 AM, Mohit Chawla wrote:
> Hello,
>
> Has anyone faced the issue of pre-flight check not completing because
> of too many service dependencies ? The check stalls at 'Checking for
> circular host& service dependencies'.
> I have a simple setup, but the number of dependencies is around 90k.
> Basically these are transport service groups like ssh, nrpe etc. on
> which a lot of checks depend.
>
> define servicedependency {
> servicegroup_name "transport-ssh"
> dependent_servicegroup_name "group1, group2...groupN"
> }
>
> Similar for nrpe. The rest depend on ping.
>
> Any suggestions ?
>
Some ideas come to mind immediately.
A) Implement the algorithm for dependencies that Jean Gabès hacked up for
parent/child detection.
B) Implement service parents. It's one of the (not that many) TODO items
for Nagios 4. That way you'd get the above check logic for free.
C) Rework how dependencies are organized in Nagios core memory and how
they link to other objects. That patch would have to go in Nagios 4 as
well, but I wouldn't be opposed to it.
D) Remove the service dependencies which are for ping. Especially if you
use ICMP (ping) for checking if the host is up, since you're otherwise
using redundant dependency logic.
--
Andreas Ericsson [email protected]
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.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Nagios-users mailing list
[email protected]
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
