Univention Bugzilla – Bug 37555
traceback in connector-s4.log when syncing locked objects (saving as rejected)
Last modified: 2019-12-03 10:13:14 CET
Found the following tracebacks in one of my envs in /var/log/univention/connector-s4.log: 25.11.2014 21:26:23,906 LDAP (PROCESS): sync from ucs: Resync rejected file: /var/lib/univention-connector/s4/1416013819.020017 25.11.2014 21:26:23,909 LDAP (PROCESS): sync from ucs: [ user] [ modify] cn=5tn93llrkw,cn=87thmndrce,dc=dgalkin,dc=dev 25.11.2014 21:26:23,926 LDAP (PROCESS): Unable to sync cn=5tn93llrkw,cn=87thmndrce,dc=dgalkin,dc=dev (GUID: 71e3da28-b837-4748-bf01-df9e2211ce75). The object is currently locked. 25.11.2014 21:26:23,928 LDAP (PROCESS): sync from ucs: Resync rejected file: /var/lib/univention-connector/s4/1416013819.228149 25.11.2014 21:26:23,931 LDAP (PROCESS): sync from ucs: [ user] [ delete] cn=5tn93llrkw,cn=87thmndrce,dc=dgalkin,dc=dev 25.11.2014 21:26:23,946 LDAP (PROCESS): Unable to sync cn=5tn93llrkw,cn=87thmndrce,dc=dgalkin,dc=dev (GUID: 71e3da28-b837-4748-bf01-df9e2211ce75). The object is currently locked. 25.11.2014 21:26:23,948 LDAP (PROCESS): sync from ucs: Resync rejected file: /var/lib/univention-connector/s4/1416013819.249796 25.11.2014 21:26:23,949 LDAP (PROCESS): sync from ucs: [ container] [ delete] cn=87thmndrce,dc=dgalkin,dc=dev 25.11.2014 21:26:23,973 LDAP (WARNING): delete subobject: uid=5tn93llrkw,cn=87thmndrce,dc=dgalkin,dc=dev 25.11.2014 21:26:23,975 LDAP (WARNING): sync failed, saved as rejected /var/lib/univention-connector/s4/1416013819.249796 25.11.2014 21:26:23,975 LDAP (WARNING): Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/univention/s4connector/__init__.py", line 785, in __sync_file_from_ucs or (not old_dn and not self.sync_from_ucs(key, object, premapped_ucs_dn, old_dn, old, new))): File "/usr/lib/pymodules/python2.7/univention/s4connector/s4/__init__.py", line 2524, in sync_from_ucs self.delete_in_s4( object, property_type ) File "/usr/lib/pymodules/python2.7/univention/s4connector/s4/__init__.py", line 2578, in delete_in_s4 if not self.sync_from_ucs(key, subobject, object_mapping['dn']): File "/usr/lib/pymodules/python2.7/univention/s4connector/s4/__init__.py", line 2231, in sync_from_ucs if self.property[property_type].sync_mode in ['read', 'none']: KeyError: None the object uid=5tn93llrkw,cn=87thmndrce,dc=dgalkin,dc=dev seems to be deleted, but containers not.
I don't know how it could be reproduced. Please re-open with more details.
I had this traceback on a ucs@school 4.3 singlemaster after executing 63_udm-containers/07_container_ou_rename_uppercase How to reproduce: Add an ou Add an user under that ou Lock that user: ''' from univention.s4connector.lockingdb import LockingDB lockingdbfile = '/etc/univention/connector/lockingdb.sqlite' lockingdb = LockingDB(lockingdbfile) lockingdb.lock_ucs($entryUUID) lockingdb.lock_s4($objectGUID) ''' Now delete that ou (through udm) The traceback should now show up in the connector-s4.log Problem: s4connector/s4/__init__.py:2806 ''' if self.modules[k].identify(result[0], result[1]): ''' identify doesn't work with samba objects only with ldap objects.
Created attachment 9609 [details] Bug37555_untested_proposal.patch
Happened again in the tests. While this probably doesn't happen very often in customer environments, dealing with rejects seems to often produce side effects and lots of log messages during the tests. That's why I would like to see a fix for this.
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.
As mentioned in comment 4, this can still happen. -> Updated version field to 4.3
Happened on a school slave with UCS 4.4-1 186 I will test the proposed patch here
*** This bug has been marked as a duplicate of bug 49956 ***
<http://errata.software-univention.de/ucs/4.4/239.html>