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
Check the rejected status of the connector. If you find rejects here, try to solve them with the help of this article:
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