#444 closed defect (fixed)
CheckTaskSched exception in wrapHandleCommand
| Reported by: | alu-one | Owned by: | mickem |
|---|---|---|---|
| Priority: | 1 | Milestone: | 0.4.0 |
| Component: | CheckTaskSchedule | Version: | 0.3.9 |
| Severity: | Bugs | Keywords: | CheckTaskSched CheckTaskSched2 Windows Server 2008 R2 |
| Cc: |
Description
When executing this command on remote host:
./check_nrpe -H 192.168.1.86 -p 5666 -c CheckTaskSched -a "filter=exit_code ne 0" "syntax=%title%: %exit_code%" warn=>0
No result comes back.
Nsclient.log shows this message:
2011-04-07 08:23:35: critical:modules\CheckTaskSched2\CheckTaskSched2.cpp:173: Unknown exception in: wrapHandleCommand(...) 2011-04-07 08:23:35: message:NSClient++.cpp:1195: No handler for command: 'CheckTaskSched' 2011-04-07 08:23:35: message:include\NSCHelper.cpp:238: No handler for command 'CheckTaskSched'.
This also happens with CheckTaskSched2.dll.
The system where NSClient is installed is a virtual Windows Server 2008 R2 64-bit, running on 2008 R2 Hyper-V.
NsClient? version is 0.3.9.297 (it was not selectable in the Version combobox).
Change History (5)
comment:1 Changed 16 months ago by mickem
- Milestone set to 0.4.1
- Owner changed from MickeM to mickem
- Version changed from 0.4.0-nightly to 0.3.9
comment:2 Changed 16 months ago by mickem
- Component changed from Core to CheckTaskSchedule
comment:3 Changed 14 months ago by light13s
comment:4 Changed 14 months ago by alu-one
- Resolution set to fixed
- Status changed from new to closed
Thank you!
Note: See
TracTickets for help on using
tickets.









The issue is caused by a incorrectly specified warning threshold(Which is specified incorrectly in the wiki" http://www.nsclient.org/nscp/wiki/CheckTaskSched2/CheckTaskSched").
Change the "warn=>0" to "MaxWarn=1" to fix the issue.
The full query would be:
"./check_nrpe -H 192.168.1.86 -p 5666 -c CheckTaskSched -a "filter=exit_code ne 0" "syntax=%title%: %exit_code%" MaxWarn=1"