First of all thank you all for the answers and for trying to help me. I agree with you michael regarding the parameters passed in the ./configure command, the location is not part of the problem. The file system used is XFS. and the strace command logs are in the attached link https://drive.google.com/file/d/1R_b6TzeJVmNIpnlkPfRk0CtkpeU4dgcg/view?usp=share_link Rowland, the result of the command mentioned by you: samba-tool ntacl get /usr/local/samba/var/lib/samba/sysvol --as-sddl O:LAG:BAD:P(A;OICI;0x001f01ff;;;BA)(A;OICI;0x001200a9;;;SO)(A;OICI;0x001f01ff;;;SY)(A;OICI;0x001200a9;;;AU ) Em dom., 2 de abr. de 2023 ?s 06:29, Rowland Penny via samba < samba at lists.samba.org> escreveu:> > > On 02/04/2023 09:21, Michael Tokarev via samba wrote: > > > Neither of the 3 should be a problem. Especially the ones which > > are already set by default. --enable-fhs uses slightly different > > layout within $prefix, that's all. The build-time configuration > > looks entirely okay. > > You may be correct Michael, but I still wouldn't use '--enable-fhs' by > itself. > > > > > There's something else going on here. > > Very probaby. > > > > > Anderson, what filesystem the sysvol is on? > > This may be the cause, but it isn't being helped by Anderson using the > wrong tool to check the permissions, he should be using samba-tool > because this is a DC and the permissions are stored in an EA. I suggest > he posts the output of: > > sudo samba-tool ntacl get /usr/local/samba/var/lib/samba/sysvol --as-sddl > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
On 03/04/2023 00:53, Anderson Sampaio Mello via samba wrote:> First of all thank you all for the answers and for trying to help me. > > I agree with you michael regarding the parameters passed in the ./configure > command, the location is not part of the problem. > > The file system used is XFS. and the strace command logs are in the > attached link > https://drive.google.com/file/d/1R_b6TzeJVmNIpnlkPfRk0CtkpeU4dgcg/view?usp=share_link > > Rowland, the result of the command mentioned by you: > > samba-tool ntacl get /usr/local/samba/var/lib/samba/sysvol --as-sddl > > O:LAG:BAD:P(A;OICI;0x001f01ff;;;BA)(A;OICI;0x001200a9;;;SO)(A;OICI;0x001f01ff;;;SY)(A;OICI;0x001200a9;;;AU > ) >That is exactly what would be expected, so there appears to be nothing wrong with the permissions. There probably isn't anything wrong with the location, which leaves us with the filesystem and the programs you installed to compile Samba. The xfs filesystem is supposed to be okay with Samba, so what OS are you using (it appears to be a red-hat variant) and what packages did you install ? Rowland
03.04.2023 02:53, Anderson Sampaio Mello via samba ?????:> First of all thank you all for the answers and for trying to help me. > > I agree with you michael regarding the parameters passed in the ./configure > command, the location is not part of the problem. > > The file system used is XFS. and the strace command logs are in the > attached link > https://drive.google.com/file/d/1R_b6TzeJVmNIpnlkPfRk0CtkpeU4dgcg/view?usp=share_linkFrom this trace: getxattr("/usr/local/samba/var/lib/samba/sysvol/exemple.com", "security.NTACL", NULL, 0) = 320 getxattr("/usr/local/samba/var/lib/samba/sysvol/exemple.com", "security.NTACL", "\4\0\4\0\0\0\2\0\4\0\2\0\1\0\35\26\34P,\223\25\234{\21\3324g-\34\rgD"..., 320) = 320 getxattr("/usr/local/samba/var/lib/samba/sysvol/exemple.com/scripts", "security.NTACL", NULL, 0) = 0 getxattr("/usr/local/samba/var/lib/samba/sysvol/exemple.com/scripts", "security.NTACL", "", 0) = 0 write(2, "ERROR(runtime): uncaught excepti"..., 63ERROR(runtime): uncaught exception - (11, 'Buffer Size Error') So it looks like we have a bug in the python code. After successful getxattr() call (for a fun filename - exemple.com) it return an error. It smells like the code does not expect to see 0-length NTACL. /mjt