similar to: [PATCH] Re: Failing replication

Hi Andrew, no offence. I was just wondering if I could get around this issue if I nuke my Samba DCs and start fresh? Regards, Alexander On 12. February 2020 at 07:07:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: I've been busy with other matters, including a serious issue with SCOPE_ONELEVEL searches ( https://gitlab.com/samba-team/samba/-/merge_requests/1125).

Thanks for your invaluable help. I proceeded as advised and installed the patched packages. Still an error though, debug.txt attached. Regards, Alexander On 10. February 2020 at 11:17:02, L.P.H. van Belle via samba (samba at lists.samba.org) wrote: Hai Alexander, I had a quick look, sorry for all the absence but im very buzzy atm with some office work. A quick howto for add this in the

Any update on this one? Is there anything I can do from my side? I?m prepared to nuke my Samba DC?s and start afresh if necessary. Currently I have three sites not picking up changes so I?m getting a bit anxious here? On 10. February 2020 at 19:52:02, Andrew Bartlett (abartlet at samba.org) wrote: Thanks. This is a different issue. I'll continue the thread on-list once I get to work.

Hi there, I would like to continue on this one. I applied the patch but am wondering which package it influences. If it is just the two mentioned than it did not fix the error. Regards, Alexander On 8. February 2020 at 09:46:11, Alexander Harm (alexander.harm at apfel-q.de) wrote: Hi Andrew, I applied your patch to the Debian packages of Louis. Do you happen to know in which package it

OK, found this post from Louis and this fixed it for me. https://lists.samba.org/archive/samba/2019-April/222278.html @Andrew: thanks so much for your time, effort and support the last days! Alexander On 3. March 2020 at 10:01:59, Alexander Harm (alexander.harm at apfel-q.de) wrote: That did the trick for manual replication via samba-tool drs replicate dc02 dc01 dc=ds,dc=example,dc=com

Exactly! On 3. March 2020 at 11:07:02, L.P.H. van Belle via samba (samba at lists.samba.org) wrote: Just to confirm this. Im guessing you use this part : > For the DsREplicatSync error, i would suggest these steps first. > DC2, change the resolv.conf, set DC1 first, then DC2, reboot. > Wait 5 min, now check replication again, if its ok, now you can change > the

Hi Andrew, I applied your patch to the Debian packages of Louis. Do you happen to know in which package it will end up? Tried samba and samba-dsdb-modules but the error remains the same. Alexander On 8. February 2020 at 01:38:25, Alexander Harm (alexander.harm at apfel-q.de) wrote: Hi Andrew, you can use my name if you want (Alexander Harm). I will try and build with your patch.

Thanks for the explanation. I have a few more sites which I will test today and feedback if a manual sync of the DNS partition solves the problem as well. Alexander On 3. March 2020 at 18:54:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: So, the reason this happens is if in the long time replication to this DC has been broken the local idea of the DNS layout for the other

That did the trick for manual replication via samba-tool drs replicate dc02 dc01 dc=ds,dc=example,dc=com --sync-all --local -d 9 However, if I run samba-tool drs showrepl it shows me a result 1326 (WERR_LOGON_FAILURE) and also samba-tool drs replicate dc02 dc01 dc=ds,dc=example,dc=com --full-sync fails with the same error. How can I fix this? On 3. March 2020 at 04:23:02, Andrew

Hi Andrew, you can use my name if you want (Alexander Harm). I will try and build with your patch. Alexander On 8. February 2020 at 00:30:02, Andrew Bartlett (abartlet at samba.org) wrote: Thanks. At this stage is looks like a bug in the repl_meta_data module. Try the attached patch. Can I name you in the bug and is there any affiliation (eg employer) you would like named?

Hi, as instructed I upgraded to ?Version 4.11.6-Debian?. Attached the new debug file. Regards, Alexander On 7. February 2020 at 10:01:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: I would fix that first, please run Samba 4.11. We have done much on replication since then and I'm keen to rule out things we have already fixed before digging into this further.

Hi Andrew, thanks for your feedback. What are my options now? Nuke the whole thing? Alexander On 24. February 2020 at 02:08:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: G'Day Alexander, This is looking trickier than I had hoped. I don't think the patch I included is the right approach, and I can't reproduce what I thought was the issue on master.

Thanks. At this stage is looks like a bug in the repl_meta_data module. Try the attached patch. Can I name you in the bug and is there any affiliation (eg employer) you would like named? I've filed a bug and will file a merge request once I have a test to confirm this. https://bugzilla.samba.org/show_bug.cgi?id=14272 Thanks! Andrew Bartlett On Fri, 2020-02-07 at 23:34 +0100, Alexander

Version 4.9.5-Debian On 7. February 2020 at 09:55:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: Much better. What Samba version is this? Andrew Bartlett On Fri, 2020-02-07 at 09:44 +0100, Alexander Harm via samba wrote: > Is this better? > > > > > On 7. February 2020 at 09:42:01, Andrew Bartlett via samba (samba at lists.samba.org) wrote:

Is this better? On 7. February 2020 at 09:42:01, Andrew Bartlett via samba (samba at lists.samba.org) wrote: I mean the final columns, not lines. There are long lines that seem to be cut off mid-word, rather than wrapped. Andrew Bartlett On Fri, 2020-02-07 at 09:14 +0100, Alexander Harm via samba wrote: > I did but these are the last lines. It ends with ?raise e? also in the

I did but these are the last lines. It ends with ?raise e? also in the shell. I also ran it on the other DCs and they all end with ?raise e?. Alexander On 7. February 2020 at 09:12:02, Andrew Bartlett (abartlet at samba.org) wrote: G'Day Alexander, It looks like you have copied the logs out of a terminal and lost the ends of the lines. Those have the critical (groan...) details of

G'Day Alexander, It looks like you have copied the logs out of a terminal and lost the ends of the lines. Those have the critical (groan...) details of what went wrong with the apparent 'critical extension' failure. Can you try and get those and I'll look at them tomorrow. Thanks! Andrew Bartlett On Fri, 2020-02-07 at 08:56 +0100, Alexander Harm via samba wrote: > Hi

Hey Andre,? Sure, we already on the latest Patch Level on Ubuntu with 2:4.13.17~dfsg-0ubuntu1.20.04.4 Installer, but the issue still exist.? The only way to resolve the issue and to make a login possible again, was the workaround in my previous mail.? The Windows clients are Windows 10 22H2 with all updates installed. We also doesn't have any special settings in smb.conf. If you have any

Hi Andrew, thanks for your reply. Find attached the output of the command. Looks like it fails on renaming an object to me. Regards, Alexander On 7. February 2020 at 08:50:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: On Wed, 2020-02-05 at 23:41 +0100, Alexander Harm via samba wrote: > Hello, > > we could need some help resolving a replication issue we

Strange, we had this working the last 6 months... only a week ago these errors started showing... So, no other idea than downgrading our Windows DC to 2016? Alexander On 6. February 2020 at 10:23:43, Rowland penny via samba (samba at lists.samba.org) wrote: On 05/02/2020 22:41, Alexander Harm via samba wrote: Hello, we could need some help resolving a replication issue we experience since one