Nagios Support Forum

We figured it out - looks like only plugins with 3 letter extensions get pulled down. My coworker copied one of the .exe files in the Windows plugin folder (on the XI server), and renamed it. After configuring a new NRDS test with the new executable, it successfully pulled the file down. We then tri...

I'm going to upgrade XI to the current version and then re-try this scenario.

Thanks

The plugin directory on the Windows box does not include perl_script.pl in it, but the Config.ini file does have the new test, now modified with command[PERL_SCRIPT] = perl.exe $PLUGIN_DIR$\perl_script.pl It's kind of weird I don't see anything in the debug log about detecting a new plugin or attemp...

Here's my NRDS Config.ini file on the remote host - I verified that the version is the same as in Nagios XI: [settings] CONFIG_VERSION=2.4 CONFIG_OS=Windows (64-bit) CONFIG_NAME=TDOC URL=http://10.10.240.165/nrdp/ TOKEN=4c2rbj36cnb2 HOSTNAME= PLUGIN_DIR=C:\Program Files\Nagios\NRDS_Win\plugins SEND_...

Did a little more testing - I simplified my perl script to be extremely simple (i.e a print statement followed by an exit(0)) - and also granted all permissions on it. Tried placing it in both the Generic and Windows plugin folders as well. Same result as before.

Here's the output of the ls -l command: (It's currently in
"/usr/local/nrdp/plugins/Generic" at the moment, but I can move it back to the Windows one if needed)

I'm currently testing the passive monitoring capabilities of NRDS for a Healthcare IT company with systems deployed on-site all across the country (100's of hosts and services). Since most all of these hosts are not on our network, the passive "phone-home" capability of NRDS has really got...