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

PRTG Network Monitor

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

Free Download

Top Tags


View all Tags

All "Probe Health" sensors alarm at same time?

Votes:

0

Your Vote:

Up

Down

Hey everyone.

Just installed the trial version to see what PRTG is like. So far so good, it does everything we need.

However, we have an issue with some of the remote probes.

Every now and then, maybe a few times every hour, the Probe Health will go to alarm state. It does this for all remote probes at the same time.

Our graphs are ruined as there are outage gaps throughout.

How is it possible that all remote probe healths can Alarm at the same time, when none of the other sensors are even in Warning?

What can we do to fix this?

health probe remote-probe

Created on Aug 21, 2013 10:41:11 AM by  Rich (50) 1 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Thanks very much for your help Konstantin, the issue was indeed caused by conflicting (and very frequent) time updates.

Everything is now working perfectly!

Created on Aug 22, 2013 2:17:41 PM by  Rich (50) 1 1



7 Replies

Votes:

0

Your Vote:

Up

Down

Hi,
the only thing which could explain this behaviour of the remote probes throwing the errors is that the core server is loosing connection to the probes at the same time. Are they by any chance all connected via the same switch? If so, there might be a hardware failure.
Additional, please send or upload the logs of at least one probe loosing connection and the core server as outlined here. Please send an email as well where referring to this article.
Best regards

Created on Aug 21, 2013 7:26:51 PM by  Konstantin Wolff [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi there.

All the remote probes are in different physical locations.

The main PRTG server is on a server at our data center, one probe is at another data center in a different country, another probe is in our office in England, another probe is at another data center - so they are well spread out.

I've send the log files (I didn't have a PAE number?) via the Server Administrator.

Who shall I send the email to?

Created on Aug 22, 2013 10:20:56 AM by  Rich (50) 1 1



Votes:

0

Your Vote:

Up

Down

Incidentally, I just found this in one of the PROBE log files:

22/08/2013 08:10:00 Server TimeSync from 22/08/2013 07:10:00 to 22/08/2013 07:14:19
22/08/2013 08:11:00 Server TimeSync from 22/08/2013 07:15:19 to 22/08/2013 07:11:00
22/08/2013 08:23:00 Server TimeSync from 22/08/2013 07:23:00 to 22/08/2013 07:27:19
22/08/2013 08:24:00 Server TimeSync from 22/08/2013 07:28:19 to 22/08/2013 07:24:00
22/08/2013 08:35:00 Server TimeSync from 22/08/2013 07:35:00 to 22/08/2013 07:39:19
22/08/2013 08:36:00 Server TimeSync from 22/08/2013 07:40:19 to 22/08/2013 07:36:00
22/08/2013 08:47:00 Server TimeSync from 22/08/2013 07:47:00 to 22/08/2013 07:51:19
22/08/2013 08:48:00 Server TimeSync from 22/08/2013 07:52:19 to 22/08/2013 07:48:00
22/08/2013 08:59:00 Server TimeSync from 22/08/2013 07:59:00 to 22/08/2013 08:03:19
22/08/2013 09:00:00 Server TimeSync from 22/08/2013 08:04:19 to 22/08/2013 08:00:00
22/08/2013 09:12:00 Server TimeSync from 22/08/2013 08:12:00 to 22/08/2013 08:16:19
22/08/2013 09:13:00 Server TimeSync from 22/08/2013 08:17:19 to 22/08/2013 08:12:59

And on a different PROBE:

22/08/2013 08:11:45 Server TimeSync from 22/08/2013 07:10:00 to 22/08/2013 07:14:19
22/08/2013 08:12:45 Server TimeSync from 22/08/2013 07:15:19 to 22/08/2013 07:11:00
22/08/2013 08:14:23 Timediff: -104954
22/08/2013 08:19:23 Timediff: -104911
22/08/2013 08:24:23 Timediff: -104914
22/08/2013 08:24:45 Server TimeSync from 22/08/2013 07:23:00 to 22/08/2013 07:27:19
22/08/2013 08:25:45 Server TimeSync from 22/08/2013 07:28:19 to 22/08/2013 07:24:00
22/08/2013 08:29:23 Timediff: -104987
22/08/2013 08:30:06 Time change. System: 22/08/2013 08:30:06 PRTG (UTC): 22/08/2013 07:28:21 PRTG (Local Timezone): 22/08/2013 08:28:21
22/08/2013 08:30:06 Time Monitor:  8:29:57 8:29:58 8:29:59 8:30:0 8:30:1 8:30:2 8:30:3 8:30:4 8:30:5 8:30:6 | 8:30:6
22/08/2013 08:34:23 Timediff: -104950
22/08/2013 08:36:45 Server TimeSync from 22/08/2013 07:35:00 to 22/08/2013 07:39:19

Could this be the issue??

What might the cause be?

Created on Aug 22, 2013 10:26:09 AM by  Rich (50) 1 1

Last change on Aug 6, 2015 4:40:07 AM by  Luciano Lingnau [Paessler]



Votes:

0

Your Vote:

Up

Down

You should have received my answer via email.
Best regards

Created on Aug 22, 2013 10:46:26 AM by  Konstantin Wolff [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Here's another PROBE:

22/08/2013 11:48:49 Time change. System: 22/08/2013 11:48:49 PRTG (UTC): 22/08/2013 10:48:49 PRTG (Local Timezone): 22/08/2013 11:48:49
22/08/2013 11:48:49 Time Monitor:  11:48:39 11:48:40 11:48:41 11:48:42 11:48:43 11:53:4 11:53:5 11:53:6 11:53:7 11:53:8 | 11:48:49
22/08/2013 11:48:51 Possible timeshift detected: 258 seconds. Please check system time synchronisation settings!
22/08/2013 11:54:09 Time change. System: 22/08/2013 11:54:09 PRTG (UTC): 22/08/2013 10:49:49 PRTG (Local Timezone): 22/08/2013 11:49:49
22/08/2013 11:54:09 Time Monitor:  11:49:40 11:49:41 11:49:42 11:49:43 11:49:44 11:49:45 11:49:46 11:49:47 11:49:48 11:49:49 | 11:54:9
22/08/2013 11:54:09 Server TimeSync from 22/08/2013 10:49:49 to 22/08/2013 10:54:09
22/08/2013 11:49:55 Time change. System: 22/08/2013 11:49:55 PRTG (UTC): 22/08/2013 10:54:15 PRTG (Local Timezone): 22/08/2013 11:54:15
22/08/2013 11:49:55 Time Monitor:  11:49:45 11:49:46 11:49:47 11:49:48 11:49:49 11:54:10 11:54:11 11:54:12 11:54:13 11:54:14 | 11:49:55
22/08/2013 11:49:55 Time change. System: 22/08/2013 11:49:55 PRTG (UTC): 22/08/2013 10:54:15 PRTG (Local Timezone): 22/08/2013 11:54:15
22/08/2013 11:49:55 Time Monitor:  11:49:45 11:49:46 11:49:47 11:49:48 11:49:49 11:54:10 11:54:11 11:54:12 11:54:13 11:54:14 | 11:49:55
22/08/2013 11:49:57 Possible timeshift detected: 258 seconds. Please check system time synchronisation settings!
22/08/2013 11:50:49 Server TimeSync from 22/08/2013 10:55:09 to 22/08/2013 10:50:49
22/08/2013 11:55:15 Time change. System: 22/08/2013 11:55:15 PRTG (UTC): 22/08/2013 10:50:55 PRTG (Local Timezone): 22/08/2013 11:50:55
22/08/2013 11:55:15 Time Monitor:  11:50:45 11:50:46 11:50:47 11:50:48 11:50:49 11:50:50 11:50:51 11:50:52 11:50:53 11:50:54 | 11:55:15
22/08/2013 11:51:00 Time change. System: 22/08/2013 11:51:00 PRTG (UTC): 22/08/2013 10:51:00 PRTG (Local Timezone): 22/08/2013 11:51:00
22/08/2013 11:51:00 Time Monitor:  11:50:50 11:50:51 11:50:52 11:50:53 11:50:54 11:55:15 11:55:16 11:55:17 11:55:18 11:55:19 | 11:51:0
22/08/2013 11:51:00 Time change. System: 22/08/2013 11:51:00 PRTG (UTC): 22/08/2013 10:51:00 PRTG (Local Timezone): 22/08/2013 11:51:00
22/08/2013 11:51:00 Time Monitor:  11:50:50 11:50:51 11:50:52 11:50:53 11:50:54 11:55:15 11:55:16 11:55:17 11:55:18 11:55:19 | 11:51:0
22/08/2013 11:51:02 Possible timeshift detected: 258 seconds. Please check system time synchronisation settings!
22/08/2013 11:56:21 Time change. System: 22/08/2013 11:56:21 PRTG (UTC): 22/08/2013 10:52:00 PRTG (Local Timezone): 22/08/2013 11:52:00
22/08/2013 11:56:21 Time Monitor:  11:51:51 11:51:52 11:51:53 11:51:54 11:51:55 11:51:56 11:51:57 11:51:58 11:51:59 11:52:0 | 11:56:21
22/08/2013 11:52:05 Time change. System: 22/08/2013 11:52:05 PRTG (UTC): 22/08/2013 10:52:05 PRTG (Local Timezone): 22/08/2013 11:52:05
22/08/2013 11:52:05 Time Monitor:  11:51:56 11:51:57 11:51:58 11:51:59 11:52:0 11:56:21 11:56:22 11:56:23 11:56:24 11:56:25 | 11:52:5
22/08/2013 11:52:05 Time change. System: 22/08/2013 11:52:05 PRTG (UTC): 22/08/2013 10:52:05 PRTG (Local Timezone): 22/08/2013 11:52:05
22/08/2013 11:52:05 Time Monitor:  11:51:56 11:51:57 11:51:58 11:51:59 11:52:0 11:56:21 11:56:22 11:56:23 11:56:24 11:56:25 | 11:52:5
22/08/2013 11:52:07 Possible timeshift detected: 258 seconds. Please check system time synchronisation settings!

This can't be healthy, surely?

Created on Aug 22, 2013 10:57:06 AM by  Rich (50) 1 1

Last change on Aug 6, 2015 4:40:21 AM by  Luciano Lingnau [Paessler]



Votes:

0

Your Vote:

Up

Down

Do you have received my email? As this might be getting some more complex, please let us just switch to email conversation. Thank you!

Created on Aug 22, 2013 11:23:19 AM by  Konstantin Wolff [Paessler Support]



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Thanks very much for your help Konstantin, the issue was indeed caused by conflicting (and very frequent) time updates.

Everything is now working perfectly!

Created on Aug 22, 2013 2:17:41 PM by  Rich (50) 1 1



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.