[Samba] Replication issue (maybe due to 4.7.0 bug?)

[Gaetan SLONGO]

Re, 


It seems OK now. I had to manualy remove the object in the destination DC. I did it using MMC and "change domain controler" to force acting on this DC. Then launching replicate doesnt thow any error anymore and ldapcmp is OK 


Thanks 

----- Mail original -----

De: "Gaetan SLONGO via samba" <samba at lists.samba.org> 
À: "Andrew Bartlett" <abartlet at samba.org> 
Cc: samba at lists.samba.org 
Envoyé: Jeudi 25 Janvier 2018 10:37:23 
Objet : Re: [Samba] Replication issue (maybe due to 4.7.0 bug?) 

Hi Andrew, 


I did the requested update, but still have the same issue when doin samba-tool drs replicate : 


On the destination server : 



[2018/01/25 10:34:04.404627, 1] ../source4/dsdb/repl/replicated_objects.c:894(dsdb_replicated_objects_commit) 
Failed to apply records: replmd_delete: Failed to modify object CN=DMZRODC-0,CN=Deleted Objects,DC=ads,DC=XXX,DC=be in delete - attribute 'msDS-RevealedUsers': no such attribute for delete on 'CN=DMZRODC-0,CN=Deleted Objects,DC=ads,DC=XXX,DC=be': No such attribute 




Executed command : 



[root at dc ~]# samba-tool drs replicate nas dc DC=ads,DC=XXX,DC=be --full-sync 
ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (58, 'WERR_BAD_NET_RESP') 
File "/usr/lib64/python2.7/site-packages/samba/netcmd/drs.py", line 386, in run 
drs_utils.sendDsReplicaSync(server_bind, server_bind_handle, source_dsa_guid, NC, req_options) 
File "/usr/lib64/python2.7/site-packages/samba/drs_utils.py", line 85, in sendDsReplicaSync 
raise drsException("DsReplicaSync failed %s" % estr) 



Any idea ? 


Thanks ! 




----- Mail original ----- 

De: "Andrew Bartlett" <abartlet at samba.org> 
À: "Gaetan SLONGO" <gslongo at it-optics.com> 
Cc: samba at lists.samba.org 
Envoyé: Mardi 19 Décembre 2017 19:16:07 
Objet : Re: [Samba] Replication issue (maybe due to 4.7.0 bug?) 

On Tue, 2017-12-19 at 11:00 +0100, Gaetan SLONGO wrote: 
> Hi Andrew, 
> 
> Thank you for your answer. The issue is in the source or destination ? 
> Because meanwhile I noticed the destination server was on 4.6.11 and not 4.7.3 as the source. What do you think about it ? 

Update the destination to 4.7.4 when this is released in a few days. 

I hope this helps, 

Andrew Bartlett 
-- 
Andrew Bartlett http://samba.org/~abartlet/ 
Authentication Developer, Samba Team http://samba.org 
Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba 




-- 




www.it-optics.com 

Gaëtan SLONGO | Head of Infrastructure Department 
Boulevard Initialis, 28 - 7000 Mons, BELGIUM 
Company : +32 (0)65 84 23 85 
Direct : +32 (0)65 32 85 88 
Fax : +32 (0)65 84 66 76 
Skype ID : gslongo.pro 
GPG Key : gslongo-gpg_key.asc 


- Please consider your environmental responsibility before printing this e-mail - 








-- 
To unsubscribe from this list go to the following URL and read the 
instructions: https://lists.samba.org/mailman/options/samba 



-- 




www.it-optics.com 
	
Gaëtan SLONGO | Head of Infrastructure Department 
Boulevard Initialis, 28 - 7000 Mons, BELGIUM 
Company : 	+32 (0)65 84 23 85 
Direct : 	+32 (0)65 32 85 88 
Fax : 	+32 (0)65 84 66 76 
Skype ID : 	gslongo.pro 
GPG Key : 	gslongo-gpg_key.asc 
	

- Please consider your environmental responsibility before printing this e-mail -