Hi,
I tried to replicate two DC's (on test setup) with "--full-sync"
option
but fails with error message below. I tried "--full-sync" because I
wonder if it has any effect on some diverged entries reported
by "samba-tool ldapcmp".
# samba-tool drs replicate dc1 dc2 --full-sync DC=samdom,DC=com
ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to
dc1
failed - drsException: DRS connection to dc1 failed: (3221225653,
'{Device Timeout} The specified I/O operation on %hs was not completed
before the time-out period expired.') File
"/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line 44, in
drsuapi_connect (ctx.drsuapi, ctx.drsuapi_handle,
ctx.bind_supported_extensions) = drs_utils.drsuapi_connect(ctx.server,
ctx.lp, ctx.creds) File
"/usr/lib/python2.7/dist-packages/samba/drs_utils.py", line 58, in
drsuapi_connect raise drsException("DRS connection to %s failed: %s" %
(server, e))
Same command without "--full-sync" option doesn't give this error.
Both DC's Samba 4.8.4
Ubuntu 18.0.4
BIND9_DLZ
---
Taner Tas
On Fri, 2018-08-31 at 11:40 +0300, Taner Tas via samba wrote:> Hi, > > I tried to replicate two DC's (on test setup) with "--full-sync" option > but fails with error message below. I tried "--full-sync" because I > wonder if it has any effect on some diverged entries reported > by "samba-tool ldapcmp". > > # samba-tool drs replicate dc1 dc2 --full-sync DC=samdom,DC=com > > ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc1 > failed - drsException: DRS connection to dc1 failed: (3221225653, > '{Device Timeout} The specified I/O operation on %hs was not completed > before the time-out period expired.') File > "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line 44, in > drsuapi_connect (ctx.drsuapi, ctx.drsuapi_handle, > ctx.bind_supported_extensions) = drs_utils.drsuapi_connect(ctx.server, > ctx.lp, ctx.creds) File > "/usr/lib/python2.7/dist-packages/samba/drs_utils.py", line 58, in > drsuapi_connect raise drsException("DRS connection to %s failed: %s" % > (server, e)) > > Same command without "--full-sync" option doesn't give this error.Try adding --local This will do the work in the local python process and so might avoid one of the steps in between timing out. Andrew Bartlett> Both DC's Samba 4.8.4 > Ubuntu 18.0.4 > BIND9_DLZ > > --- > Taner Tas >-- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
On Fri, 31 Aug 2018 20:42:56 +1200 Andrew Bartlett via samba <samba at lists.samba.org> wrote:> On Fri, 2018-08-31 at 11:40 +0300, Taner Tas via samba wrote: > > Hi, > > > > I tried to replicate two DC's (on test setup) with "--full-sync" > > option but fails with error message below. I tried "--full-sync" > > because I wonder if it has any effect on some diverged entries > > reported by "samba-tool ldapcmp".It might also help if you could tell us what the 'diverged entries' are. Rowland
Fri, 31 Aug 2018 20:42:56 +1200 tarihinde Andrew Bartlett <abartlet at samba.org> yazdı:> Try adding --local > > This will do the work in the local python process and so might avoid > one of the steps in between timing out. > > Andrew BartlettThanks. It worked. I think "--local" must have used on target DC as what ouput of command tells about what have done. I want get DC1 full-synced so I give this command on DC1 # samba-tool drs replicate dc1 dc2 --full-sync --local DC=samdom,DC=com Full Replication of all ***** objects and ***** links from dc2 to tdb:///var/lib/samba/private/sam.ldb was successful. --- Taner Tas