search for: master_own

...gs) File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", line 390, in run infrastructureMaster = get_fsmo_roleowner(samdb, infrastructure_dn) File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", line 42, in get_fsmo_roleowner master_owner = res[0]["fSMORoleOwner"][0] sudo /usr/local/samba/bin/samba-tool dbcheck --fix --cross-ncs Checking 3527 objects ERROR: fSMORoleOwner not found for role CN=RID Manager$,CN=System,DC=cb,DC=cliffbells,DC=com Sieze role CN=RID Manager$,CN=System,DC=cb,DC=cliffbells,DC=com onto current D...

...eturn self.run(*args, **kwargs) File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", line 339, in run self.seize_role("rid", samdb, force) File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", line 255, in seize_role master_owner = get_fsmo_roleowner(samdb, m.dn) File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", line 42, in get_fsmo_roleowner master_owner = res[0]["fSMORoleOwner"][0] I found another thread about the issue: http://www.spinics.net/lists/samba/msg131164.html...

.../lib/python2.7/site-packages/samba/netcmd/fsmo.py", > line 390, in run > infrastructureMaster = get_fsmo_roleowner(samdb, infrastructure_dn) > File > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", > line 42, in get_fsmo_roleowner > master_owner = res[0]["fSMORoleOwner"][0] > > > sudo /usr/local/samba/bin/samba-tool dbcheck --fix --cross-ncs > Checking 3527 objects > ERROR: fSMORoleOwner not found for role CN=RID > Manager$,CN=System,DC=cb,DC=cliffbells,DC=com > Sieze role CN=RID Manager$,CN=System,DC=cb,D...

.../netcmd/fsmo.py", line >>>> 395, in run >>>> domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) >>>> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line >>>> 42, in get_fsmo_roleowner >>>> master_owner = res[0]["fSMORoleOwner"][0] >>>> >>>> Which concerns me. What could I do here to get me out of this >>>> pickle? Do I have to (re)seize FSMO responsibilities? I did run >>>> this on the DC that was the FSMO before all these shenanigans:...

...;> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 395, in run >> domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) >> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 42, in get_fsmo_roleowner >> master_owner = res[0]["fSMORoleOwner"][0] >> >> Which concerns me. What could I do here to get me out of this pickle? Do I have to (re)seize FSMO responsibilities? I did run this on the DC that was the FSMO before all these shenanigans: >> >> samba-tool fsmo seize --role=a...

...thon2.7/dist-packages/samba/netcmd/fsmo.py", line 395, in run >>>>> domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) >>>>> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 42, in get_fsmo_roleowner >>>>> master_owner = res[0]["fSMORoleOwner"][0] >>>>> >>>>> Which concerns me. What could I do here to get me out of this pickle? Do I have to (re)seize FSMO responsibilities? I did run this on the DC that was the FSMO before all these shenanigans: >>>>> >...

...return self.run(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 395, in run domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 42, in get_fsmo_roleowner master_owner = res[0]["fSMORoleOwner"][0] --------- Transfering or seizing the roles one by one, I can see that any operation involving the two "new" roles (domaindns and forestdns) is what actually breaks it. I don't think this is an upstream bug (is it?) Any ideas? Best regards, G...

...ile "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 395, in run >>> domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) >>> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 42, in get_fsmo_roleowner >>> master_owner = res[0]["fSMORoleOwner"][0] >>> >>> Which concerns me. What could I do here to get me out of this pickle? Do I have to (re)seize FSMO responsibilities? I did run this on the DC that was the FSMO before all these shenanigans: >>> >>> samba-tool fsm...

...return self.run(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 395, in run domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 42, in get_fsmo_roleowner master_owner = res[0]["fSMORoleOwner"][0] Which concerns me. What could I do here to get me out of this pickle? Do I have to (re)seize FSMO responsibilities? I did run this on the DC that was the FSMO before all these shenanigans: samba-tool fsmo seize --role=all This DC already has the 'rid...

...return self.run(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 396, in run domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 43, in get_fsmo_roleowner master_owner = res[0]["fSMORoleOwner"][0] root at gteste2:~# My samba config is: root at gteste2:~# cat /etc/samba/smb.conf # Global parameters [global] workgroup = TESTEAD realm = testead.gsurfnet.com netbios name = GTESTE2 interfaces = lo ens33 bind inter...

...return self.run(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 396, in run domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 43, in get_fsmo_roleowner master_owner = res[0]["fSMORoleOwner"][0] root at gteste2:~# root at gteste2:~# Thanks, Anderson Hoffmann 2016-07-07 16:50 GMT-03:00 Jason Waters <jason at geeknocity.com>: > what do you get when you do samba-tool fsmo show, > > also try samba-tool fsmo transfer --role=all -U...

...> "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", > line 339, in run > self.seize_role("rid", samdb, force) > File > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", > line 255, in seize_role > master_owner = get_fsmo_roleowner(samdb, m.dn) > File > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py", > line 42, in get_fsmo_roleowner > master_owner = res[0]["fSMORoleOwner"][0] > > I found another thread about the issue: > http://www.s...

I ran ldbsearch on my sam.ldb I searched for CBADC02, CBADC03, and TESTES (all VMs that fail to join domain), results are below: CBADC02 shows up a few times: # record 1906 dn: CN=CBADC02\0ADEL:de85228c-f92b-4d5d-9d6a-01c3f915dec9,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu$ objectClass: top objectClass: server instanceType: 4 whenCreated: 20160310044543.0Z uSNCreated: 4215

.../python2.7/dist-packages/samba/netcmd/fsmo.py", line 396, >> in run >> domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) >> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 43, >> in >> get_fsmo_roleowner >> master_owner = res[0]["fSMORoleOwner"][0] >> root at gteste2:~# >> >> >> My samba config is: >> >> root at gteste2:~# cat /etc/samba/smb.conf >> # Global parameters >> [global] >> workgroup = TESTEAD >> realm = testead.gsurf...

...gt;>> line 395, in run >>>>>> domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) >>>>>> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", >>>>>> line 42, in get_fsmo_roleowner >>>>>> master_owner = res[0]["fSMORoleOwner"][0] >>>>>> >>>>>> Which concerns me. What could I do here to get me out of this >>>>>> pickle? Do I have to (re)seize FSMO responsibilities? I did run >>>>>> this on the DC that was the FS...

...*kwargs) > File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 395, in run > domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) > File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 42, in get_fsmo_roleowner > master_owner = res[0]["fSMORoleOwner"][0] > > Which concerns me. What could I do here to get me out of this pickle? Do I have to (re)seize FSMO responsibilities? I did run this on the DC that was the FSMO before all these shenanigans: > > samba-tool fsmo seize --role=all Did you just e...

...thon2.7/dist-packages/samba/netcmd/fsmo.py", line 395, >> in run >> domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) >> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 42, >> in >> get_fsmo_roleowner >> master_owner = res[0]["fSMORoleOwner"][0] >> --------- >> >> Transfering or seizing the roles one by one, I can see that any operation >> involving the two "new" roles (domaindns and forestdns) is what actually >> breaks it. >> >> I don't think...

...rgs) File "/usr/local/samba/lib64/python2.7/site-packages/samba/netcmd/fsmo.py", line 396, in run domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) File "/usr/local/samba/lib64/python2.7/site-packages/samba/netcmd/fsmo.py", line 43, in get_fsmo_roleowner master_owner = res[0]["fSMORoleOwner"][0] I tried Samba 4.4.0rc5 with same result. I also tried this process on Samba-only AD domain and transfer worked correctly. What is the correct way to transfer DomainDnsZonesMasterRole and ForestDnsZonesMasterRole to Samba? Kind regards, Daniil Landau

....py", line 395, *>>>* in run *>>>* domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) *>>>* File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 42, *>>>* in *>>>* get_fsmo_roleowner *>>>* master_owner = res[0]["fSMORoleOwner"][0] *>>> * ---------* Follwing command returned a record, but without fSMORoleOwner $ /usr/local/samba/bin/ldbsearch -H /usr/local/samba/private/sam.ldb --cross-ncs --show-binary -b "CN=Infrastructure,DC=ForestDnsZones,DC=test,DC=local" fS...

...;/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 396, >> in run >> domaindnszonesMaster = get_fsmo_roleowner(samdb, domaindns_dn) >> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 43, >> in get_fsmo_roleowner >> master_owner = res[0]["fSMORoleOwner"][0] >> root at gteste2:~# >> root at gteste2:~# >> >> >> >> Thanks, >> Anderson Hoffmann >> >> >> >> >> 2016-07-07 16:50 GMT-03:00 Jason Waters <jason at geeknocity.com>: >> >...