[Samba] Initial replication halts with "The handle is invalid." (msDS-NC-Replica-Locations corrupted?)

[Adam Tauno Williams]

Quoting Rowland Penny via samba <samba at lists.samba.org>:
>> samba-tool's dbcheck finds only two errors in cn=Configuration, but it
>> does not repair them.  These appear to be references to an original,
>> long since demoted, DC.  But these values appear in neither the
>> results of an ldbsearch or via ADSI edit.
> Have a look at this bug report:
> https://bugzilla.samba.org/show_bug.cgi?id=12385

Thanks.  I have checked out master and built it [**1];  Bug#12297  
[**2] indicates I can run samba-tool from the build of the checkout.   
I assume tombstone expunge, even for CN=Configuration, runs against  
sam.ldb???  So the correct syntax is -

[ADC28 samba]# bin/samba-tool domain tombstones expunge -H  
/var/lib/samba/private/sam.ldb

    ???

[**1]
   git clone https://git.samba.org/samba.git
   cd samba/
   yum install gcc libacl-devel python-devel gnutls-devel openldap-devel
   ./configure
   make
   ls bin/samba-tool

[**2]
   https://bugzilla.samba.org/show_bug.cgi?id=12297

>> [root at larkin27 ~]#  ldbsearch --cross-ncs -H
>> /var/lib/samba/private/sam.ldb -b
>> "CN=Configuration,DC=micore,DC=US"  - s sub
>> CN=3ad6381a-9725-4e28-8157-a5a3fde68a43 msDS-NC-Replica-Locations
>> # record 1
>> dn: CN=3ad6381a-9725-4e28-8157-
>> a5a3fde68a43,CN=Partitions,CN=Configuration,DC=micore,DC=us
>> msDS-NC-
>> Replica-Locations: CN=NTDS Settings,CN=LARKIN26,CN=Servers,CN=Default-
>>  First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us
>> msDS-NC-Replica-Locations: CN=NTDS
>> Settings,CN=LARKIN28,CN=Servers,CN=Default-
>> First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us
>> msDS-NC-Replica-Locations: CN=NTDS
>> Settings,CN=LARKIN27,CN=Servers,CN=Default-
>> First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us
>>
>>
>> [root at larkin27 ~]# samba-tool dbcheck --cross-ncs --fix --yes
>> Checking 8411 objects
>> ERROR: no target object found for GUID component for msDS-NC-Replica-
>> Locations in object CN=3ad6381a-9725-4e28-8157-
>> a5a3fde68a43,CN=Partitions,CN=Configuration,DC=micore,DC=us -
>> <GUID=7d3f95a5cdfa1246b1fb2fcd16e5f877>;<RMD_ADDTIME=130000065100000000
>> >;<RMD_CHANGETIME=130000065100000000>;<RMD_FLAGS=0>;<RMD_INVOCID=01db57
>> fd8d4ddd469aee9cbd36abb3e1>;<RMD_LOCAL_USN=5160>;<RMD_ORIGINATING_USN=3
>> 630>;<RMD_VERSION=0>;CN=NTDS Settings,CN=BARBEL,CN=Servers,CN=Default-
>> First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us
>> Not removing dangling forward link
>> ERROR: no target object found for GUID component for msDS-NC-Replica-
>> Locations in object CN=55b4d7f1-b1b1-4843-ae00-
>> 7908adf44ffa,CN=Partitions,CN=Configuration,DC=micore,DC=us -
>> <GUID=7d3f95a5cdfa1246b1fb2fcd16e5f877>;<RMD_ADDTIME=130000065100000000
>> >;<RMD_CHANGETIME=130000065100000000>;<RMD_FLAGS=0>;<RMD_INVOCID=01db57
>> fd8d4ddd469aee9cbd36abb3e1>;<RMD_LOCAL_USN=5134>;<RMD_ORIGINATING_USN=3
>> 629>;<RMD_VERSION=0>;CN=NTDS Settings,CN=BARBEL,CN=Servers,CN=Default-
>> First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us
>> Not removing dangling forward link