Page 2 of 2
Re: Hard State Reached prior to 3/3 check
Posted: Thu Jun 04, 2015 1:47 pm
by JakeHatMacys
jdalrymple wrote:Are there any other services that depend on these? I noticed this in your nagios.cfg:
Code: Select all
enable_predictive_host_dependency_checks=1
enable_predictive_service_dependency_checks=1
So if anything depends on a host or service and it's noticed that it's down an on-demand check will be spawned. My guess is that it is on-demand checks that are causing this behavior if I'm understanding the problem fully.
No services but other hosts that depend on that host being up. So if I turn that off will that potentially give me the behavior I desire? (Shutting off checks on the dependent servers for 1 hour once the parent is down).
And is there a way to change this in the GUI or do I need to edit the file manually?
Re: Hard State Reached prior to 3/3 check
Posted: Thu Jun 04, 2015 1:58 pm
by jdalrymple
You can "edit the nagios.cfg file manually" in the gui.
Configure --> Core Configuration Manager --> Advanced --> Nagios Core Main Config
You might try to disable those 2 options just to see if it gives you the expected results before disabling a bunch of depending services/hosts.
After you change that file make sure to restart Nagios Monitoring Engine.
Re: Hard State Reached prior to 3/3 check
Posted: Fri Jun 05, 2015 7:16 am
by JakeHatMacys
I'll give that a shot, another question I have on the 1/1 checks I set up... They're being labeled by XI as soft 1/1, shouldn't those be Hard?
Edit According to this thread this is a known Bug:
http://support.nagios.com/forum/viewtop ... 2&p=126275
I'm running version 2.5 on this box. I'll check the release notes of 2.7 again to see if this was fixed. Don't recall it being mentioned before.
Re: Hard State Reached prior to 3/3 check
Posted: Fri Jun 05, 2015 10:34 am
by lmiltchev
I'll give that a shot, another question I have on the 1/1 checks I set up... They're being labeled by XI as soft 1/1, shouldn't those be Hard?
Can you show us how this host is defined? Also, show us the State History report for this host (State Types = Both; Host/Service = Hosts).
Consider the following scenario - in your host definition, you have:
Code: Select all
max_check_attempts 1
check_interval 1
retry_interval 1
When the host is detected to be in a non-OK state, during the regular check interval (every minute), the host will switch to a soft down state.
THIS IS THE FIRST CHECK (run on the regular "check_interval" schedule)
After this, the "retry_interval" will kick in (which is also 1 min). After the number of "max_check_attempts" (which is also one minute), the host will switch to a hard down state.
THIS IS THE SECOND CHECK (run on the "retry_interval" schedule)
This is the default (expected) behavior.
Host - retry interval
This directive is used to define the number of "time units" to wait before scheduling a re-check of the hosts. Hosts are rescheduled at the retry interval when they have changed to a non-UP state. Once the host has been retried max_check_attempts times without a change in its status, it will revert to being scheduled at its "normal" rate as defined by the check_interval value. Unless you've changed the interval_length directive from the default value of 60, this number will mean minutes. More information on this value can be found in the check scheduling documentation.
Are you seeing something else?
Re: Hard State Reached prior to 3/3 check
Posted: Mon Jul 20, 2015 1:34 pm
by joshuasmith
Were you able to fix the 'HARD - attempt 1 of 3' error? I've been experiencing the same problem, and turning off predictive host checks hasn't had any effect.
Re: Hard State Reached prior to 3/3 check
Posted: Mon Jul 20, 2015 4:41 pm
by lmiltchev
Any updates, JakeHatMacys? Did your issue get resolved?