Opened 2 years ago
Closed 15 months ago
#427 closed defect (fixed)
Check_nt Process State Returns CheckSystem.cpp Error
| Reported by: | mantious | Owned by: | mickem |
|---|---|---|---|
| Priority: | 5 | Milestone: | 0.3.9 |
| Component: | check_nt | Version: | 0.3.8 |
| Severity: | Bugs | Keywords: | check_net CheckSystem.cpp |
| Cc: |
Description
When I run any of the following check_nt PROCSTATE checks the NSClient++ returns the same error noted below in the log file
Nagios Server: 3.2.3
NSClient++ x64 0.3.8.76 2010-05-27
Server Windows 2008 Std R2 x64
Check_NT Command:
./check_nt -H %HOSTNAME% -p 12489 -s %PASSWORD% -v PROCSTATE -d SHOWALL -l caf.exe caf.exe: not running ./check_nt -H %HOSTNAME% -p 12489 -s %PASSWORD% -v PROCSTATE -d SHOWALL -l explorer.exe Explorer.EXE: Running ./check_nt -H %HOSTNAME% -p 12489 -s %PASSWORD% -v PROCSTATE -l explorer.exe OK: All processes are running.
NSClient.log:
message:modules\CheckSystem\CheckSystem.cpp:813: Failed to open process: 4: error:modules\CheckSystem\CheckSystem.cpp:810: Unhandled exception describing PID: 4: Failed to open process: 4:
Change History (6)
comment:1 Changed 2 years ago by mantious
comment:2 follow-up: ↓ 3 Changed 2 years ago by mickem
This is usually a privelage issue. in other words the user running nsclient++ does not have access to see information about the pid in question (4) this is usually not a "problem" per see....
Do you have any problems related to this (apart from the error)
comment:3 in reply to: ↑ 2 Changed 2 years ago by mantious
I thought so as well so I ran it on the test system with Administrator privilages and still gives the same error in the log file. No other issues from what I am using it for on the Windows 2003 R2 32 bit (CPU, Memory, Services, and Processes). Just the Process check throwing that error on only the 64 bit live and test systems.
comment:4 Changed 2 years ago by mickem
Well, not even admin (ish) can "see" all processes. What I do is try to get information from it PID 4 is usually something called System which it fails for. I guess I should remove the error message in some instances...
Michael Medin
comment:5 Changed 2 years ago by mantious
True though it should of provided something more specific with the up'd permissions, but then again the 2008 R2 64 bit servers have quarky in general though. Figured I'd ask any how. Thanks for the assistance.
Mat
comment:6 Changed 15 months ago by mickem
- Milestone changed from 0.3.8 to 0.3.9
- Resolution set to fixed
- Status changed from new to closed
This was fixed if I recall correctly...









I put your last nightly build (NSClient++-0.3.9-x64-20101226-1452) on a test Windows 2008 R2 64 Bit server. It also has the issue, just figured I would try it and see if it corrected the issue.