NSClient++ Help (#1) - Client crashes unregulary (#432) - Message List
I'm having some issues with my client which crashes unregulary - or at least stops working for some minutes.
Previously I had "NSClient++ - 0.3.6 06/14/09 19:24:24) so I tried using the nightly build "NSClient++ Nightly Build (3.7. - 07/19/09 15:32:54" - nothing changed.
I sometimes can't even restart the service properly. With debugging activated I receive the following error:
2009-08-04 16:54:47: debug:modules\NSClientListener\NSClientListener.cpp:146: Data: XXXXXXXXXX&2&1440
2009-08-04 16:54:47: debug:modules\NSClientListener\NSClientListener.cpp:171: Data: 1440
2009-08-04 16:54:47: debug:NSClient++.cpp:1034: Injecting: checkCPU: 1440, nsclient
2009-08-04 16:54:47: debug:NSClient++.cpp:1070: Injected Result: OK '0'
2009-08-04 16:54:47: debug:NSClient++.cpp:1071: Injected Performance Result:
2009-08-04 16:58:44: debug:NSClient++.cpp:753: No shared session: ignoring change event!
2009-08-04 16:58:46: debug:NSClient++.cpp:753: No shared session: ignoring change event!
And EventLog? Tells me:
Application popup: Microsoft Visual C++ Runtime Library : Assertion failed!
Program: C:\Program Files\NSClient++\NSClient++.exe File: .\util\locale.cpp Line: 190
For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts
(Press Retry to debug the application - JIT must be enabled)
For more information, see Help and Support Center at
enable debug logging and see what that tells you.
MickeMmickem08/04/09 18:36:14 (4 years ago)
That's what debug log tells me - 2009-08-04 16:58:44: debug:NSClient++.cpp:753: No shared session: ignoring change event!
After that event the client doesn't work anymore.zkaerf08/05/09 09:52:16 (4 years ago)
This message is most likely not related.
That message just pops up since you log in so "some part of nsclient was alive at that time".
What checks do you run? And can you disable checks and run just "one at a time" to see which causes the problem?
One option would be (I guess) to try running a debug build as you will then get a nice stack trace at the assert but it depends a bit on what kind of machine it is and hw intermitent the problems is.
Michael Medinmickem08/08/09 07:59:22 (4 years ago)