Univention Bugzilla – Bug 45399
UMC-Diagnostic check for notifier-ID rollback
Last modified: 2020-07-03 20:56:16 CEST
The UMC diagnostic plugin "03_check_notifier_replication.py" should report a critical state if a notifier-ID rollback has been detected, i.e. if the upstream ID is *lower* than the local ID. That's what usually happens when an administrator decides to revert a vertualized master to an earlier snapshot. +++ This bug was initially created as a clone of Bug #45398 +++
Created attachment 9205 [details] diagnostic_check_for_notifier_replication_rollback.patch
(In reply to Arvid Requate from comment #0) > The UMC diagnostic plugin "03_check_notifier_replication.py" should report a > critical state if a notifier-ID rollback has been detected, i.e. if the > upstream ID is *lower* than the local ID. Please note, that this might also happen if a slaves switches from dc master to a still replicating dc backup: dc master dc backup slave NID 1234 1200 ---- LID 1234 1200 1234 ← slave is using notifier of dc master now the connection between notifier of dc master and listener of dc slave is lost and a new connection is established by the dc slave with the notifier of the dc backup. Since the dc backup is still replicating, the UMC diagnostic check on the dc slave should NOT show an critical error, that the NID (of dc backup) is lower than the LID of the dc slave, if the NID of the dc master is equal or higher than the LID of the dc slave.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.