NSClient++ Help (#1) - Problem monitoring 32bits process on 64bit nsclient (#979) - Message List
Hi everyone we have been using nsclient++ 32bits for a while, but latly we updated to Windows server 2008R2 so we installed NSclient++ x64
Every thing is fine exept 2 bugs
We are looking at 2 specific processes.
1 is a 3rd party app process that i will call myprocess.exe *32 and the other is explorer.exe
When we installed the 64bits nsclient myprocess.exe *32bits keep saying critical, we keep trying to change the info in nagios exemple myprocess.exe myprocess.exe *32 or 'myprocess.exe *32' none work
So we tried to reinstalled the 32bits + the 64bits on the same server.
Now my process *32 works but explorer.exe went down and keep saying critical. I have no idea what to do
Thanks and sorry for my english
The way it is sopped to work is:
- 32bit NSClient can ONLY see 32bit process regardless of OS.
- 64bit NSClient can see 32bit and 64bit process on x64 os.
x64 nsclient on x64 os looking for w32 chrome and x64 conhost.exe process:
CheckProcState ShowAll chrome.exe=started conhost.exe=started ... d rvice\NSClient++.cpp:947 Result checkprocstate: OK l ce\simple_client.hpp:80 OK:OK: chrome.exe: running, conhost.exe: running l ce\simple_client.hpp:82 Performance data: 'chrome.exe'=31;0;1 'conhost.exe'=9;0;1
Please validate that you are running with a user which has privileged to see the processes. A good way to start this is tun run nscp test as administrator and executing the commands there...
Michael Medinmickem05/19/12 08:41:26 (12 months ago)
Is it the same with perf counters? I'm trying to monitor the queue depth of a whole bunch of queues in an IBM Websphere MQ instance. Unfortunately IBM publish the perf counters in a 32-bit DLL and there for I need to use a 32bit version of NSCP on a 64bit server. It could work ok if it wasn't for a huge memory leakage in the 32bit version.
I'm using: Windows 2008R2 64 bit. NSClient++-0.4.0.172-win32
MartinMigoo06/12/12 07:39:54 (12 months ago)
Is there a memory leak in the 32 bit version? Please tell me so I can fix it :)
And from what I know counters are counters ie. no 32/64 bitness to them but I can investigate a bit.
Michael Medinmickem06/12/12 09:53:59 (12 months ago)
I'm having the same issue as ratatapa..
using the 64bit version of NSClient only on Windows 2008 R2 64bit.
I can monitor 64 bit processes just fine but my 32 bit procs are always showing as not running:
running test as admin gives:
CheckProcState ShowAll GatewayAdmin?.exe=started
d rvice\NSClient++.cpp:923 Injecting: checkprocstate...
d stem\CheckSystem.cpp:902 PROC>>> enumerate_processes
d stem\CheckSystem.cpp:902 PROC>>> enable_token_privilege
d stem\CheckSystem.cpp:905 PROC<<<enable_token_privilege
d stem\CheckSystem.cpp:902 PROC>>> FEnumProcesses
d stem\CheckSystem.cpp:905 PROC<<<FEnumProcesses
d stem\CheckSystem.cpp:899 PROC::: Failed to open process: 4:
d stem\CheckSystem.cpp:902 PROC>>> find_crashed_pids
d stem\CheckSystem.cpp:905 PROC<<<find_crashed_pids
d stem\CheckSystem.cpp:905 PROC<<<enumerate_processes
d rvice\NSClient++.cpp:948 Result checkprocstate: CRITICAL
l ce\simple_client.hpp:80 CRITICAL:CRITICAL: GatewayAdmin?.exe: stopped < criti cal
l ce\simple_client.hpp:82 Performance data: 'GatewayAdmin?.exe'=0;0;1
PID 4 is system
I can see that the process IS running. in Process Monitor, this shows as GatewayAdmin? *32 - don't know if the *32 makes a difference ? (putting it into the command makes no difference).
I have tried running the process as Admin, NSC++ as admin..
(ignore the ? in the app exe name, the board is trying to create a wiki link for some reason!!)
thanksphilyardley10/23/12 14:07:45 (7 months ago)