Problem setting Sensor to Error in a v8.1Clustered environment
Modified on 2025-06-10 12:06:22 +0200
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.
Important: We no longer maintain this article. The information might be out of date.
Before migrating to a clustered PRTG setup we were able to log into a PRTG Node and set a sensor to error for testing purposes (this is part of our monthly test to ensure that our sensor notifications are being sent/received).
Now, when setting a sensor to error (Right click -> Pause -> Set Sensor to Error) it must be completed on the Primary Node in the cluster (and cannot be completed on the secondary node as configuration changes are not accepted).
This causes the sensor to go into a Partial Down state (Primary Node recognises it has been set to error, but secondary node does not because we cannot set it in that node) and the notification is never triggered because a Down (Full Down) state is never met.
Is there a way to set a sensor to error on both nodes to initiate a down state?
Article Comments
This will be amended in an upcoming update release. Please bear with us.
Nov, 2010 - 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.
This will be amended in an upcoming update release. Please bear with us.
Nov, 2010 - Permalink