We are running Nagios 5.6.1 on 64bit Red Hat 7.6 VM's. We have the setting host_down_disable_service_checks=1 in our nagios.cfg file.
We had an issue where a Host Check failed at 9:03:56PM, and a service check started 16 seconds earlier. That service check timed out and send an alert and page out due to it being marked as a Hard Down.
Is there a way to catch issues like this to prevent unneccessary notifications? Situations where the host is marked down in the middle of a service check running, causing the service check to be marked as a Hard Down and alert?
Service marked down even though Host in a down status
Service marked down even though Host in a down status
You do not have the required permissions to view the files attached to this post.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Service marked down even though Host in a down status
There is no way to stop a service from notifying if the check started BEFORE the host went down. Once the check has started it must complete the whole process
Re: Service marked down even though Host in a down status
Thanks.
I thought so, but wanted to check. Feel free to close the topic.
I thought so, but wanted to check. Feel free to close the topic.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Service marked down even though Host in a down status
Lockinghbouma wrote:Thanks.
I thought so, but wanted to check. Feel free to close the topic.