The Samba-Bugzilla – Bug 9614
windows command: repadmin /showvector /latency produces wrong timestamps with samba4 replication
Last modified: 2015-07-31 08:21:02 UTC
Samba 4.0 server joined to windows AD server (server 2003 functional level). Replication seems to be working between servers, "repadmin /showrepl" shows all well, as does "samba-tool drs showrepl".
However in the Windows event log for Directory Service I am getting:
Log Name: Directory Service
Date: 25/01/2013 11:54:37
Event ID: 1864
Task Category: Replication
User: ANONYMOUS LOGON
This is the replication status for the following directory partition on this directory server.
This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals.
More than 24 hours:
More than a week:
More than one month:
More than two months:
More than a tombstone lifetime:
Tombstone lifetime (days):
Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
To identify the directory servers by name, use the dcdiag.exe tool.
You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
If I execute "repadmin /showvector /latency dc=inview,dc=local"
I get :
94ec3f8c-dae2-47ef-8bea-50b7e81801a9 @ USN 4703900 @ Time 2012-10-05 13:57:27
Default-First-Site-Name\INVIEW-DC1 @ USN 403333 @ Time 2013-01-29 14:06:16
Default-First-Site-Name\INVIEW-DC2 @ USN 8886 @ Time 4232-19-00 10:00:00
82e59ee0-222c-4a28-82c5-d926918aa49e @ USN 8203 @ Time 4232-19-00 01:00:00
inview-dc2 is the samba4 box server, and the other lines represent servers which have been removed using metadata cleanup process (one of which was a Samba4 server).
Both Samba 4 servers have crazy date stamps, yr 4232.
I assume that the wrong datestamp is causing the event id 1864.
The same situation has occurred in my test environment.