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
The PRTG core service was restarted due to a deadlock event
Modified on 2025-06-10 20:57:36 +0200
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.
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.
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