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?

Article Comments

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.


Oct, 2012 - Permalink

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


Oct, 2012 - Permalink

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


Oct, 2012 - Permalink

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?


Oct, 2012 - Permalink

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.


Oct, 2012 - Permalink