Re: [Samba] AD replication issue

Path	csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod
From	lingpanda101 via samba <samba@lists.samba.org>
Newsgroups	linux.samba
Subject	Re: [Samba] AD replication issue
Date	Mon, 13 Mar 2017 21:20:01 +0100
Message-ID	<tkEBH-5Mm-9@gated-at.bofh.it> (permalink)
References	<tkC6R-3QE-9@gated-at.bofh.it> <tkCJz-4on-7@gated-at.bofh.it> <tkDcB-4C4-11@gated-at.bofh.it> <tkEim-5lT-3@gated-at.bofh.it>
X-Original-To	Arthur Ramsey <arthur_ramsey@mediture.com>, samba@lists.samba.org
Dkim-Signature	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.samba.org; s=2954282; h=From:List-Id:Subject:Date:To; bh=JdF8ZlZ2euCl3e7nAs+MmaDVzoZfqIdCbUDe1ClB69Y=; b=XoS3qEXEsSErnl4OWpZRXFH0yuYC93bxsuUbCp8DSG8EB7gjgEhbzGpV08fDsAVdvzdz4uuKrM4t0M+BmKMhBCeRNl2qxI6XlG0TUm+M7t0FmJ8mXcVT/OQvoeu7P+VqR+uLxhRj/a4/2kpycSliVUEEeYd3p73qDiAKgtKGy7S8P4EtmOaCdjnvJQLM42bTuSvTe9xWR5Yo4OX0MLbLOIRy0ZYuivfugC1uqGOdLKwSxrHbDfXipbBJoEaetMX8xOQeAPU32yPaDvLB5Ajj3b8oIF0lslcmvCztC7KRmFIKWjXuaI6+MD1D1U7vIb1MmxiMbc9hPqOU4dltHhRmwA==;
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=LJY5r6YlGlEAhLNnJycWlpbj5/vqjanUPobOox9Mw00=; b=ja9Dw51olpV8dPaH5+Jc7f9kY21Xc8xHUgQ3QC/i0+KDCccb2xYUiHGBG9LY0+ngGP j/VVaXdBhZ7ixiUKxYVekwx9HPuaCgLzKF1R0mm47p45dTsCeEZtU8f7zZYj2DEPYeKj n32/lq9ytU89gePn59rcSBwHZD3iTN+e6Tw35ASy1LMth8mQ8I0YCnm8odSEMn1EH5Mw GvLk2PTwPMgU+opgjJh3OFp2ib/ngUIccBqVEhdwszrMIyjoVqIgAyYZRvtca9ZIQiMU qgWoX5wob1fQb2Y2Q9Xcmzw7zT0RXPcgFN4DAL7v8V/9CqWIsHUhADPOrI/jQYaScv+g zw8w==
X-Google-Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=LJY5r6YlGlEAhLNnJycWlpbj5/vqjanUPobOox9Mw00=; b=lMyUDoXEZgAAo5eOCM5EcgTjddorShnSKYNmLwrXCZaslqfgrS28Mhk83GPn9IkkQL cRcMi7dljSqxT2AQRizYM0InCrPuKZ9FEcuIN6j9vuOwvhxZ1Y49kLH5IgV12vY2TiWO 4n1S9HqiLYq51Uc4MtAnLV0zO//RqDEClj1IXV3tB1x2ltHXdFQqXAq6MuYOonu4We9N XNKQi8coY5JvSg9phCjpV4RbmGlwg31UDPhUvgv5xLBYTRlygza6AZw19KlCw1y0No4U 5PTa5YK3FqZMkGdqcKNRMcl9NyX52TtpJG1nmnPVvXlbmO5IKOJd1Y9MkAJsYOpZb/kp lEtw==
X-Gm-Message-State	AMke39lSWy9L/D2Odzpzsc+j5WjAipUI5dKULIyf+9rPLf38qaUCRwV2rXeF8ZJ24ndxKg==
X-Received	by 10.237.36.84 with SMTP id s20mr34145784qtc.271.1489435741014; Mon, 13 Mar 2017 13:09:01 -0700 (PDT)
User-Agent	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version	1.0
List-ID	General questions regarding Samba <samba.lists.samba.org>
List-Archive	<http://lists.samba.org/pipermail/samba/>
Reply-To	lingpanda101 <lingpanda101@gmail.com>
Content-Transfer-Encoding	7bit
Content-Type	text/plain; charset="utf-8"; Format="flowed"
Sender	robomod@news.nic.it
Approved	robomod@news.nic.it
Lines	181
Organization	linux.* mail to news gateway
X-Original-Date	Mon, 13 Mar 2017 16:08:59 -0400
X-Original-Message-ID	<92b2861d-03b7-43b2-2203-b1d46f846b61@gmail.com>
X-Original-References	<4a01100d-580b-2362-1525-6b96989c6fa6@mediture.com> <17012b30-e8d9-af46-3569-4f8d716a0760@mediture.com> <da3e45ee-3b77-3185-aa2f-ec54f3dc69eb@gmail.com> <cb6bdee2-4dd1-72b9-3392-12c8095e8c33@mediture.com>
X-Original-Sender	"samba" <samba-bounces@lists.samba.org>
Xref	csiph.com linux.samba:60340

Show key headers only | View raw

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@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@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


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

Back to linux.samba | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

[Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-13 18:40 +0100
  Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-13 19:20 +0100
    Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-13 19:50 +0100
      Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-13 21:00 +0100
        Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-13 21:20 +0100
        Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 01:00 +0100
          Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 12:20 +0100
          Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 12:30 +0100
            Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 15:10 +0100
          Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 15:20 +0100
            Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 15:40 +0100
              Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 16:10 +0100
                Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 16:30 +0100
                Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 17:20 +0100
                Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 18:30 +0100
                Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 18:30 +0100

csiph-web