On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote:> Upgraded to 4.6.0 on all nodes. Still seeing the same issue. > > If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't > replicate. If I create it on vsc-dc01 (PDC emulator) then it does > replicate. > > On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >> >> I believe the problem is a lack of outbound replication for non PDC >> emulator DCs. You'll notice isn't even trying because last >> successful was epoch (never) yet there are no errors. Inbound >> replication for this DC seems fine. >> >> [root at vsc-dc02 ~]# samba-tool drs showrepl >> [...]==== OUTBOUND NEIGHBORS ===>> >> DC=DomainDnsZones,DC=mediture,DC=dom >> aws\AWS-DC01 via RPC >> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >> Last attempt@ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=DomainDnsZones,DC=mediture,DC=dom >> epo\EPO-DC01 via RPC >> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >> Last attempt@ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=DomainDnsZones,DC=mediture,DC=dom >> vsc\DC01 via RPC >> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=ForestDnsZones,DC=mediture,DC=dom >> aws\AWS-DC01 via RPC >> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=ForestDnsZones,DC=mediture,DC=dom >> epo\EPO-DC01 via RPC >> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=ForestDnsZones,DC=mediture,DC=dom >> vsc\DC01 via RPC >> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=mediture,DC=dom >> epo\EPO-DC01 via RPC >> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=mediture,DC=dom >> aws\AWS-DC01 via RPC >> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=mediture,DC=dom >> vsc\DC01 via RPC >> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> CN=Schema,CN=Configuration,DC=mediture,DC=dom >> aws\AWS-DC01 via RPC >> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> CN=Schema,CN=Configuration,DC=mediture,DC=dom >> epo\EPO-DC01 via RPC >> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> CN=Schema,CN=Configuration,DC=mediture,DC=dom >> vsc\DC01 via RPC >> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> CN=Configuration,DC=mediture,DC=dom >> aws\AWS-DC01 via RPC >> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> CN=Configuration,DC=mediture,DC=dom >> epo\EPO-DC01 via RPC >> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >> Last attempt @NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> CN=Configuration,DC=mediture,DC=dom >> vsc\DC01 via RPC >> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> ==== KCC CONNECTION OBJECTS ===>> >> Connection -- >> Connection name: 42b18310-000a-498f-911f-d57443724681 >> Enabled : TRUE >> Server DNS name : aws-dc01.mediture.dom >> Server DN name : CN=NTDS >> Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom >> TransportType: RPC >> options: 0x00000001 >> Warning: No NC replicated for Connection! >> Connection -- >> Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814 >> Enabled : TRUE >> Server DNS name : epo-dc01.mediture.dom >> Server DN name : CN=NTDS >> Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom >> TransportType: RPC >> options: 0x00000001 >> Warning: No NC replicated for Connection! >> Connection -- >> Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c >> Enabled : TRUE >> Server DNS name : dc01.mediture.dom >> Server DN name : CN=NTDS >> Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom >> TransportType: RPC >> options: 0x00000001 >> Warning: No NC replicated for Connection! >> -- >> Arthur Ramsey >> System Administrator >> Mediture >> arthur_ramsey at mediture.com >> 952.400.0323 >Not sure exactly what your issue is but the NTTIME(0) is a bug. -- - James
That bug is reported? Do you have a link? You're saying it is just an issue with the logging or am I correct that this indicates an outbound replication isn't trying. On 03/13/2017 01:45 PM, lingpanda101 via samba wrote:> On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: >> Upgraded to 4.6.0 on all nodes. Still seeing the same issue. >> >> If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it >> doesn't replicate. If I create it on vsc-dc01 (PDC emulator) then it >> does replicate. >> >> On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >>> >>> I believe the problem is a lack of outbound replication for non PDC >>> emulator DCs. You'll notice isn't even trying because last >>> successful was epoch (never) yet there are no errors. Inbound >>> replication for this DC seems fine. >>> >>> [root at vsc-dc02 ~]# samba-tool drs showrepl >>> [...]==== OUTBOUND NEIGHBORS ===>>> >>> DC=DomainDnsZones,DC=mediture,DC=dom >>> aws\AWS-DC01 via RPC >>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>> Last attempt@ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=DomainDnsZones,DC=mediture,DC=dom >>> epo\EPO-DC01 via RPC >>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>> Last attempt@ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=DomainDnsZones,DC=mediture,DC=dom >>> vsc\DC01 via RPC >>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=ForestDnsZones,DC=mediture,DC=dom >>> aws\AWS-DC01 via RPC >>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=ForestDnsZones,DC=mediture,DC=dom >>> epo\EPO-DC01 via RPC >>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=ForestDnsZones,DC=mediture,DC=dom >>> vsc\DC01 via RPC >>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=mediture,DC=dom >>> epo\EPO-DC01 via RPC >>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=mediture,DC=dom >>> aws\AWS-DC01 via RPC >>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=mediture,DC=dom >>> vsc\DC01 via RPC >>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> CN=Schema,CN=Configuration,DC=mediture,DC=dom >>> aws\AWS-DC01 via RPC >>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> CN=Schema,CN=Configuration,DC=mediture,DC=dom >>> epo\EPO-DC01 via RPC >>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> CN=Schema,CN=Configuration,DC=mediture,DC=dom >>> vsc\DC01 via RPC >>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> CN=Configuration,DC=mediture,DC=dom >>> aws\AWS-DC01 via RPC >>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> CN=Configuration,DC=mediture,DC=dom >>> epo\EPO-DC01 via RPC >>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>> Last attempt @NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> CN=Configuration,DC=mediture,DC=dom >>> vsc\DC01 via RPC >>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> ==== KCC CONNECTION OBJECTS ===>>> >>> Connection -- >>> Connection name: 42b18310-000a-498f-911f-d57443724681 >>> Enabled : TRUE >>> Server DNS name : aws-dc01.mediture.dom >>> Server DN name : CN=NTDS >>> Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom >>> TransportType: RPC >>> options: 0x00000001 >>> Warning: No NC replicated for Connection! >>> Connection -- >>> Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814 >>> Enabled : TRUE >>> Server DNS name : epo-dc01.mediture.dom >>> Server DN name : CN=NTDS >>> Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom >>> TransportType: RPC >>> options: 0x00000001 >>> Warning: No NC replicated for Connection! >>> Connection -- >>> Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c >>> Enabled : TRUE >>> Server DNS name : dc01.mediture.dom >>> Server DN name : CN=NTDS >>> Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom >>> TransportType: RPC >>> options: 0x00000001 >>> Warning: No NC replicated for Connection! >>> -- >>> Arthur Ramsey >>> System Administrator >>> Mediture >>> arthur_ramsey at mediture.com >>> 952.400.0323 >> > > Not sure exactly what your issue is but the NTTIME(0) is a bug. >-- Arthur Ramsey System Administrator Mediture arthur_ramsey at mediture.com 952.400.0323 This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at privacyofficer at mediture.com.
On 3/13/2017 3:48 PM, Arthur Ramsey wrote:> That bug is reported? Do you have a link? You're saying it is just > an issue with the logging or am I correct that this indicates an > outbound replication isn't trying. > > On 03/13/2017 01:45 PM, lingpanda101 via samba wrote: >> On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: >>> Upgraded to 4.6.0 on all nodes. Still seeing the same issue. >>> >>> If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it >>> doesn't replicate. If I create it on vsc-dc01 (PDC emulator) then >>> it does replicate. >>> >>> On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >>>> >>>> I believe the problem is a lack of outbound replication for non PDC >>>> emulator DCs. You'll notice isn't even trying because last >>>> successful was epoch (never) yet there are no errors. Inbound >>>> replication for this DC seems fine. >>>> >>>> [root at vsc-dc02 ~]# samba-tool drs showrepl >>>> [...]==== OUTBOUND NEIGHBORS ===>>>> >>>> DC=DomainDnsZones,DC=mediture,DC=dom >>>> aws\AWS-DC01 via RPC >>>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>>> Last attempt@ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> DC=DomainDnsZones,DC=mediture,DC=dom >>>> epo\EPO-DC01 via RPC >>>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>>> Last attempt@ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> DC=DomainDnsZones,DC=mediture,DC=dom >>>> vsc\DC01 via RPC >>>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> DC=ForestDnsZones,DC=mediture,DC=dom >>>> aws\AWS-DC01 via RPC >>>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> DC=ForestDnsZones,DC=mediture,DC=dom >>>> epo\EPO-DC01 via RPC >>>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> DC=ForestDnsZones,DC=mediture,DC=dom >>>> vsc\DC01 via RPC >>>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> DC=mediture,DC=dom >>>> epo\EPO-DC01 via RPC >>>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> DC=mediture,DC=dom >>>> aws\AWS-DC01 via RPC >>>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> DC=mediture,DC=dom >>>> vsc\DC01 via RPC >>>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> CN=Schema,CN=Configuration,DC=mediture,DC=dom >>>> aws\AWS-DC01 via RPC >>>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> CN=Schema,CN=Configuration,DC=mediture,DC=dom >>>> epo\EPO-DC01 via RPC >>>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> CN=Schema,CN=Configuration,DC=mediture,DC=dom >>>> vsc\DC01 via RPC >>>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> CN=Configuration,DC=mediture,DC=dom >>>> aws\AWS-DC01 via RPC >>>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> CN=Configuration,DC=mediture,DC=dom >>>> epo\EPO-DC01 via RPC >>>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>>> Last attempt @NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> CN=Configuration,DC=mediture,DC=dom >>>> vsc\DC01 via RPC >>>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>>> Last attempt @ NTTIME(0) was successful >>>> 0 consecutive failure(s). >>>> Last success @ NTTIME(0) >>>> >>>> ==== KCC CONNECTION OBJECTS ===>>>> >>>> Connection -- >>>> Connection name: 42b18310-000a-498f-911f-d57443724681 >>>> Enabled : TRUE >>>> Server DNS name : aws-dc01.mediture.dom >>>> Server DN name : CN=NTDS >>>> Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom >>>> TransportType: RPC >>>> options: 0x00000001 >>>> Warning: No NC replicated for Connection! >>>> Connection -- >>>> Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814 >>>> Enabled : TRUE >>>> Server DNS name : epo-dc01.mediture.dom >>>> Server DN name : CN=NTDS >>>> Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom >>>> TransportType: RPC >>>> options: 0x00000001 >>>> Warning: No NC replicated for Connection! >>>> Connection -- >>>> Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c >>>> Enabled : TRUE >>>> Server DNS name : dc01.mediture.dom >>>> Server DN name : CN=NTDS >>>> Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom >>>> TransportType: RPC >>>> options: 0x00000001 >>>> Warning: No NC replicated for Connection! >>>> -- >>>> Arthur Ramsey >>>> System Administrator >>>> Mediture >>>> arthur_ramsey at mediture.com >>>> 952.400.0323 >>> >> >> Not sure exactly what your issue is but the NTTIME(0) is a bug. >> >I can't recall if it was reported on Bugzilla. Here is the thread where Garming mentioned it as such. https://lists.samba.org/archive/samba/2016-September/203160.html -- - James
I forgot to associate inter-site links (all using default), which fixed
a lot though I'm still having an issue.
* vsc site
o vsc-dc01
o vsc-dc02
* aws site
o aws-dc01
* epo site
o epo-dc01
* vsc-dc01 => anywhere: OK
* vsc-dc02 => anywhere: not replicating
* aws-dc01 => anywhere: OK
* epo-dc01 => anywhere: OK
I've tried with samba_kcc = false and true.
Thanks,
Arthur
This e-mail and any attachments may contain CONFIDENTIAL information, including
PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or
disclosure of this information is STRICTLY PROHIBITED; you are requested to
delete this e-mail and any attachments, notify the sender immediately, and
notify the Mediture Privacy Officer at privacyofficer at mediture.com.