Nagios Support Forum

You are right scottwilkerson . That is the absolute case that Im struggling with at the moment. If these messages can report the host IP then at least we can have an idea of in which site this host might be located in. Since there's no any other way to find out this host info I hope we can close thi...

Thanks scottwilkerson I tried it as well. There I get only the public IPs of the incoming nrdp requests as my hosts are located overseas and reporting to the Nagios server hosted in a could. (Not a LAN environment) I reckon it would be a nice to have feature to include the host details inside NRDP m...

Thanks @scottwilkerson.

But there's no any matching records for "submitcheck" string in access.log

Background: I have setup quite a few NRDS client machines. They all work well and everything was fine. Recently someone has cloned one of those machines including its NRDP configs. I dont have any information regarding who has cloned the machine, whats its Domain name or IP, where it is running. Now...

Hi Everyone,

I found the answer under the sections "Submitting Passive Service Check Results" and "Submitting Passive Host Check Results" in.

https://assets.nagios.com/downloads/nag ... hecks.html

We can close the thread now.
Thank you..!

if I execute a check from the command-line before its Next Scheduled Active Check Time with it updates the check status in Nagios system before its scheduled check time ? If you submit the check via the external commands file via a command like SCHEDULE_HOST_CHECK or SCHEDULE_SVC_CHECK , yes it wil...

Thanks @mcapra

This is what I was exactly looking for.

We are good to close the thread @npolovenko. Thanks..!

Hi Everyone, In case if I want to run a check before its (scheduled) Next Scheduled Active Check Time, I can execute the command in the command-line with required parameters. Thats all good. Now my question is, if I execute a check from the command-line before its Next Scheduled Active Check Time wi...

Hi @kyang,

Thanks, We are good to close the thread.

Hi @kyang,

Thanks, We are good to close the thread.