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


Traceroute sensors waiting for mutex (code PE035)

Votes:

0

Your Vote:

Up

Down

I have multiple traceroute sensors in the error state "Timeout caused by wait for mutex (code: PE035)".

This is a surprise because these are not custom/exe sensors, but the standard traceroute sensor provided in PRTG. I can't find anywhere I can set the mutex for this type of sensor either.

Does anybody know what can cause this or how I can make the problem go away?

mutex pe035 prtg traceroute

Created on Oct 10, 2012 8:16:11 AM by  Morten Elk (0) 1



5 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

the traceroute sensor is actually internally an executable. How many of those sensors with which scanning interval do you have (under one probe)?

best regards.

Created on Oct 10, 2012 1:03:46 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

We have a couple of probes with the problem. Two of the probes have two traceroute sensors each scanning at a 15m interval. It seems the problem is fixed for a while if we stop and start the probe service.

Best, Thomas

Created on Oct 15, 2012 12:40:35 PM by  Morten Elk (0) 1



Votes:

0

Your Vote:

Up

Down

What do these two sensors then have as values usually under "Execution Time"?

Created on Oct 15, 2012 1:41:25 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Typical response times are 400-800ms. However, I can see that when one of the sensors developed the issue we had elevated response times. This happened a couple of days ago, so I only have averages, but as far as I can tell there probably was some spike in response times. Does that help?

Created on Oct 15, 2012 2:45:19 PM by  Morten Elk (0) 1



Votes:

0

Your Vote:

Up

Down

There is an issue with the sensor when the target is not available. We will send you a fixed version of the sensor via email.

Created on Oct 16, 2012 9:01:40 AM by  Torsten Lindner [Paessler Support]

Last change on Oct 16, 2012 9:50:57 AM 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.