Nagios Support Forum

Box293 wrote:

PhilG wrote:check_xi_service_nsclient!<pass>!SERVICESTATE!-l GxEvMgrC(Instance001) -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l GxCVD(Instance001) -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l MSSQLFDLauncher$UWCX01 -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l MSSQL$UWCX01 -d SHOWALL

The brackets and $ signs need to be escaped with a backslash '\'.

Code: Select all

check_xi_service_nsclient!<pass>!SERVICESTATE!-l GxEvMgrC\(Instance001\) -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l GxCVD\(Instance001\) -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l MSSQLFDLauncher\$UWCX01 -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l MSSQL\$UWCX01 -d SHOWALL

How about Services that have spaces in them, ex. "BMC FootPrints Asset Core Agent". I would have to add a backslash in front of each space then or are spaces acceptable and don't require the escape character?

Usually, wrapping the service name in double quotes is sufficient, for example:
BTW, did you check to see if there is a "friendlier" name that you can use in your check (i.e. "Service name" vs "Display name")? I mean, is there an option where there are no spaces/special characters in the name?

Right-click on the service under "Services" on the Windows box, then click on "Properties".

lmiltchev wrote:Usually, wrapping the service name in double quotes is sufficient, for example:

Code: Select all

./check_nt -H 192.168.x.x -s password -p 12489 -v SERVICESTATE -l "Group Policy Client" -d SHOWALL
 Group Policy Client: Started

BTW, did you check to see if there is a "friendlier" name that you can use in your check (i.e. "Service name" vs "Display name")? I mean, is there an option where there are no spaces/special characters in the name?

Right-click on the service under "Services" on the Windows box, then click on "Properties".

Yes, that's the first thing I did was identify the actual Service Name. The vendor chose to be "non-standard" for some reason, ex.
Service name: GxEvMgrC(Instance001)
Display name: CommVault Client Event Manager (Instance001)
Path to executable: "C:\Program Files\CommVault\Simpana\Base\evmgrc.exe" -vm Instance001

I can probably find the Process name "evmgrc.exe" and use that instead of doing a Service Name check.

BTW, "gpsvc" is the Service name of the Display name "Group Policy Client".

I see. Try:
Let us know how it went.

lmiltchev wrote:I see. Try:

Code: Select all

 ./check_nt -H <client ip> -s <password> -p 12489 -v PROCSTATE -l evmgrc.exe -d SHOWALL

Let us know how it went.

I didn't have time to get to this today and I will be out of the office until Mon. 12/1/2014. I will say that the backslash did work for one of the Services that had the "$" character.

Sounds good! Post back on Monday to give us an update.

Update:
1). Windows Service Names that contain spaces are being monitored successfully at this time. I enclosed the service name with the double quotations (as was suggested), ex.
"Stupid Long Windows Service Name From Vendor That Uses Spaces"

2). Windows Service Names that contain a special character, ex. a "$", are being successfully monitored at this time. I have preceded the special character with the escape character "\", as was suggested, ex. (without the double quotations):
"StupedWindowsServiceName\$WithSpecialCharacter"

Thank you for your assistance! You may freeze this post.

We'll go ahead and close this thread for you. Thanks.