Opened 4 years ago

Closed 15 months ago

#331 closed defect (fixed)

NSClient SERVICESTATE check can't handle service names with commas

Reported by: mmelin Owned by: mickem
Priority: 3 Milestone: 0.4.0
Component: check_nt Version: 0.3.7
Severity: Bugs Keywords:
Cc:

Description

Steps to reproduce:

  1. Create Windows service with comma in the name:

C:\> sc.exe create "Hello, World" binPath= "C:\WINDOWS\notepad.exe"
[SC] CreateService? SUCCESS

  1. Set up NSClient++ 0.3.7.344 2009-09-20 with both NRPE and NSClient listeners
  1. Observe:

# ./check_nt -H nnn.nnn.nnn.nnn -v SERVICESTATE -l "Hello, World"

Hello: Not found - World: Not found

# ./check_nt -H nnn.nnn.nnn.nnn -v SERVICESTATE -l ""Hello, World""

Hello: Not found

# ./check_nt -H nnn.nnn.nnn.nnn -v SERVICESTATE -l "Hello\, World"

Hello\: Error - World: Not found

# ./check_nrpe -H nnn.nnn.nnn.nnn -c CheckServiceState -a ShowAll "Hello, World"
CRITICAL: Hello, World: stopped (critical)

Change History (4)

comment:1 Changed 4 years ago by mickem

  • Owner changed from MickeM to mickem

Ohhh... I was just about to discard this as "check_nt is crap", but if the problem exists for NRPE it is a problem.

Is shall investigate this...

MickeM

comment:2 Changed 15 months ago by mickem

  • Milestone set to 0.4.0

comment:3 Changed 15 months ago by mickem

  • Component changed from NSClientListener to check_nt

comment:4 Changed 15 months ago by mickem

  • Resolution set to fixed
  • Status changed from new to closed

This works via NRPE on 0.4.0 thus I will close this...

Note: See TracTickets for help on using tickets.