Opened 5 years ago
Closed 4 years ago
#242 closed defect (fixed)
CheckVersion has old version number
| Reported by: | af@… | Owned by: | mickem |
|---|---|---|---|
| Priority: | 1 | Milestone: | 0.3.6 |
| Component: | None | Version: | 0.3.5 |
| Severity: | Bugs | Keywords: | checkVersion |
| Cc: |
Description (last modified by mickem)
Hi,
My CheckVersion? returns: OK:0.3.5.1 2008-09-24
But my Clientverion is: 0.3.5.2 2008-09-24
A good idea was append "w32" or "w64" etc.
c:\> nsclient++ -test e \Socket.h(668) Socket did not start properly, we will now do nothing... l \NSClient++.cpp(476) NSCLient++ - 0.3.5.2 2008-09-24 Started! e \Socket.h(645) bind failed: 10048: Normalerweise darf jede Socketadresse okoll, Netzwerkadresse oder Anschluss) nur jeweils einmal verwendet werden l \NSClient++.cpp(278) Using settings from: INI-file e \Socket.h(668) Socket did not start properly, we will now do nothing... l \NSClient++.cpp(279) Enter command to inject or exit to terminate... checkversion d \NSClient++.cpp(910) Injecting: checkversion: d \NSClient++.cpp(946) Injected Result: OK '0.3.5.1 2008-09-24' d \NSClient++.cpp(947) Injected Performance Result: '' OK:0.3.5.1 2008-09-24
Change History (5)
comment:1 Changed 5 years ago by mickem
- Description modified (diff)
- Milestone set to 0.3.6
- Owner set to mickem
- Status changed from new to assigned
comment:2 Changed 5 years ago by mickem
comment:3 Changed 4 years ago by mickem
- Resolution set to fixed
- Status changed from assigned to closed
Fixed in the next nightly...
MickeM
comment:4 Changed 4 years ago by schamarthy@…
- Resolution fixed deleted
- Status changed from closed to reopened
I'm stuck up, I'm trying to setup on Nsclient on windows server 2008 but I'm getting the same error
C:\Program Files\NSClient++>nsclient++ /test
Launching test mode - client mode
Service seems to be started, this is probably not a good idea...
l \NSClient++.cpp(370) Attempting to start NSCLient++ - 0.3.5.2 2008-09-24
d \NSClient++.cpp(773) Loading plugin: CheckDisk...
d \NSClient++.cpp(773) Loading plugin: Event log Checker....
d \NSClient++.cpp(773) Loading plugin: Helper function...
d \NSClient++.cpp(773) Loading plugin: CheckSystem...
d \NSClient++.cpp(773) Loading plugin: File logger...
d \PDHCollector.cpp(66) Autodetected w2k or later, using w2k PDH counters.
l \FileLogger.cpp(93) Log path is: C:\Program Files\NSClient++
nsclient.log
d \PDHCollector.cpp(103) Using index to retrive counternames
d \NSClient++.cpp(773) Loading plugin: NRPE client...
d \NRPEClient.cpp(49) humm...
d \NSClient++.cpp(773) Loading plugin: NRPE server...
d \PDHCollector.cpp(123) Found countername: CPU: \Processor(_total)\% Process
or Time
d \PDHCollector.cpp(124) Found countername: UPTIME: \System\System Up Time
d \PDHCollector.cpp(125) Found countername: MCL: \Memory\Commit Limit
d \PDHCollector.cpp(126) Found countername: MCB: \Memory\Committed Bytes
d \NSClient++.cpp(773) Loading plugin: NSClient server...
e \Socket.h(645) bind failed: 10048: Only one usage of each socket address (prot
ocol/network address/port) is normally permitted.
l \NSClient++.cpp(476) NSCLient++ - 0.3.5.2 2008-09-24 Started!
e \Socket.h(645) bind failed: 10048: Only one usage of each socket address (prot
ocol/network address/port) is normally permitted.
e \Socket.h(668) Socket did not start properly, we will now do nothing...
l \NSClient++.cpp(278) Using settings from: INI-file
e \Socket.h(668) Socket did not start properly, we will now do nothing...
l \NSClient++.cpp(279) Enter command to inject or exit to terminate...
Which stable release can I use??
comment:5 Changed 4 years ago by mickem
- Resolution set to fixed
- Status changed from reopened to closed
This issue will be fixed in the 0.3.6 relasae, which I am working on... I am trying to track down a memory leak... something which unfortunately takes a bit of time...
The problems above is that the port is in use and thus you can not use it "twice", look for another program who has the port open (possibly NSClient++ running as a service)
MickeM









humm...
interesting... the version is from the "module" IIRC and this sounds dangerous in so far that my compile seems to have failed...
I shall investigate...