Changing Notification Settings Causes PRTG Crash

Modified on 2025-06-10 12:20:30 +0200

Hi,

Enabling/disabling the Amazon Simple Notification Service for notifications at the the root level has caused the core server to crash for up to 45 minutes causing all monitoring to be lost. This was not a one off occurrence. Any suggestions to why this is happening and how to avoid it?

Cheers

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 Dylan,

Thank you for your post.

I'm afraid I'm not able to reproduce your issue. Could you please forward us a Support Bundle including the system log files for analysis?

Please open the "PRTG Administration Tool" and send us the Log Files from the tab card "Logs and Infos". Please enter this ticket's case number (PAE1132749) when submitting the Bundle.

Thank you in advance!

Kind regards,
Andreas Günther
Tech Support, Paessler AG

Dec, 2018 - Permalink

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.

Changing Notification Settings Causes PRTG Crash

Article CommentsAttention: 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.

Search

Attention

Related Articles

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.