samba - Mar 2019 - replication fails

Am 13.03.19 um 12:49 schrieb Rowland Penny via samba:
>> Should /etc/hosts contain pointers to own FQDN or not? To DCs?
>>
> 
> /etc/hosts should contain a line that points 127.0.0.1 to localhost and
> a line that points the DC's ipaddress to its FQDN and shorthostname
> 
> EXAMPLE:
> 
> 127.0.0.1 localhost
> 192.168.0.6 dc4.samdom.example.com dc4
> 
> There will probably be ipv6 lines as well, anything else isn't really
> needed, but I suppose you could add any other DC's info.
Thank you. The clearer the better (or so).

DC2 is set up like that, but still ~500 replication failures.

Off for some food and water now ... I hope I get it later.

thanks all

Am 13.03.19 um 12:53 schrieb Stefan G. Weichinger via samba:
> DC2 is set up like that, but still ~500 replication failures.
getting lost more and more somehow

Now on DC1 I get:

# samba-tool drs showrepl
Default-First-Site-Name\DC
DSA Options: 0x00000001
DSA object GUID: e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4
DSA invocationId: f26592be-46f6-47f2-bf58-9fac99a02e92

==== INBOUND NEIGHBORS ===
DC=ForestDnsZones,DC=mytld,DC=at
	Default-First-Site-Name\PRE01SVDEB03 via RPC
		DSA object GUID: dab06c8b-ec8a-47c8-b059-d979949d88c0
		Last attempt @ Wed Mar 13 13:19:28 2019 CET failed, result 2
(WERR_FILE_NOT_FOUND)
		7 consecutive failure(s).
		Last success @ Wed Mar 13 12:48:09 2019 CET


My DC1 is named "PRE01SVDEB02"
and DC2 = "PRE01SVDEB03"

Am 13.03.19 um 13:25 schrieb Stefan G. Weichinger via samba:
> My DC1 is named "PRE01SVDEB02"
> and DC2 = "PRE01SVDEB03"
checked for resolv.conf and DNS-pointers again. made sure that all 3
FQDNs (2 DCs, one DM) resolve from the servers.

showrepl is happy again on DC1, but still fails on/to DC2

hm

manual replicate: no progress or success visible (either from DC1 or DC2)

-

compared smb.confs ... raised log level on DC2 and see this in log.samba
now:

# tail -f log.samba
[2019/03/13 13:55:19.905976,  0]
../source4/smbd/server.c:674(binary_smbd_main)
  binary_smbd_main: samba: using 'standard' process model
[2019/03/13 13:55:34.957655,  1]
../source4/dsdb/kcc/garbage_collect_tombstones.c:68(garbage_collect_tombstones_part)
  Doing a full scan on DC=ForestDnsZones,DC=mytld,DC=at and looking for
deleted objects
[2019/03/13 13:55:34.958862,  1]
../source4/dsdb/kcc/garbage_collect_tombstones.c:68(garbage_collect_tombstones_part)
  Doing a full scan on DC=DomainDnsZones,DC=mytld,DC=at and looking for
deleted objects
[2019/03/13 13:55:34.960768,  1]
../source4/dsdb/kcc/garbage_collect_tombstones.c:68(garbage_collect_tombstones_part)
  Doing a full scan on DC=mytld,DC=at and looking for deleted objects
[2019/03/13 13:55:34.968403,  1]
../source4/dsdb/kcc/garbage_collect_tombstones.c:68(garbage_collect_tombstones_part)
  Doing a full scan on CN=Configuration,DC=mytld,DC=at and looking for
deleted objects

...


maybe I just have to wait now?

greets from the drama queen
Stefan