Problem: lockingdb.sqlite file is over 10 GB in size

[scheinig]

Problem:

The lockingdb.sqlite file is high above GB in size
-rw-r--r-- 1 root root 13G Dez 12 08:09 /etc/univention/connector/lockingdb.sqlite

Investigation

Check the rejected status of the connector. If you find rejects here, try to solve them with the help of this article:

How to deal with s4-connector rejects

S4-Connector Rejects Rejects You can use the following command to have a look at the current S4-Connector replication status: univention-s4connector-list-rejected If you see rejected objects in the output it is recommended to have a look at the relevant log files to determine the reason for the reject. The relevant log file is /var/log/univention/connector-s4.log. UCS rejected refers to object modifications that have been detected in UCS/OpenLDAP and could not be synchronized to the Samba/AD …

S4-Connector:
univention-s4connector-list-rejected
AD-Connector:
univention-connector-list-rejected

Solution

If all rejects are resolved, both tables can be emptied in the database.
Of course you are welcome to make a backup. Before you do so, stop the S4 connector, empty tables using sqlite3 and restart the connector.

/etc/init.d/univention-s4-connector stop
sqlite3 /etc/univention/connector/lockingdb.sqlite
sqlite>.tables                   # show tables
sqlite> select * from UCS_LOCK;  # have a look, if you want
sqlite> select * from S4_LOCK;
sqlite> DELETE from UCS_LOCK;     # empty 
sqlite> DELETE from S4_LOCK;
sqlite> VACUUM;
sqlite>.quit
/etc/init.d/univention-s4-connector start