Univention Bugzilla – Bug 42657
replication.py completely fills /var with failed move_to pickle files
Last modified: 2021-02-05 17:49:57 CET
If a move_to operation could not be processed correctly the listener and the replication module place files in /var/lib/univention-directory-replication and /var/univention-backup/replication and might fill up the complete disc, either by space or by inode. After the disc has been filled completely the listener continues to process new notifier ids buts fails at creating the backup files. I also noticed that /var/lib/univention-directory-replication seems to be never cleaned up by the listener. It would avoid manual intervention and filled filesystems, if the backup creation is configurable and the files in /var/lib/univention-directory-replication are removed after a certain time, e.g. based on processed notifier ids since creation.
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
With Bug #34355 fixed with git:07d8c9a42eb7c25234387c611a164337c60f3dce since release-3.2-2~116 UDL guarantees to always perform the two parts of a rename/move transaction in sequence. Therefor it is sufficient to keep the state in memory and the code to persist it to disk can (and should) be removed completely. Patch in git:phahn/replication