Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#222 closed defect (fixed)

NSClient++ v0.3.3.20 memory failures

Reported by: minddigger Owned by: mickem
Priority: 1 Milestone: 0.3.4
Component: Core Version: 0.3.3
Severity: Bugs Keywords:
Cc:

Description

Using NSClient++ v 0.3.3.20 W32 as of date 2008-07-02, used on a WIN-2003-SBS standard server I reglarly get error messages about Instruction on 0x......... pointed to memory on 0x......... Read or write on memory failed. The memory could not be read. I don't know where that comes from.

I also use NSClient++ on another WIN-2003-SBS, but with version 0.3.0.1 as of date 2007-11-28 wich does not cause such problems.
I was intend to upgrade that version to the latest, but now I am afraid that it also will cause the same memory fault.

Attachments (2)

nsclient-config.rar (4.0 KB) - added by minddigger 5 years ago.
NSClient-config file
nsclient.zip (49.7 KB) - added by minddigger 5 years ago.
NSClient logfile

Download all attachments as: .zip

Change History (24)

comment:1 Changed 5 years ago by mickem

  • Owner changed from MickeM to mickem
  • Status changed from new to assigned

Could you try it with the latest nightly?

Michael Medin

comment:2 Changed 5 years ago by mickem

  • Resolution set to fixed
  • Status changed from assigned to closed

should have been fixed in the 0.3.4 version (try the RC and report back)

comment:3 Changed 5 years ago by rob.jongejan@…

Having installed your latest version now, hope it wil work and dos not show any error anymore.
Thanks in advance for your adequate support.

comment:4 Changed 5 years ago by minddigger

Well, as far as I can see now there is a new error from systray.exe.
It says instruction on 0x761a4885 points to memory on 0x00530650. A read/write action on the memory has failed. The memory could not be read.
This has not happend before the install of the version NSClient++-WIN32-0.3.4-RC-3

Hope you can use this information. Else tell me what to do.
Regards
Rob Jongejan

comment:5 Changed 5 years ago by mickem

  • Resolution fixed deleted
  • Status changed from closed to reopened

humm, this is strange.

Could you paste the config you use (feel free to remove passwords and such).
TAlso the systray is not a "critical" component so you could tryu to disable it.
But I hardly see the system tray causing a crash, so it is strange.

Michael Medin

comment:6 Changed 5 years ago by anonymous

Hello Michael,
Sorry about the late answer. I'm not as often at my office as I wish.
Error pattern:
The error occurs always when I login at the server-console
The erorr seems not to show-up with a RDP session (normal usage of this server)
The error does not show-up when I disable the NSClient service

When I try to copy/paste the config file in this textbox the submission is rejected with an error saying that tis contains spam.... So I try to attach it with the button above.

Changed 5 years ago by minddigger

NSClient-config file

comment:7 Changed 5 years ago by minddigger

Weard..... The upload of files seems not to be possible with textfiles..
The ticket-system classifies it always as possible spam and rejects it...
Now I have uploaded it as a RAR file instead.

comment:8 Changed 5 years ago by mickem

  • Resolution set to fixed
  • Status changed from reopened to closed

ARGH!!, this was a bit of a SNAFU on my side, will be fixed in next RC (4?) in a while (am compiling now).

Let me know if this fixes this issue.

MickeM

comment:9 Changed 5 years ago by mickem

RC-4 out now (should fix this issue I hope)

comment:10 Changed 5 years ago by minddigger

  • Resolution fixed deleted
  • Status changed from closed to reopened

Hello Michael, Sorry, but the error still occurs with the systray.exe, and as far as I can see only on the system-console and not in the RDP sessions. I will ask the users if they have seen errors. With the version before (0.3.1) they did, but I don't know if they see the error now with the latest versions...

comment:11 Changed 5 years ago by mickem

the "systray.exe" has never been there before so it would surprise me if you had seen it before :)
And the latest version does not have a systray.exe (it is now called nstray.exe) so I'm guessing the upgrade failed or possibly my build failed.

Are you sure you have upgraded to the latest RC (RC-4)?
And did you use the installer or the zip-download?
And are you on w32 or x64?

MickeM

comment:12 Changed 5 years ago by anonymous

Hmmm.
I am on w32
The latest version wich I have downloaded is NSClient++-Win32-0.3.4-RC-4.msi

I use the installer and had some difficulties when the service went down.

After clicking on the repair button I have seen that the Agent still is version 0.3.4.24-RC instead of 0.3.4-RC-4
Maybe I should uninstall and reinstall?

comment:13 Changed 5 years ago by mickem

  • Resolution set to fixed
  • Status changed from reopened to closed

The "RC" number in the versions tring is not bumped, the RC is a tag for the status of the build. The version is an internal number:

C:\nsc>"NSClient++.exe" /version
l \NSClient++.cpp(244) NSClient++ Version: 0.3.4.28 RC 2008-09-14, Plattform: w32

Is the one you want so I am thinking you have the "old" version still.
Simplest way for you to get "it right" is to:

  1. stop the service:
    net stop nsclientpp
    
  2. unzip the .zip file to the distribution (probably don't want to replace the nsc.ini file)
  3. delete the systray.exe file (should have a nstray.exe instead).
  4. start the service
    net start nsclientpp
    

Another option is to:

  1. uninstall
  2. reboot
  3. delete all files
  4. install new version

All in all the installer is "beta" in the 0.3.x branch so it "works" but not very well, best way is to manually copy the files if you ask me :)
Especially when you play with RC:S that might break :)

Hope this has not caused too much problems and hopefully the new RC will sort things out for you.

comment:14 Changed 5 years ago by minddigger

  • Resolution fixed deleted
  • Status changed from closed to reopened

Hi Michael
Sorry but.......

Having downloaded the zip file instead of the msi file and done the instructions as mentioned in the fisrt four points.
As a result I got the same error but now from NSTRAY.EXE instead.
I think I will do the other option this evening, because I have to reboot the server and I can't do this when users are working on it.

comment:15 Changed 5 years ago by mickem

wait wait you get the same error?
humm, this is indeed interesting, could you paste the debug log?
And make sure you don't have shared_session=1 in your config.

I shall investigate further tonight then :(

MickeM

Changed 5 years ago by minddigger

NSClient logfile

comment:16 Changed 5 years ago by minddigger

Michael,
I've uploaded the nsclient logfile to the ticket.
Shared_session is not an available item in the config file I use with NSClient, or do you perhaps mean another config parameter??

comment:17 Changed 5 years ago by mickem

  • Resolution set to fixed
  • Status changed from reopened to closed

hello, a bit of a trial thingy again, I missed an issue in the last version so hopefully this time (RC5) I have managed to get it right :)

and BTW: "niet" (russian) but the rest looked "comprehensible" (german/swedish), where are you from?

This time, replace stuff from the .zip (-minus the config file) simplest I think...
Installer I think needs to be "updated" to work properly something I only do for realses since it is a pain...

MickeM

comment:18 Changed 5 years ago by anonymous

Hello Michael, I'm Dutch and live in a pretty little city called Enkhuizen.
The last version seems to be good. No more errors (until now ;-))

Last question :
In the logfile an error of the PDHCollector.cpp appears : Failed to query performance counters:\Processor(_total)\Percentage processortijd: PdhGetFormattedCounterValue? failed: - 2147481642: een item met een negatieve waarde voor de deler gevonden.

Translation :
Failed to query performance counters:\Processor(_total)\Percentage processortime: PdhGetFormattedCounterValue? failed: - 2147481642: an item found with a negative value for the divisor.

I think this has nothing to do with the error, but can you give me an explain about this error message?

comment:19 Changed 5 years ago by mickem

unfortunately not... this is an error that "sometimes appears" I have yet to understand why and what is affected.

DO you get it "consistently" or just intermittently?
And if so would you be able to run a test "client" to help me diagnose the error a bit?

Michael Medin

comment:20 Changed 5 years ago by minddigger

It also appears in the logfile i've attached as nsclient.zip
As you can see at the start of the logfile it does not happens on a regularly base, but nearly every day a couple of times and after 2008-09-11

How can I run a testclient ?

comment:21 Changed 5 years ago by mickem

Well, I would tailor a build for you (after 0.3.4) with some additional debug info and then you would install that on a (preferably) non-critical server and send me back the logfile...

Michael Medin

comment:22 Changed 5 years ago by anonymous

No problem, as long as it doesn't hang the server.
Let's try... ;-)

Note: See TracTickets for help on using tickets.