Univention Bugzilla – Bug 48917
sysvol-sync fails because lock directory is owned 640 by some UCS slave ADDC
Last modified: 2019-04-08 17:34:16 CEST
root@backup11:~# tail -f /var/log/univention/sysvol-sync.log sh: 1: cannot create /var/lock/sysvol-sync-dir: Permission denied 2019-02-28 06:40:09 ERROR [master10] Could not aquire remote read lock after 30 seconds. 2019-02-28 06:40:09 ERROR [master10] Skipping sync to local sysvol! sh: 1: cannot create /var/lock/sysvol-sync-dir: Permission denied 2019-02-28 06:45:14 ERROR [master10] Could not aquire remote read lock after 30 seconds. 2019-02-28 06:45:14 ERROR [master10] Skipping sync to local sysvol! root@master10:~# ls -ld /var/lock/sysvol-sync-dir -rw-r--r-- 1 slave12$ DC Slave Hosts 0 Feb 28 06:30 /var/lock/sysvol-sync-dir
It occurred in a domain that was updated from UCS 4.1 originally, so maybe it's just an artefact of an old bug that has already been fixed (bug not properly).
Yes, this can happen if the file is not present on the upstream server. In this case get_remote_lock() creates the lock file with default permissions. fixed in univention-samba4 72f8111531d7babe731f601d42c0a9909a9200b7 yaml 23a5e43afb32e0a8fee282d88dac673e71b75676
Ok.
<http://errata.software-univention.de/ucs/4.4/35.html>