Greetings,
This post pertains to Samba version 4.16.8 on FreeBSD 13.1.
When GPMC.MSC is invoked from within a Windows server domain member, it
displays an inconsistency error:
<https://attachments.samba.org/attachment.cgi?id=8386>
<https://bugzilla.samba.org/show_bug.cgi?id=14927>
# samba-tool ntacl sysvolreset
# samba-tool ntacl sysvolcheck
ERROR(<class 'TypeError'>): uncaught exception - (22, 'Invalid
argument')
File
"/usr/local/lib/python3.9/site-packages/samba/netcmd/__init__.py",
line
186, in _run
return self.run(*args, **kwargs)
File
"/usr/local/lib/python3.9/site-packages/samba/netcmd/ntacl.py",
line 443, in run
provision.checksysvolacl(samdb, netlogon, sysvol,
File
"/usr/local/lib/python3.9/site-packages/samba/provision/__init__.py",
line 1874, in checksysvolacl
fsacl = getntacl(lp, dir_path, session_info,
direct_db_access=direct_db_access, service=SYSVOL_SERVICE)
File "/usr/local/lib/python3.9/site-packages/samba/ntacls.py", line
112, in getntacl
attribute = samba.xattr_native.wrap_getxattr(file,
Doesn't remedy the inconsistency. Is the information at the following
link still valid?
<https://support.microsoft.com/en-US/help/2838154/permissions-for-this-gpo-in-the-sysvol-folder-are-inconsistent-with-th>
Any other ideas?
Thank you in advance.
Danke,
--
Don, KB7RPU, https://www.qsl.net/kb7rpu
There was a young lady named Bright Whose speed was far faster than
light;
She set out one day In a relative way And returned on the previous
night.
On 05/05/2023 17:34, Don Kuenz via samba wrote:> Greetings, > > This post pertains to Samba version 4.16.8 on FreeBSD 13.1.There have been lots of problems reported with running a Samba AD DC on FreeBSD.> > When GPMC.MSC is invoked from within a Windows server domain member, it > displays an inconsistency error: > > ? <https://attachments.samba.org/attachment.cgi?id=8386> > > ? <https://bugzilla.samba.org/show_bug.cgi?id=14927> > > # samba-tool ntacl sysvolreset > # samba-tool ntacl sysvolcheck > ERROR(<class 'TypeError'>): uncaught exception - (22, 'Invalid argument') > ? File > "/usr/local/lib/python3.9/site-packages/samba/netcmd/__init__.py", line > 186, in _run > ??? return self.run(*args, **kwargs) > ? File "/usr/local/lib/python3.9/site-packages/samba/netcmd/ntacl.py", > line 443, in run > ??? provision.checksysvolacl(samdb, netlogon, sysvol, > ? File > "/usr/local/lib/python3.9/site-packages/samba/provision/__init__.py", > line 1874, in checksysvolacl > ??? fsacl = getntacl(lp, dir_path, session_info, > direct_db_access=direct_db_access, service=SYSVOL_SERVICE) > ? File "/usr/local/lib/python3.9/site-packages/samba/ntacls.py", line > 112, in getntacl > ??? attribute = samba.xattr_native.wrap_getxattr(file,I do not think you are hitting bug 14927, you are resetting the ACL's on sysvol and then immediately checking them, where it fails. This is possibly being caused by the NFSv4 acls that freebsd uses, as both commands work correctly on Linux. Rowland