Help! nrpe_nt, service check when name contains $ problem

[Andreas Ericsson]

Evan Touchett wrote:
> I am trying to get nagios and nrpe to check a windows 2003 server
> service.  The problem I am experiencing is that the name of the
> service contains a $ in it.
> 
> The service name in the registry on the windows server is
> "MSSQL$BKUPEXEC"
> 
> In services.cfg on the linux box running nagios 2.0b, I have the
> following for the service check.
> 
> define service{ use                             generic-service
> ; Name of service template to use host_name
> TapeBackup service_description             Service - BE MSSQL 
> is_volatile                     0 check_period
> 24x7 max_check_attempts              3 normal_check_interval
> 5 retry_check_interval            1 contact_groups
> windows-admins notification_interval           120 
> notification_period             24x7 notification_options
> w,u,c,r check_command
> check_nt_service!MSSQL\$BKUPEXEC }
> 
> But I get a warning with the results showing " MSSQL$BKUPEXEC$:
> Unknown  "  as you can see it is adding another $ at then endof the
> service name.  Can anyone suggest a way to pass the name correctly?
> 

Escape the $ with a $, so that you have double dollar-signs in your 
command, like so
MSSQL\$$BKUPEXEC

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null