Nagios Support Forum

Still haven't rolled out the newer version, but yes, that's the plan right now. But if in the mean time you'd like me to try anything else, that would be OK.

Thanks for all the effort =)

-t

No joy I'm afraid. The change to that setting had no effect whatsoever. The expectation with settings below would be that after SOFT DOWN 1, Nagios should retry every 2 min. Instead it retried 8 times within a period of about 3 minutes. Test host: Ash. Test Setings: check_interval 1, retry_interval ...

Giving that a shot. Will post results soon. Thanks!

Sorry for the delay, holidays and all, and took a while to get back to this. But here ya go...

check_host_freshness=0
host_freshness_check_interval=60
host_inter_check_delay_method=s
max_host_check_spread=1

Took a while to get back to this, but no, suggestion of disabling the freshness check didn't work. Also just to say again, this isn't a problem for the services. They work as expected. It's the host checks that do not. Though I know it's only a difference in definition, it still manifests as a devia...

Ash was a test host and is no longer configured as such. But for each host down test, the parameters are included with the results in my original post. However the host template used is below. I am including a configuration that is current for another host, Malheur, and the results of an unexpected ...

Running version 3.4.1, compiled from source. I get load spikes about every 10 minutes to about 2.0, but the average is about 0.9. Also, this isn't happening with services, only with host checks. Any other configuration settings besides the ones related to intervals in the nagios.cfg that could cause...

I'm trying to figure out something which seems pretty straight forward, which is the relationship between recheck_interval and max_check_attempts. I thought I understand what they're supposed to do, but it isn't working out that way. From reading the docs, recheck_interval should be the amount of ti...