With that being said, are you certain that FIREWA01/MCLINK/TELECOM aren't in a down or unknown state when your host is supposed to send out its notification?https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/dependencies.html wrote: Before Nagios executes a service check or sends notifications out for a service, it will check to see if the service has any dependencies. If it doesn't have any dependencies, the check is executed or the notification is sent out as it normally would be. If the service does have one or more dependencies, Nagios will check each dependency entry as follows:
1 Nagios gets the current status* of the service that is being depended upon.
2 Nagios compares the current status of the service that is being depended upon against either the execution or notification failure options in the dependency definition (whichever one is relevant at the time).
3 If the current status of the service that is being depended upon matches one of the failure options, the dependency is said to have failed and Nagios will break out of the dependency check loop.
4 If the current state of the service that is being depended upon does not match any of the failure options for the dependency entry, the dependency is said to have passed and Nagios will go on and check the next dependency entry.
No notification on host down
Re: No notification on host down
Re: No notification on host down
Sorry for delay.
FIREWA01 isn't down, as well as the other two hosts.
Are there any progresses in the analysis of the files?
Thank you,
Giuseppe
FIREWA01 isn't down, as well as the other two hosts.
Are there any progresses in the analysis of the files?
Thank you,
Giuseppe
Re: No notification on host down
I haven't been able to figure out anything conclusive based on digging through those files - though I may have missed something small. Is there any chance you have a support contract with us? If so, we could set up a remote session to get this nailed out.
If not, I'm interested in knowing whether or not you've experienced this behavior since we last spoke. Have you had any luck/additional info on your side? From the looks of it, your dependencies are set up appropriately.
You might try removing the host from all dependencies and verifying that it works fine. After that, try adding dependencies one at a time - does it function as expected?
If not, I'm interested in knowing whether or not you've experienced this behavior since we last spoke. Have you had any luck/additional info on your side? From the looks of it, your dependencies are set up appropriately.
You might try removing the host from all dependencies and verifying that it works fine. After that, try adding dependencies one at a time - does it function as expected?
Re: No notification on host down
I'll propose to evaluate the support contract to our purchase manager.
Since we last spoke I haven't experienced the issue, because the host didn't go down.
Next step, I'll redesignate dependencies.
This time I'll create one dependency definition per father host and omit the "inherit_parent" statement for "root" hosts.
Any other suggestions?
Thank you for the support!
Giuseppe
Since we last spoke I haven't experienced the issue, because the host didn't go down.
Next step, I'll redesignate dependencies.
This time I'll create one dependency definition per father host and omit the "inherit_parent" statement for "root" hosts.
Any other suggestions?
Thank you for the support!
Giuseppe
Re: No notification on host down
It could be the Inherit_parents causing the notifications to stop.
Try that out and let us know if it works.
Try that out and let us know if it works.
Be sure to check out our Knowledgebase for helpful articles and solutions!