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.
Using Nagios core 4.3.2 with cfg files from Nagios 4.1.1, the host on demand check is not getting executed when a service underneath the host has failed check. I created a new file from scratch with the same parameters, still the host check will not execute. I'm hoping that I misses some setting from 4.1.1 to 4.3.2 that will make it work correctly. The service returns an unknown status and in 4.1.1 it checks the host.
I tested the on demand checks and was seeing the proper behavior with 4.3.2. Can you provide the actual config files(host and service definitions, nagios.cfg, and command.cfg)? as well as clear description on how you're testing this?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
I'd really like to see the config for the host and service. If you're unable to post them here, can you PM them to me? Better yet, create a profile under Admin > System > System Profile and send that along with the name of the host and service.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Ok, there must be something I'm missing. I complied Nagios 4.3.2 on Fedora 26 server and still have the issue. I have even removed my 4.1.1 configs and create new ones from scratch and the host on demand check isn't executing when the service check alarms. Here is the host config:
I am positive that the host check isn't executing. Using tcpdump, I only see the snmp tries and no icmp traffic to the host. the host check is check-host-alive. Changing it back seemed to work to more what we are use to. I'd like to understand how this the change operates so I can perhaps make a config change to produce the desired result.