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

What are conditions for PRTG Probe Service to restart automatically

Votes:

0

Your Vote:

Up

Down

Hello,

Periodically PRTG Probe Service seems to restart itself based on certain conditions. Atleast:

"Trying to restart probe. Reason: more than 50 unresponsive scan threads" is one of these.

Are there any other conditions when this is triggered?

br, Olli Jokinen

probe prtg restart service

Created on Aug 4, 2010 6:00:19 AM by  Olli Jokinen (10) 1



5 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

In essence, the only situations that cause the probe service to restart are:

  • more than 50 unresponsive scan threads
  • all WMI connections being in an identical error state

And, of course, restarting the service manually.

Created on Aug 5, 2010 3:08:11 PM by  Patrick Hutter [Paessler Support] (7,225) 3 3



Votes:

0

Your Vote:

Up

Down

Thanks for the info,

Additionally is this another condition as well?

"Trying to restart probe. Reason: connection unresponsive for more than 60 seconds."

Since this seems to have the same effect...

Created on Aug 6, 2010 10:04:04 AM by  Olli Jokinen (10) 1



Votes:

0

Your Vote:

Up

Down

The message "connection unresponsive for more than 60 seconds" is one of the ways a stalled probe<>core SSL connection can materialize.

Created on Aug 6, 2010 10:21:51 AM by  Dirk Paessler [Founder Paessler AG] (10,983) 3 5



Votes:

0

Your Vote:

Up

Down

Should this be the case when data is cached on the probe until the core is back online?

It would be beneficial to understand all possible conditions when to expect such problems.

Created on Sep 2, 2010 7:40:53 PM by  Olli Jokinen (10) 1



Votes:

0

Your Vote:

Up

Down

Yes, a probe might also be restarted even if it has cached data, due to a "not available" Core Server. Because it is surely better to have a working/monitoring probe rather than a not-scanning one, which has a bit of cached data.

Created on Sep 3, 2010 12:41:14 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.