Univention Bugzilla – Bug 43763
LMDB listener doesn't remove objects from cache that have no modules but LDAP children
Last modified: 2020-07-03 20:53:49 CEST
During re-initialization tests with the UCS 4.2 LMDB listener code (Bug 23367) I found log messages that show that the listener doesn't remove cache objects that have no modules but LDAP children in the dntree. The old code would have removed those cache objects in this case. This is a very special case and I'm not even sure if it's a bug or a feature. Reproducible e.g. on a DC Master with S4-Connector by disabling the s4-connector listener module and re-initializing all modules: ucr set connector/s4/listener/disabled=yes connector/s4/autostart=no service univention-directory-listener stop rm /var/lib/univention-directory-listener/handlers/* service univention-directory-listener start The listener logs these error messages for each container object: ================================================================== 09.03.17 11:34:12.772 LISTENER ( WARN ) : initializing module s4-connector 09.03.17 11:34:12.773 LISTENER ( ERROR ) : dntree_del_id: delete failed: subordinate objects must be deleted first ================================================================== +++ This bug was initially created as a clone of Bug #23367 +++
Created attachment 8508 [details] dntree_del.patch This patch would change the behavior back to the previous. As I said above, currently I'm not sure if we should apply this patch.
Created attachment 8509 [details] dntree_del.patch Updated instructions to reproduce.
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.