mj
2020-Nov-17 12:20 UTC
[Samba] changes on DC not replicated, while showrepl reports no issues
Hi, Again more data: The command samba-tool visualize reps seems to agree with the observed lack of replication from DC4 to DC3 & DC2:> RepsTo objects for DOMAIN > destination > ,--- CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com > |,-- CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com > source ||,- CN=DC4,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com > CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com 011 > CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com 101 > CN=DC4,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com --0 > > Data can get from source to destination in the indicated number of steps. > 0 means zero steps (it is the same DC) > 1 means a direct link > 2 means a transitive link involving two steps (i.e. one intermediate DC) > - means there is no connection, even through other DCsI hope formatting survives. ABove it says: "no connection" for DOMAIN from DC4 to DC3 / DC2. Even though there is nothing in between our DCs. No firewalling, all in the same subnet, etc. Anyone can explain more..? MJ
cn at brain-biotech.de
2020-Nov-17 13:12 UTC
[Samba] changes on DC not replicated, while showrepl reports no issues
Am 17.11.20 um 13:20 schrieb mj via samba:>> ,--- >> CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >> >> >> |,-- >> CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >> >> >> source ||,- >> CN=DC4,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >> >> CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >> 011 >> CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >> 101 >> CN=DC4,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >> --0 > > I hope formatting survives. > > ABove it says: "no connection" for DOMAIN from DC4 to DC3 / DC2. >We also have some Links with "no connection". So what I would like to know what other have here. Also we do not have any replication problems like the OP. ldapcmp says everything is fine. Regards Christian -- Dr. Christian Naumer Unit Head Bioprocess Development B.R.A.I.N Aktiengesellschaft Darmstaedter Str. 34-36, D-64673 Zwingenberg e-mail cn at brain-biotech.com, homepage www.brain-biotech.com fon +49-6251-9331-30 / fax +49-6251-9331-11 Subscribe to BRAIN's Newsletter: http://www.brain-biotech.com/de/newsletter Sitz der Gesellschaft: Zwingenberg/Bergstrasse Registergericht AG Darmstadt, HRB 24758 Vorstand: Adriaan Moelker (Vorstandsvorsitzender), Lukas Linnig Aufsichtsratsvorsitzender: Dr. Georg Kellinghusen
Rowland penny
2020-Nov-17 14:48 UTC
[Samba] changes on DC not replicated, while showrepl reports no issues
On 17/11/2020 13:12, cn--- via samba wrote:> Am 17.11.20 um 13:20 schrieb mj via samba: > >>> ,--- >>> CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >>> >>> |,-- >>> CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >>> >>> source ||,- >>> CN=DC4,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >>> >>> CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >>> 011 >>> CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >>> 101 >>> CN=DC4,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >>> --0 >> >> I hope formatting survives. >> >> ABove it says: "no connection" for DOMAIN from DC4 to DC3 / DC2. >> > > We also have some Links with "no connection". So what I would like to > know what other have here. > > Also we do not have any replication problems like the OP. ldapcmp says > everything is fine. > > Regards > > Christian >OK, after digging into the code, it seems that the 'Unknown invocation ID' lines are pretty meaning less, they come from here: ??????? try: ??????????? settings_dn = str(res[0]["distinguishedName"][0]) ??????????? prefix, dsa_dn = settings_dn.split(',', 1) ??????? except IndexError as e: ??????????? print("Unknown invocation ID %s" % inv_id, ????????????????? file=sys.stderr) ??????????? continue The Unknown invocation ID's appear to be artefacts of a DC being replaced and are pretty meaningless. Just about the only use I can see for printing it, is to scare the life out of users ? As you can see, right after printing the ID, it just continues to the next ID, perhaps the print part of the code needs removing ? It appears that the important lines are the last 5 Rowland
Seemingly Similar Threads
- How to configure samba domain member to use LDAPS instead of LDAP
- changes on DC not replicated, while showrepl reports no issues
- How to configure samba domain member to use LDAPS instead of LDAP
- Kerberos ticket lifetime
- Samba AD with multiple DC and multiple NICs