Host check issue

[sandeepatil]

Host definition from template.cfg.

We are using passive check

max_check_attempts 1
check_interval 1
retry_interval 1
active_checks_enabled 0
passive_checks_enabled 1

In critical, shwoing soft state, want to hard state to sent notification.

Host status update taking 10 min to get status details.

Please help to fix this issue.

[scottwilkerson]

In the nagios.cfg
change this

Code: Select all

passive_host_checks_are_soft=1

to this

Code: Select all

passive_host_checks_are_soft=0

and restart nagios

[sandeepatil]

passive_host_checks_are_soft=0

already updated in nagios.cfg

[scottwilkerson]

What version of Nagios Core are you running?

These should be HARD by default, but there were a few bugs in early 4.4.x that could cause this behavior.

[sandeepatil]

We are using

Nagios core version : 4.3.4

[scottwilkerson]

Can you show an example of one of these?

[sandeepatil]

Please find attached screen shot

[scottwilkerson]

Can you show the whole configuration for this host (obfuscating any sensitive info)?

[sandeepatil]

Question :

What is importance of freshness_threshold in host passive check, if this is zero or not defined, ok with host definition, any impact on server resource utilization.

We have nagios core server version 4.3.4 with 1000 host and 80k services monitoring

[scottwilkerson]

freshness_threshold

This directive is used to specify the freshness threshold (in seconds) for this host. If you set this directive to a value of 0, Nagios will determine a freshness threshold to use automatically.

When the freshness_threshold is reached, an active check is performed if check_freshness is enabled
https://assets.nagios.com/downloads/nag ... tions.html