Opened 3 years ago

Closed 3 years ago

#355 closed defect (fixed)

checkServiceState -a CheckAll returns ShellHWDetection and sppsvc as stopped while actually running

Reported by: chek01 Owned by: mickem
Priority: 1 Milestone: 0.3.8
Component: check_nrpe Version:
Severity: Bugs Keywords:
Cc:

Description

When asking nscp to check all service states on Windows 2008 R2 via nrpe we get back that ShellHWDetection and sppsvc is stopped while actually running.
ShellHWDetection and sppsvc set to Automatic and started

Tested with 0.3.7 and the last nightly 0.3.8

Windows 2008 R2 (build 7600)

Attachments (1)

nsclient.log (18.5 KB) - added by chek01 3 years ago.
nscp debug log

Download all attachments as: .zip

Change History (8)

comment:1 Changed 3 years ago by chek01

Latest-latest nightly now returns;

2010-01-28 16:52:54: message:modules\FileLogger\FileLogger.cpp:92: Starting to log for: NSClient++ - 0.3.8.12 2010-01-26
2010-01-28 16:53:58: debug:CACHENSClient++.cpp:533: Attempting to start NSCLient++ - 0.3.8.12 2010-01-26
2010-01-28 16:53:58: message:CACHEmodules\FileLogger\FileLogger.cpp:93: Log path is: C:\Program Files\NSClient++
nsclient.log
2010-01-28 16:53:58: error:modules\NRPEListener\NRPEListener.cpp:325: NRPESocketException: To much data cant create return packet (truncate datat)

When running that check.

comment:2 Changed 3 years ago by mickem

Humm.. sounds odd.. I will have to investigate it...

Michael Medin

comment:3 Changed 3 years ago by chek01

Anything we can help with? Debugs etc...

Kind regards,
Christian Ekstam

comment:4 Changed 3 years ago by mickem

Might wanna attach debug log IIRC it should nowdays actually log errors properly...

Michael medin

Changed 3 years ago by chek01

nscp debug log

comment:5 Changed 3 years ago by mickem

Could this be the culprit:
2010-02-01 10:04:14: error:modules\NRPEListener\NRPEListener.cpp:325: NRPESocketException: To much data cant create return packet (truncate data)

Seems the performance data is to long since you have to many services in the list.
Presumably you can simulate this by adding a bunch of excludes to the check to reduce the performance data output.

Maybe I need to add a truncate option...

(0.4.x will solve this for real hopefully)

Michael Medin

comment:6 Changed 3 years ago by chek01

Aahhh, okey, we will test with a couple of excludes to see if it goes away.

Thanks,
Christian

comment:7 Changed 3 years ago by mickem

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

There is a truncate for CheckServiceState (so should work with that option)

Note: See TracTickets for help on using tickets.