Univention Bugzilla – Bug 35506
locking fails if cn=ATTRIBUTE_NAME,cn=temporary,cn=univention is not readable
Last modified: 2020-07-03 20:51:39 CEST
The locking mechanism could create the necessary container cn=ATTRIBUTE_NAME,cn=temporary,cn=univention if it does not exists. 36856 29.07.14 08:11:21.223 ADMIN ( INFO ) : LOCK univention.admin.locking.lock scope = base 36857 29.07.14 08:11:21.224 ADMIN ( INFO ) : Traceback (most recent call last): 36862 File "/usr/lib/pymodules/python2.6/univention/admin/hooks.d/.py", line 62, in lock 36863 value = request(module.lo, module.position, MAP_NAME, value=value) 36864 File "/usr/lib/pymodules/python2.6/univention/admin/allocators.py", line 169, in request 36865 return acquireUnique(lo, position, type, value, _type2attr[type], scope = _type2scope[type]) 36866 File "/usr/lib/pymodules/python2.6/univention/admin/allocators.py", line 158, in acquireUnique 36867 univention.admin.locking.lock(lo, position, type, value, scope=scope) 36868 File "/usr/lib/pymodules/python2.6/univention/admin/locking.py", line 66, in lock 36869 lo.add(dn, al, exceptions=0) 36870 File "/usr/lib/pymodules/python2.6/univention/admin/uldap.py", line 398, in add 36871 raise univention.admin.uexceptions.ldapError, _err2str(msg) 36872 ldapError: No such object
locking mechanism means univention.admin.allocators.request()
If I remeberes this some days ago... This is a simple adaption to Bug #42379. We should not create the container (because this happens probably only when the ACL's deny read access) but we should handle this error appropriatly with a nice error message.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.