Elias Pereira
2015-May-21 16:28 UTC
[Samba] Import idmap database error on classicupgrade process
You're right, man! Sorry! My mistake! I put that file because I read in somewhere about the persistent and temporary files regarding .tdb files. The winbindd_idamp.tbm was on that list, and I think that's why I left it in the folder. :D Another doubt. For the provisioning starts, I had to comment out the line referring to the ldap backend in the smb.conf of samba3. # passdb backend = ldapsam:ldap://empresa.com This can affect the provisioning? On Thu, May 21, 2015 at 12:48 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote:> On 21/05/15 16:31, Elias Pereira wrote: > >> I copied all the database files of samba3 as is mentioned in the wiki - >> The >> classicupgrade process >> < >> https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process >> > >> >> >> But if the winbindd_idmap.tdb file is in the folder, the errors occur. See >> below: >> >> Importing idmap database >> >>> ERROR(assert): uncaught exception >>> File >>> "/opt/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", >>> line 175, in _run >>> return self.run(*args, **kwargs) >>> File "/opt/samba/lib/python2.7/site-packages/samba/netcmd/domain.py", >>> line 1452, in run >>> useeadb=eadb, dns_backend=dns_backend, use_ntvfs=use_ntvfs) >>> File "/opt/samba/lib/python2.7/site-packages/samba/upgrade.py", line >>> 749, in upgrade_from_samba3 >>> import_idmap(result.idmap, samba3, logger) >>> File "/opt/samba/lib/python2.7/site-packages/samba/upgrade.py", line >>> 215, in import_idmap >>> samba3_idmap = samba3.get_idmap_db() >>> File >>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>> line 406, in get_idmap_db >>> return IdmapDatabase(self.statedir_path("winbindd_idmap")) >>> File >>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>> line 63, in __init__ >>> self._check_version() >>> File >>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>> line 146, in _check_version >>> assert fetch_int32(self.db, "IDMAP_VERSION\0") == IDMAP_VERSION_V2 >>> >> >> If I remove/delete the file, the provisioning continues and tells me he >> did >> not find the file: *Can not open database idmap, Ignoring: [Errno 2] No >> such file or directory* >> >> Can I still provisioning without the file? There is the possibility of >> post-migration issues regarding lack of this file? >> >> > Hi, on the wiki page, it tells you to copy: > > secrets.tdb > schannel_store.tdb > passdb.tdb > gencache_notrans.tdb > group_mapping.tdb > account_policy.tdb > > It does not mention 'winbindd_idmap.tdb'. > > So why are you including it ? > > Rowland > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >-- Elias Pereira
Rowland Penny
2015-May-21 16:53 UTC
[Samba] Import idmap database error on classicupgrade process
On 21/05/15 17:28, Elias Pereira wrote:> You're right, man! Sorry! My mistake! > > I put that file because I read in somewhere about the persistent and > temporary files regarding .tdb files. The winbindd_idamp.tbm was on that > list, and I think that's why I left it in the folder. :D > > Another doubt. For the provisioning starts, I had to comment out the line > referring to the ldap backend in the smb.conf of samba3. > > # passdb backend = ldapsam:ldap://empresa.com > > This can affect the provisioning?Possibly, without that line I don't think it will contact the ldap server, but 'ldap://empresa.com' doesn't look right, I would expect something like 'ldap://ldapdc.empresa.com' or 'ldap://127.0.0.1' i.e a resolvable dns address. Rowland> > On Thu, May 21, 2015 at 12:48 PM, Rowland Penny <rowlandpenny at googlemail.com >> wrote: >> On 21/05/15 16:31, Elias Pereira wrote: >> >>> I copied all the database files of samba3 as is mentioned in the wiki - >>> The >>> classicupgrade process >>> < >>> https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process >>> >>> But if the winbindd_idmap.tdb file is in the folder, the errors occur. See >>> below: >>> >>> Importing idmap database >>> >>>> ERROR(assert): uncaught exception >>>> File >>>> "/opt/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", >>>> line 175, in _run >>>> return self.run(*args, **kwargs) >>>> File "/opt/samba/lib/python2.7/site-packages/samba/netcmd/domain.py", >>>> line 1452, in run >>>> useeadb=eadb, dns_backend=dns_backend, use_ntvfs=use_ntvfs) >>>> File "/opt/samba/lib/python2.7/site-packages/samba/upgrade.py", line >>>> 749, in upgrade_from_samba3 >>>> import_idmap(result.idmap, samba3, logger) >>>> File "/opt/samba/lib/python2.7/site-packages/samba/upgrade.py", line >>>> 215, in import_idmap >>>> samba3_idmap = samba3.get_idmap_db() >>>> File >>>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>>> line 406, in get_idmap_db >>>> return IdmapDatabase(self.statedir_path("winbindd_idmap")) >>>> File >>>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>>> line 63, in __init__ >>>> self._check_version() >>>> File >>>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>>> line 146, in _check_version >>>> assert fetch_int32(self.db, "IDMAP_VERSION\0") == IDMAP_VERSION_V2 >>>> >>> If I remove/delete the file, the provisioning continues and tells me he >>> did >>> not find the file: *Can not open database idmap, Ignoring: [Errno 2] No >>> such file or directory* >>> >>> Can I still provisioning without the file? There is the possibility of >>> post-migration issues regarding lack of this file? >>> >>> >> Hi, on the wiki page, it tells you to copy: >> >> secrets.tdb >> schannel_store.tdb >> passdb.tdb >> gencache_notrans.tdb >> group_mapping.tdb >> account_policy.tdb >> >> It does not mention 'winbindd_idmap.tdb'. >> >> So why are you including it ? >> >> Rowland >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >> > >
Elias Pereira
2015-May-21 17:22 UTC
[Samba] Import idmap database error on classicupgrade process
Ok. I uncomment that line and put: passdb backend = ldapsam:ldap://127.0.0.1 Error message: Provisioning> smbldap_search_domain_info: Searching > for:[(&(objectClass=sambaDomain)(sambaDomainName=EMPRESA))] > smbldap_open_connection: connection opened > failed to bind to server ldap://127.0.0.1 with > dn="cn=Manager,dc=empresa,dc=com" Error: Invalid credentials > (unknown)On Thu, May 21, 2015 at 1:53 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote:> On 21/05/15 17:28, Elias Pereira wrote: > >> You're right, man! Sorry! My mistake! >> >> I put that file because I read in somewhere about the persistent and >> temporary files regarding .tdb files. The winbindd_idamp.tbm was on that >> list, and I think that's why I left it in the folder. :D >> >> Another doubt. For the provisioning starts, I had to comment out the line >> referring to the ldap backend in the smb.conf of samba3. >> >> # passdb backend = ldapsam:ldap://empresa.com >> >> This can affect the provisioning? >> > > Possibly, without that line I don't think it will contact the ldap server, > but 'ldap://empresa.com' doesn't look right, I would expect something > like 'ldap://ldapdc.empresa.com' or 'ldap://127.0.0.1' i.e a resolvable > dns address. > > Rowland > > >> On Thu, May 21, 2015 at 12:48 PM, Rowland Penny < >> rowlandpenny at googlemail.com >> >>> wrote: >>> On 21/05/15 16:31, Elias Pereira wrote: >>> >>> I copied all the database files of samba3 as is mentioned in the wiki - >>>> The >>>> classicupgrade process >>>> < >>>> >>>> https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process >>>> >>>> But if the winbindd_idmap.tdb file is in the folder, the errors occur. >>>> See >>>> below: >>>> >>>> Importing idmap database >>>> >>>> ERROR(assert): uncaught exception >>>>> File >>>>> "/opt/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", >>>>> line 175, in _run >>>>> return self.run(*args, **kwargs) >>>>> File >>>>> "/opt/samba/lib/python2.7/site-packages/samba/netcmd/domain.py", >>>>> line 1452, in run >>>>> useeadb=eadb, dns_backend=dns_backend, use_ntvfs=use_ntvfs) >>>>> File "/opt/samba/lib/python2.7/site-packages/samba/upgrade.py", >>>>> line >>>>> 749, in upgrade_from_samba3 >>>>> import_idmap(result.idmap, samba3, logger) >>>>> File "/opt/samba/lib/python2.7/site-packages/samba/upgrade.py", >>>>> line >>>>> 215, in import_idmap >>>>> samba3_idmap = samba3.get_idmap_db() >>>>> File >>>>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>>>> line 406, in get_idmap_db >>>>> return IdmapDatabase(self.statedir_path("winbindd_idmap")) >>>>> File >>>>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>>>> line 63, in __init__ >>>>> self._check_version() >>>>> File >>>>> "/opt/samba/lib/python2.7/site-packages/samba/samba3/__init__.py", >>>>> line 146, in _check_version >>>>> assert fetch_int32(self.db, "IDMAP_VERSION\0") =>>>>> IDMAP_VERSION_V2 >>>>> >>>>> If I remove/delete the file, the provisioning continues and tells me >>>> he >>>> did >>>> not find the file: *Can not open database idmap, Ignoring: [Errno 2] No >>>> such file or directory* >>>> >>>> Can I still provisioning without the file? There is the possibility of >>>> post-migration issues regarding lack of this file? >>>> >>>> >>>> Hi, on the wiki page, it tells you to copy: >>> >>> secrets.tdb >>> schannel_store.tdb >>> passdb.tdb >>> gencache_notrans.tdb >>> group_mapping.tdb >>> account_policy.tdb >>> >>> It does not mention 'winbindd_idmap.tdb'. >>> >>> So why are you including it ? >>> >>> Rowland >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: https://lists.samba.org/mailman/options/samba >>> >>> >> >> > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >-- Elias Pereira
Possibly Parallel Threads
- Import idmap database error on classicupgrade process
- Import idmap database error on classicupgrade process
- Import idmap database error on classicupgrade process
- Import idmap database error on classicupgrade process
- Import idmap database error on classicupgrade process