NRDS_Win Hangs at first Check

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
matt.uebel
Posts: 84
Joined: Thu Jun 20, 2013 7:43 am

NRDS_Win Hangs at first Check

Post by matt.uebel »

I am using the NRDS_Win plugins to passively monitor systems as described here http://exchange.nagios.org/directory/Ad ... in/details

Working for all servers except one. Problem server starts plugin dialog as revealed in NRDS_Debug.log, but then never proceeds past the first plugin, which is check_winping.exe. Nothing ever gets sent to the Nagios server.

However, if I manually run the NRDS_Win.vbs script, it completes successfully and sends the checks to the Nagios server.

Got any ideas yribbens?
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: NRDS_Win Hangs at first Check

Post by slansing »

Is the service running correctly? Can you try restarting it to see if checks come in?

The service's have already been configured and added into Nagios correct? Or are some still in Unconfigured objects?
Problem server starts plugin dialog as revealed in NRDS_Debug.log
Can you send a copy of the log?
matt.uebel
Posts: 84
Joined: Thu Jun 20, 2013 7:43 am

Re: NRDS_Win Hangs at first Check

Post by matt.uebel »

PM'd copy of log.

I have also found a server where the script doesn't run at all from task scheduler, but succeeds if run manually from command line. These are both Windows 2k3 servers.
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: NRDS_Win Hangs at first Check

Post by slansing »

I don't think the attachment got through, could you re-send it?
yancy
Posts: 523
Joined: Thu Oct 06, 2011 10:12 am

Re: NRDS_Win Hangs at first Check

Post by yancy »

Matt,

I apologize for the late response. It sounds like NRDS_win.vbs passes check results back when run manually, otherwise if run by the task scheduler, it does not run. Correct?

There is likely a problem with where the task scheduler is running the file from.

Can you run the following from the command line

Code: Select all

schtasks
Thanks,

-Yancy
Locked