Hi paessler, what does this mean and should i be concerned? It restarted dead in the middle of our busiest period and i want to make sure this doesnt happen again, we were running your since rolled back update and have since updated over that with the fixed version


Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi Sam,

Please send a support bundle via Setup | Contact Support so we can check this. Usually, this is caused by various parts of PRTG trying to access the same ressource either to read or write, but can't do so since it's locked. This is fixable sometimes. If it's not fixable, it was probably something that won't occur again since the condition was more of a singularity.


Kind regards,
Stephan Linke, Tech Support Team


Nov, 2017 - Permalink