Here is the English version:
Problem:
How can the Univention S4 Connector be reinitialized?
Solution:
A full resynchronization can be forced as follows:
First, stop the S4 Connector:
invoke-rc.d univention-s4-connector stop
Rename or delete the internal.sqlite file
This file contains the current synchronization state of the connector. It will be recreated during the next synchronization. In addition, cached data is backed up and any existing pickle files related to rejects are removed.
mv /etc/univention/connector/s4internal.sqlite /etc/univention/connector/s4internal.sqlite.bak
find /etc/univention/connector/ \( -name "s4*.sqlite" -o -name "lockingdb.sqlite" \) -exec mv "{}" "{}.bak_$(date +%s)" \;
rm -f /var/lib/univention-connector/s4/
Reinitialize the listener module:
univention-directory-listener-ctrl resync s4-connector
Start the S4 Connector:
/etc/init.d/univention-s4-connector start
The status can be checked in the following log files:
/var/log/univention/connector-s4-status.log
/var/log/univention/connector-s4.log