[Samba] Lost DC with FSMO-Rolls

Marc Muehlfeld mmuehlfeld at samba.org
Wed Nov 5 11:21:46 MST 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Stefan,

Am 05.11.2014 um 17:54 schrieb Stefan Kania:
> But it faild foir the role "naming":
> 
> root at SVL-V-AD1:~# samba-tool fsmo seize --role=naming Attempting 
> transfer... ERROR(ldb): uncaught exception - Failed FSMO transfer:
>  NT_STATUS_CONNECTION_REFUSED File 
> "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 
> 175, in _run return self.run(*args, **kwargs) File 
> "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 160, 
> in run self.seize_role(role, samdb, force) File 
> "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 126, 
> in seize_role transfer_role(self.outf, role, samdb) File 
> "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 53, 
> in transfer_role samdb.modify(m)


Which version of Samba are you running? There was a time, we had bugs
in the FSMO role seizing. (e. g.
https://bugzilla.samba.org/show_bug.cgi?id=9461).

I don't remember, which version the patches were in included. But it
was fixed in 4.0 and 4.1. So switching to the latest version, maybe
solves your problem (if you're not already using it).


Regards,
Marc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUWmqxAAoJEFNERvHO3m51wNMIAL2y/BxnKQeCm4+HktvLipuH
bs2MfS8BE6TFQgET1E974/VWzfNV7auulx5UEN9vfF0QZP9t6g6Iav14G6f4hWgg
x7WwZzw4kCrQJlhLrT6vKEI5ry6Xr/fais7zu76OkqeztEeJ6yEp3yfVjOFd1Gm1
/AFH3lhoz6UatyHlkK+9CXWbqzucFQDuUSjSuOYMsXqkrwH2/BdSbSYQsayMqeBV
gEz74K4oXNn5j2Q4tUBs4DqG1jSYWlzlaS5J641cLpq2BTL0iZaaamT8tZw6zYxM
wRZq708GTvadHt6+12fzq/0bl2DPGbdGA2ENXoFrrQOcqs+vOeIrRRsOJZlQytA=
=nimf
-----END PGP SIGNATURE-----


More information about the samba mailing list