Windows Service names with spaces fail to parse correctly

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Windows Service names with spaces fail to parse correctl

Post by lmiltchev »

Sorry for the delay. I tried the change that was recommended.
What exactly did you try? Did you try the following?

Code: Select all

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...
Be sure to check out our Knowledgebase for helpful articles and solutions!
intelXIadmin
Posts: 65
Joined: Mon Mar 25, 2013 9:10 am

Re: Windows Service names with spaces fail to parse correctl

Post by intelXIadmin »

This is solved. No matter what we tried, it doesn't seem to work with spaces. I had the Service renamed.
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Windows Service names with spaces fail to parse correctl

Post by slansing »

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