Hosts check serialization

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
ngut
Posts: 2
Joined: Tue Jul 24, 2012 10:16 am

Hosts check serialization

Post by ngut »

Hi,

I'm wondering if it's possible to serialize all "host checks" in a 3.0 version. It seems it's possible to do that with "services checks" with option "max_concurrent_checks" set to 1. It also seems that the version 1.x and 2.x did "host checks" in serial mode.

To describe my situation: I would like to test multiple (high latency / low throughput) radio links with Nagios. PC is connected to an unique radio gateway and I defined in nagios configuration multiple remote hosts that I need to test (through my gateway). I use "check-icmp" plugin with high values and I don't have any problem when it is executed alone.

My problem is that Nagios parallelize all host checks and flood my radio gateway with multiple parallel requests. I can select higher "check_interval" for each host and modify the "host_inter_check_delay_method" to improve the operation, but there isn't any synchronization between host tests so tests always finished by collide.

Do you have any solution to serialize host check? or any other equivalent trick to solve my problem?
Thanks for your help
User avatar
nscott
Posts: 1040
Joined: Wed May 11, 2011 8:54 am

Re: Hosts check serialization

Post by nscott »

To do what you're describing I do believe that the max_concurrent_checks is truly what you want. It will ultimately limit how many can be done at any given time, which seems ideal for your situation as I believe that applies globally to all checks--service and host checks.
Nicholas Scott
Former Nagios employee
ngut
Posts: 2
Joined: Tue Jul 24, 2012 10:16 am

Re: Hosts check serialization

Post by ngut »

Hi Nscott,

Thank you for your answer. Unfortunately this setting concern only services (as described in nagios.conf file bellow). I tested and I still have parallel requests executed for host tests.

# MAXIMUM CONCURRENT SERVICE CHECKS
# This option allows you to specify the maximum number of
# service checks that can be run in parallel at any given time.
# Specifying a value of 1 for this variable essentially prevents
# any service checks from being parallelized. A value of 0
# will not restrict the number of concurrent checks that are
# being executed.

max_concurrent_checks=1
Locked