I’m having trouble getting sysvol replication to work with a DC backup I just installed. The errors I’m getting in sysvol-sync.log are:
2018-11-21 18:10:18 ERROR [amanda] placing triggerfile with ssh failed with 1. (Could not chdir to home directory /dev/null: Not a directorymkdir: cannot create directory '/var/cache/univention-samba4/sysvol-sync': Permission deniedtouch: cannot touch '/var/cache/univention-samba4/sysvol-sync/.trigger/sarek': Permission denied)
2018-11-21 18:10:18 ERROR [amanda] Placing a trigger file failed.
I think the problem is that while dealing with s4-connector rejects, I deleted a couple of users that showed up in the rejects (dc.slave and dc.backup, I think? The rejects seem to have been related to my migration from Zentyal to UCS months ago, as the Zentyal hostnames appeared in some of the rejects).
Would deleting those users be the reason? If so, how do I properly recreate those users?
Hey,
those two user names dc.slave and dc.backup sound like names of UCS servers. There’s a machine (computer) account for each server in the domain, and those accounts must not be deleted as they’re used for a lot of things, the sysvol sync amongst others.
The easiest way to re-create those machine accounts is to re-join the affected UCS servers by running the command univention-join on each of them. Re-joining is safe insofar as no user data is deleted during the process. During the re-join all domain-relevant data and settings are re-created on and re-transferred from the DC Master.
Kind regards,
mosu
Thanks for your response! univention-join is how I joined the domain after deleting those users, so I know it doesn’t create them. But it is the fact that the sysvol replication errors mention “home directory /dev/null” that made me wonder about user accounts. I think I need to know what account’s home directory it’s talking about and how to recreate the user or assign it a home directory if the user does still exist.