Univention Bugzilla – Bug 33942
Check for posix ACL support when joining
Last modified: 2014-03-31 08:12:11 CEST
Ticket#: 2014011421000077 A customer reported problems joining a new UCS 3.2 Samba4 DC-Slave. In join.log, the process is complaining about missing posix ACL support several times (12 times to be precise): --- Searching for dsServiceName in rootDSE failed: operations error at ../source4/dsdb/samdb/ldb_modules/rootdse.c:501 Failed to find our own NTDS Settings DN in the ldb! ldb: module schema_load initialization failed : No such object ldb: module rootdse initialization failed : No such object ldb: module samba_dsdb initialization failed : No such object ldb: Unable to load modules for /var/lib/samba/private/sam.ldb: (null) samdb_connect failed VFS connect failed! ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: Your filesystem or build does not support posix ACLs, which s3fs requires. Try the mounting the filesystem with the 'acl' option. File "/usr/lib/python2.6/dist-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File "/usr/lib/python2.6/dist-packages/samba/netcmd/domain.py", line 560, in run machinepass=machinepass, use_ntvfs=use_ntvfs, dns_backend=dns_backend) File "/usr/lib/python2.6/dist-packages/samba/join.py", line 1220, in join_DC ctx.do_join() File "/usr/lib/python2.6/dist-packages/samba/join.py", line 1101, in do_join ctx.join_provision() File "/usr/lib/python2.6/dist-packages/samba/join.py", line 752, in join_provision use_ntvfs=ctx.use_ntvfs, dns_backend=ctx.dns_backend) File "/usr/lib/python2.6/dist-packages/samba/provision/__init__.py", line 2052, in provision raise ProvisioningError("Your filesystem or build does not support posix ACLs, which s3fs requires. Try the mounting the filesystem with the 'acl' option.") Join failed - cleaning up --- Maybe we should check for ACL support and print a helpful error message.
That exception message is from a catch all "except Exception:" block, so it might not be related to acl_xattr at all. This is supported by the customers observation that the filesystem actually is mounted with acl_xattr. I guess "samdb_connect failed" and the stuff leading up to it are relevant.
Confirmed by the Ticket, this is only an artefact of a segfault during the initial domain join, due to a missing objectclass attribute on some object.