Rowland Penny
2018-Aug-25 07:29 UTC
[Samba] Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC
On Fri, 24 Aug 2018 23:53:14 +0200 Waishon <waishon009 at gmail.com> wrote:> Hi again, > > sorry for spaming ;) > > wbinfo -U shows on the second machine only: > root at FS/# wbinfo -U 0 > failed to call wbcUidToSid: WBC_ERR_DOMAIN_NOT_FOUND > Could not convert uid 0 to sid > > On the other machine it returns the correct SID. > > Maybe that's a decent hint what went wrong? >No, it is exactly the same on my domain, fails on a Unix domain member, works on a DC. Rowland
Waishon
2018-Aug-25 07:38 UTC
[Samba] Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC
Hi, that's interesting. Why does my other system returns S-1-22-1-0 with the Samba Database that was provisioned before 4.8.x and only upgraded. Mhh The user.map contains: !root = SCHULE\\Administrator Have you tested the following: When running "samba ntacl get -D 10" onto a file with the permissions chown root:root, chmod 777, I get the stacktrace with the error in the above debug logs: uid_to_sid: winbind failed to find a sid for uid 0 When checking the same command against another file with the permissions chown "SAMDOM\\Administrator":"SAMDOM\\Administrator", chmod 777 I get the expected ntacl output without any crash. Maybe you can check if you're able to reproduce this to know if it's a general bug or only a misconfiguration on my system. Thanks in advance. Am Samstag, 25. August 2018 schrieb Rowland Penny via samba :> On Fri, 24 Aug 2018 23:53:14 +0200 > Waishon <waishon009 at gmail.com> wrote: > > > Hi again, > > > > sorry for spaming ;) > > > > wbinfo -U shows on the second machine only: > > root at FS/# wbinfo -U 0 > > failed to call wbcUidToSid: WBC_ERR_DOMAIN_NOT_FOUND > > Could not convert uid 0 to sid > > > > On the other machine it returns the correct SID. > > > > Maybe that's a decent hint what went wrong? > > > > No, it is exactly the same on my domain, fails on a Unix domain member, > works on a DC. > > Rowland > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
Rowland Penny
2018-Aug-25 08:02 UTC
[Samba] Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC
On Sat, 25 Aug 2018 09:38:09 +0200 Waishon <waishon009 at gmail.com> wrote:> Hi, > > that's interesting. Why does my other system returns S-1-22-1-0 with > the Samba Database that was provisioned before 4.8.x and only > upgraded. MhhProbably because you are using the 'rid' backend and I use the 'ad' backend on Unix domain members.> > The user.map contains: > !root = SCHULE\\AdministratorIt should be '!root = SCHULE\Administrator'> > Have you tested the following: > When running "samba ntacl get -D 10" onto a file with the permissions > chown root:root, chmod 777, I get the stacktrace with the error in > the above debug logs: > uid_to_sid: winbind failed to find a sid for uid 0 > > When checking the same command against another file with the > permissions chown "SAMDOM\\Administrator":"SAMDOM\\Administrator", > chmod 777 I get the expected ntacl output without any crash. > > Maybe you can check if you're able to reproduce this to know if it's a > general bug or only a misconfiguration on my system.I tried it on a Unix domain member and it didn't error, but I also didn't get any output. As Andrew said, there is a bug in there somewhere, it shouldn't panic, but using samba-tool on a Unix domain member isn't really supported. Some of it will work, but usually only when pointed at a DC. Rowland
Reasonably Related Threads
- Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC
- Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC
- Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC
- Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC
- Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC