Adam Wojnarski
2014-May-19 08:53 UTC
[Samba] need help cleaning up my smb3 databases to complete smb4 classic upgrade
Hi, Getting straight to the point: /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/root/elara/samba/ --use-xattrs=yes --realm=mycompanyname.com.pl/root/elara.smb.conf After cleaning up all duplicate names and sutch I end up with: ldb: ldb_trace_request: (tdb)->search ldb: ldb_trace_response: ENTRY dn: CN=CONFIG cn: CONFIG upperBound: 4000000 lowerBound: None xidNumber: None distinguishedName: CN=CONFIG ldb: cancel ldb transaction (nesting: 0) ldb: ldb_trace_request: (tdb)->del_transaction idmapping sid_to_xid failed for id[0]=S-1-5-21-1275545348-4294519683-4007804651-512: NT_STATUS_NONE_MAPPED ERROR(<class 'passdb.error'>): uncaught exception - Unable to get id for sid File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/domain.py", line 1448, in run useeadb=eadb, dns_backend=dns_backend, use_ntvfs=use_ntvfs) File "/usr/local/samba/lib64/python2.6/site-packages/samba/upgrade.py", line 851, in upgrade_from_samba3 result.names.domaindn, result.lp, use_ntvfs) File "/usr/local/samba/lib64/python2.6/site-packages/samba/provision/__init__.py", line 1612, in setsysvolacl set_gpos_acl(sysvol, dnsdomain, domainsid, domaindn, samdb, lp, use_ntvfs, passdb=s4_passdb) File "/usr/local/samba/lib64/python2.6/site-packages/samba/provision/__init__.py", line 1517, in set_gpos_acl passdb=passdb) File "/usr/local/samba/lib64/python2.6/site-packages/samba/provision/__init__.py", line 1480, in set_dir_acl setntacl(lp, path, acl, domsid, use_ntvfs=use_ntvfs, skip_invalid_chown=True, passdb=passdb, service=service) File "/usr/local/samba/lib64/python2.6/site-packages/samba/ntacls.py", line 104, in setntacl (owner_id, owner_type) = passdb.sid_to_id(sd.owner_sid) I have medium size environment ~60windows PCs, ~60users and ~200registered servers (many old ones were just disbanded and not removed from the domain, about 1/3 active) so it's not a big issue if I'll have to delete one of them and re-register it or check I already know that smb3 has no consistancy checks or other sanity checks so I know why is this happening. My issue is: How do i find the offending sid in my old dbs and get rid of it? I got my samba 4 from git://git.samba.org/samba.git samba-master my smb3 server is a an ancient fedora build samba-3.2.15-0.36.fc10.x86_64 - am I right to think that upgrading it to a current 3.x line version might help things or will the db's collect even more garbage with the upgrade? A few people managed it before me so I don't know it's full history. Any help will be greatly appreciated. Best Regards Adam
Marc Muehlfeld
2014-May-19 19:38 UTC
[Samba] need help cleaning up my smb3 databases to complete smb4 classic upgrade
Hello Adam, Am 19.05.2014 10:53, schrieb Adam Wojnarski:> My issue is: > How do i find the offending sid in my old dbs and get rid of it?What kind of backend do you use on your classic domain?> I got my samba 4 from git://git.samba.org/samba.git samba-master > my smb3 server is a an ancient fedora build samba-3.2.15-0.36.fc10.x86_64 - > am I right to think that upgrading it to a current 3.x line version might > help things or will the db's collect even more garbage with the upgrade? A > few people managed it before me so I don't know it's full history.If you have any concerns, you can simply update to 4.1.7 and if everything works like it should, then do the classicupgrade to AD a few days later. But why do you want to use a developer/git version and not a released one (4.1.7)? Releases are stable. I would not run a git version in production. Regards, Marc
Reasonably Related Threads
- regpatch writing to local registry hive with -F not working (registery-utils 4.0.0~alpha15~git20110124.dfsg1-2ubuntu1)
- SAMBA4 DDNS update samba_dnsupdate issues
- Duplicate base-DN matches found for <SID=1-5-11> after classic upgrade
- domain RODC fails with default provisioning
- Samba4 KDC - no such entry found in hdb