What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Local Probe Periodically Disconnected

Votes:

0

Last night, my server start to become unstable in collecting data. When I see in the Logs > System Events > Probe Related, there are so many message contains "Probe "Local probe" at 127.0.0.1:xxxxx has disconnected" and then after few minutes, the probe is connected again. Below is sample of the logs message.

2/2/2017 14:03 None Probe Local probe Connected Probe "Local probe" at 127.0.0.1:50426 has connected 2/2/2017 13:55 None Probe Local probe Disconnected Probe "Local probe" at 127.0.0.1:50378 has disconnected 2/2/2017 13:53 None Probe Local probe Connected Probe "Local probe" at 127.0.0.1:50378 has connected 2/2/2017 13:53 None Probe Local probe Disconnected Probe "Local probe" at 127.0.0.1:50110 has disconnected

The message start to fille the logs since 2/1/2017 9:41:58 PM, and since then my server become unstable in collecting data. And there are another messages in the logs, below is the sample.

2/1/2017 22:14 None System System Data Error reading historic data (Device=16985 Sensor=17035 Date=4/12/2016) Error: Access violation at address 000000000040D49C in module 'PRTG Server.exe'. Read of address FFFFFFFFFFFFFFFF 2/1/2017 22:14 None System System Data Error reading historic data (Device=16985 Sensor=17035 Date=4/11/2016) Error: Access violation at address 000000000040D49C in module 'PRTG Server.exe'. Read of address FFFFFFFFFFFFFFFF 2/1/2017 22:14 None System System Data Error reading historic data (Device=16985 Sensor=17035 Date=4/10/2016) Error: Access violation at address 000000000040D49C in module 'PRTG Server.exe'. Read of address FFFFFFFFFFFFFFFF 2/1/2017 22:14 None System System Data Error reading historic data (Device=16985 Sensor=17035 Date=4/9/2016) Error: Access violation at address 0000000000857D0F in module 'PRTG Server.exe'. Read of address 0000000000000000

Three days ago, the harddisk is full, so I backup the Monitoring Database to another storage. After I backup the data, the server work well. But last night, the problem starts. Is there a correlation between the full harddisk and the problem above? Can you give me solution about this problem? Thank you

data local-probe prtg

Created on Feb 2, 2017 9:17:20 AM



1 Reply

Votes:

0

Dear asrafin_danang

Since solving this issue will include sending more logs, and possibly screenshots, please contact [email protected]. If possible, please contact us via Setup / Contact Support, and include a support bundle. This is a selection of log files which is a good starting point for further analysis.

Created on Feb 2, 2017 12:49:33 PM by  Arne Seifert [Paessler Support]




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.