Univention Bugzilla – Bug 27210
Temporärer objectSid Reject im S4 Connector eines UCS@school 3.0 DC Slaves
Last modified: 2016-09-01 06:18:57 CEST
Im connector-s4.log eines UCS@school 3.0 Samba 4 DC Slaves (UCS 3.0-1 errata72) findet sich ein Traceback folgender Art. Nach Abschluss der initialen Replikation ist dieser Rejects jedoch aufgelöst: 16.04.2012 22:03:31,153 LDAP (WARNING): Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/univention/s4connector/__init__.py", line 750, in __sync_file_from_ucs or (not old_dn and not self.sync_from_ucs(key, object, premapped_ucs_dn, old_dn, old))): File "/usr/lib/pymodules/python2.6/univention/s4connector/s4/__init__.py", line 2132, in sync_from_ucs self.lo_s4.lo.add_ext_s(compatible_modstring(object['dn']), compatible_addlist(addlist), serverctrls=self.serverctrls_for_add_and_modify) #FIXME encoding File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 180, in add_ext_s return self.result(msgid,all=1,timeout=self.timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 422, in result res_type,res_data,res_msgid = self.result2(msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 426, in result2 res_type, res_data, res_msgid, srv_ctrls = self.result3(msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 432, in result3 ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 96, in _ldap_call result = func(*args,**kwargs) ALREADY_EXISTS: {'info': '00002071: Entry already exists - ../ldb_tdb/ldb_index.c:1189: Failed to re-index objectSid in CN=master,OU=Domain Controllers,DC=arucs3s4x1,DC=qa - ../ldb _tdb/ldb_index.c:1121: unique index violation on objectSid in CN=master,OU=Domain Controllers,DC=arucs3s4x1,DC=qa', 'desc': 'Already exists'}
I found a similar issue but it my case the traceback still exists after the initial sync. I close this as duplicate of Bug #42207. *** This bug has been marked as a duplicate of bug 42207 ***