New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Problems with ram usage on Windows 7 SP1 Remote Probe

Votes:

1

Your Vote:

Up

Down

Used-Case: Windows 7 SP1 Remote Probe with Dual-Core CPU and 4 GB-Ram and Windows Server 2008 R2 SP1 with Quad-Core CPU and 6 GB-Ram.

Within 5 days we’ve got a RAM-Lost of at least 1 GB, falling strong. Every, i think 10-12 days, we’ve got problems with our monitoring on the remote probe. It stucks and produce wrong errors which we don’t need ;).

The Probe with the problem got a lot of linux ssh sensors. Maybe this is useful.

nsi ram windows-7

Created on Nov 17, 2014 11:52:15 AM by  Sascha Lewandowski (2,291) 3 4



1 Reply

Accepted Answer

Votes:

3

Your Vote:

Up

Down

We’ve solved the problem. Following this in a test-case.

  1. Check the processes in process manager
  2. Read the services which one hast he highest rate
  3. Re-check in system used process manager
  4. Restarting one network port
  5. Check if the error ist away

Following this we can say, that the NSI-Service got problems by closing the ports and recycle the ram. Restarting the port clears the cache on the NSI-Service. Furthermore the Paessler client crashed shortly before.

In case oft the NSI-Service, microsoft got some problems on Windows 7 SP1 which you can fix with this to packages.

http://support2.microsoft.com/kb/2847346/en-us

http://support2.microsoft.com/kb/2950358

Microsoft say’s you can use the Fix also to Windows Server 2008 R2 SP1.

Furthermore you can restart your Probe every week automatically with the PRTG Remote Manager. This will help the system to recycle the used ram.

We’ve test it for about 5 weeks and this seems to be the fix for us.

Thanks ;)

Created on Nov 17, 2014 3:36:58 PM by  Sascha Lewandowski (2,291) 3 4

Last change on Nov 17, 2014 4:44:35 PM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.