Der s4slave hat gegen den s4-backup gejoined, wie man im join.log sieht: ============================================== Configure 96univention-samba4.inst Thu Nov 14 11:51:47 CET 2013 [...] Finding a writeable DC for domain 'ucs.local' Found DC s4-backup.ucs.local ============================================== connector-s4.log: ===================================================================================================================================== 14.11.2013 11:58:08,150 LDAP (PROCESS): sync from ucs: [ dc] [ modify] cn=s4slave,ou=domain controllers,dc=ucs,dc=local 14.11.2013 11:58:09,254 LDAP (PROCESS): sync to ucs: [ dc] [ modify] cn=s4slave,cn=dc,cn=computers,dc=ucs,dc=local 14.11.2013 11:58:15,460 LDAP (PROCESS): sync from ucs: [ dc] [ modify] cn=s4slave,ou=domain controllers,dc=ucs,dc=local 14.11.2013 11:59:57,610 LDAP (PROCESS): Ignore conflicted object: CN=S4SLAVE\0ACNF:64dbddd7-0a8e-441a-8934-fca82e75322d,OU=Domain Controllers,DC=ucs,DC=local 14.11.2013 11:59:57,615 LDAP (PROCESS): sync to ucs: [ user] [ add] uid=dns-s4-backup,cn=users,dc=ucs,dc=local 14.11.2013 11:59:57,681 LDAP (WARNING): __set_values: The attributes for lastname have not been removed as it represents a mandatory attribute 14.11.2013 11:59:58,400 LDAP (PROCESS): sync to ucs: [ dc] [ modify] cn=s4-backup,cn=dc,cn=computers,dc=ucs,dc=local 14.11.2013 11:59:59,557 LDAP (PROCESS): Ignore conflicted object: CN=S4SLAVE\0ACNF:64dbddd7-0a8e-441a-8934-fca82e75322d,OU=Domain Controllers,DC=ucs,DC=local 14.11.2013 12:00:04,611 LDAP (PROCESS): sync from ucs: [ user] [ add] cn=dns-s4-backup,cn=users,dc=ucs,dc=local 14.11.2013 12:00:04,805 LDAP (PROCESS): sync from ucs: [ group] [ modify] cn=domain users,cn=groups,dc=ucs,dc=local 14.11.2013 12:00:04,843 LDAP (PROCESS): Drop /var/lib/univention-connector/s4/1384426798.271264. The DN uid=dns-s4-backup,cn=users,dc=ucs,dc=local will synced later 14.11.2013 12:00:04,867 LDAP (PROCESS): sync from ucs: [ user] [ modify] cn=dns-s4-backup,cn=users,dc=ucs,dc=local 14.11.2013 12:00:04,994 LDAP (PROCESS): sync from ucs: [ dc] [ modify] cn=s4-backup,ou=domain controllers,dc=ucs,dc=local 14.11.2013 12:00:06,124 LDAP (PROCESS): sync to ucs: [ user] [ modify] uid=dns-s4-backup,cn=users,dc=ucs,dc=local 14.11.2013 12:00:12,693 LDAP (WARNING): encode_s4_object: encode attrib repsTo failed, ignored! 14.11.2013 12:00:12,699 LDAP (PROCESS): Ignore conflicted object: CN=S4SLAVE\0ACNF:64dbddd7-0a8e-441a-8934-fca82e75322d,OU=Domain Controllers,DC=ucs,DC=local 14.11.2013 12:00:17,763 LDAP (PROCESS): Ignore conflicted object: CN=S4SLAVE\0ACNF:64dbddd7-0a8e-441a-8934-fca82e75322d,OU=Domain Controllers,DC=ucs,DC=local 14.11.2013 12:00:22,820 LDAP (PROCESS): sync to ucs: [ user] [ add] uid=dns-s4slave,cn=users,dc=ucs,dc=local 14.11.2013 12:00:22,888 LDAP (WARNING): __set_values: The attributes for lastname have not been removed as it represents a mandatory attribute 14.11.2013 12:00:29,973 LDAP (PROCESS): sync from ucs: [ user] [ add] cn=dns-s4slave,cn=users,dc=ucs,dc=local 14.11.2013 12:00:30,93 LDAP (PROCESS): sync from ucs: [ group] [ modify] cn=domain users,cn=groups,dc=ucs,dc=local ===================================================================================================================================== # Timestamps des Objekts im s4master sam.ldb, das von s4-backup stammt (erkennbar an der originating_invocation_id aus replPropertyMetaData): dn: CN=S4SLAVE\0ACNF:64dbddd7-0a8e-441a-8934-fca82e75322d,OU=Domain Controllers,DC=ucs,DC=local whenCreated: 20131114105158.0Z ## eine Sekunde zuvor wurde 96univention-samba4.inst gestartet, Objekt wurde auf s4-backup im Samba4 angelegt. uSNCreated: 3912 whenChanged: 20131114110010.0Z ## Timestamps sind UTC, also ist das hier 12:01 local time uSNChanged: 3934 # Timestamps des Objekts im s4master sam.ldb, das von s4master stammt: dn: CN=s4slave,OU=Domain Controllers,DC=ucs,DC=local whenCreated: 20131114105808.0Z ## exakt zu diesem Zeitpunkt kam das Objekt per S4-Connector aus dem LDAP auf dem Master Samba4 an. uSNCreated: 3909 whenChanged: 20131114120956.0Z uSNChanged: 3980 Interessant ist, dass der S4-Connector auf dem Master das Rechnerobjekt des DC Slave später aus UCS LDAP nach Samba4 schreibt, nachdem es schon im Samba4 auf dem S4-Backup angelegt worden ist.