Opened 5 years ago
Closed 5 years ago
#161 closed defect (worksforme)
NSClient++ allocating huge numbers of Windows handles
| Reported by: | it10@… | Owned by: | anonymous |
|---|---|---|---|
| Priority: | 1 | Milestone: | 0.4.0 |
| Component: | Core | Version: | 0.3.1 |
| Severity: | Bugs | Keywords: | |
| Cc: |
Description
I see NSCLient++ 0.31 (Win32) allocating huge amounts of Windows handles.
At about 2.9 million handles used by NSClient++, the server was nearly unusable or crashed.
I used MS perfmon to monitor NSCLient++'s handle usage on two different servers.
The machine with the 0.31 service shows a rapidly increasing handle count, the machine with an old NSClient++ service (06-23-2007) has a constant handle usage of about 400 handles.
I commented out as much as possible from NSC.ini, reducing config to an absolute minimum: no cpu load buffering, no NRPE, only processing of perfmon performance counters
CheckSystem.dll
NSClientListener.dll
[NSClient]
Attachments (1)
Change History (3)
Changed 5 years ago by anonymous
comment:1 Changed 5 years ago by anonymous
- Owner changed from MickeM to anonymous
- Status changed from new to assigned
What check do you run and from where?
ie. check_nt or check_nrpe and what "command" do you check, I am guessing check_nt and the counter check they have?
MickeM
comment:2 Changed 5 years ago by mickem
- Resolution set to worksforme
- Status changed from assigned to closed
will close this, if it still is an issue reopen...
perfmon screenshot