Univention Bugzilla – Bug 33940
(Re-)Join should remove s4internal.sqlite
Last modified: 2014-02-06 13:37:39 CET
Ticket#2014011521001985 A customer reported that the s4-connector stopped synchronizing changes from S4 to LDAP (LDAP->S4 working fine) after rejoin of a (UCS@school) DC-Slave. It turned out that the lastUSN in s4internal.sqlite was a lot higher than the actual lastUSN in S4 so I guess the s4internal.sqlite is not removed during (re)-join. Workaround: invoke-rc.d univention-s4-connector stop sqlite3 /etc/univention/connector/s4internal.sqlite 'update S4 set value=0;' invoke-rc.d univention-s4-connector start
The database is now removed while re-joining: r47416 YAML: r47417
Verified (e.g. in UCS@school): root@slave47:~# ls -l /etc/univention/connector/s4* -rw-r--r-- 1 root root 79872 28. Jan 14:23 /etc/univention/connector/s4internal.sqlite -rw-r--r-- 1 root root 93184 28. Jan 14:22 /etc/univention/connector/s4internal.sqlite_20140128142302 Advisory Ok.
http://errata.univention.de/ucs/3.2/48.html