Bug 50504 - check_univention_replication should go CRITICAL on DC backup if NID is smaller than LID
check_univention_replication should go CRITICAL on DC backup if NID is smalle...
Status: NEW
Product: UCS
Classification: Unclassified
Component: Monitoring (Prometheus or Nagios)
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-11-15 11:54 CET by Sönke Schwardt-Krummrich
Modified: 2022-06-27 17:48 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2019-11-15 11:54:55 CET
/usr/lib/nagios/plugins/check_univention_replication should return a "CRITICAL" state and an appropriate error message on a DC backup, if the notifier ID (of the DC master) is smaller than the listener ID (of the DC backup).

This situation might happen, if snapshots are reverted in the wrong order (or only the DC master is reverted).

check_univention_replication should NOT go into "CRITICAL" state on a DC slave/member if the nid is smaller than the lid →
if the listener of the dc slave switches e.g. from master to backup, the NID may jump to a smaller value, because the backup is not yet up to date. So this would be no problem.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2020-02-09 22:34:54 CET
(In reply to Sönke Schwardt-Krummrich from comment #0)
> check_univention_replication should NOT go into "CRITICAL" state on a DC
> slave/member if the nid is smaller than the lid →
> if the listener of the dc slave switches e.g. from master to backup, the NID
> may jump to a smaller value, because the backup is not yet up to date. So
> this would be no problem.

Addition:
If check_univention_replication is checking against the DC master and the master's NID is smaller than the local LID, the check HAS TO complain.