Passive checks for specified hosts are removed- rework to us

[yogesh2014]

Hi Team,

We have added passive checks for many hosts as syaing "Host is not pingable - Using Internal IP" for exalogic checks for that host.
But we observed the passive checks are removed automatically may be when server rebooted or httpd service restarted, not sure.
So again we are performing pasive checks manually for all hosts its a rework for us.
So please let us know is there any way to revert back the passive checks to the hosts what we configured already ? or can we perform bulk hosts passive checks ?

Thanks in advance for your suport

Best Regards,
Yogesh

[slansing]

What do you mean by they are being removed? The services/hosts are actually disappearing? Or the check results are being cleared after restarts?

[yogesh2014]

For the hosts actually the passive checks results - "OK" status with the comment "Host is not pingable - As using Internal IP" what we provided.
May be once server restarted, the hosts checks are become again active and showing "CRITICAL" instaed of checking passively.
So again we need to sumbmit the passive check result as specified above for all internal hosts what we are using.
Hope its cleared !!

[abrist]

There is no way for the Nagios server to force a passive check. This logic must be added to the remote host's passive check script.
You could use freshness to force an active check, but you have provided too little information for me to judge it that is possible in your environment.
How are you performing these passive checks - NRDP, NSCA, NCPA, etc?