Nagios Support Forum

Posted: **Wed May 15, 2013 2:05 pm**

Sorry for the delay. I tried the change that was recommended.

What exactly did you try? Did you try the following?

Try changing the following line in the NSC.ini (or nsclient.ini) from this:

runcmd=scripts\runcmd.bat $ARG1

to this:

runcmd=scripts\runcmd.bat "$ARG1$"

Restart the nsclinet++ service and run a check from the nagios server:

./check_nrpe -H 192.168.5.180 -p 5666 -c runcmd -a 'Klocwork 9.2 Server'

Did this fail? Any feedback on this?

It seems like that we are shifting the focus from restarting a windows service to troubleshooting custom powershell scripts...

Posted: **Wed May 22, 2013 1:12 pm**

This is solved. No matter what we tried, it doesn't seem to work with spaces. I had the Service renamed.

Posted: **Wed May 22, 2013 1:32 pm**

That is very strange, it is working as expected in other environments. Thanks for letting us know what the resolution was.

Nagios Support Forum

Windows Service names with spaces fail to parse correctly

Re: Windows Service names with spaces fail to parse correctl

Re: Windows Service names with spaces fail to parse correctl

Re: Windows Service names with spaces fail to parse correctl