We had a power cut at the office and while the servers all appeared to shut down gracefully while on battery backup, upon rebooting them there was issues with the Primary DC. The secondary appeared fine, but on the primary, when the univention-directory-notifier service started, slapd would fail.
After several hours of troubleshooting and going through every article I could find with no results, I went for the nuclear option and restored both DCs from previous nights backup (they are VMs).
The DCs are now fine, and everything appears to work, however the member servers (both Univention Samba File Servers) are showing a UDN replication Warning in the diagnostics and running
gives the following:
CRITICAL: no change of listener transaction id for last 0 checks (nid=3975 lid=4061)
I expected this, but my question is, will the member servers sort themselves out once the DC’s transaction ID catches up?