Univention Bugzilla – Bug 48835
mdb_equality_candidates ... not indexed messages after 4.3.3-448
Last modified: 2021-08-27 11:38:13 CEST
I have noticed the new occurence of "mdb_equality_candidates: (attribute) not indexed" on two systems after applying the upgrades to errata 448. In my case the attributes were "kopanoAccount" and "ownCloudEnabled|nextcloudEnabled". Other attributes may be affected too. On one machine I could proove that the UCRV "ldap/index/eq" included the attributes in question before the upgrade and missed them afterwards. Without checking the code I would conclude that some routine has reset the UCRV to a default. This assumption can be confirmed by checking config-registry.replog The solution described in https://help.univention.com/t/problem-log-entries-mdb-equality-candidates-o-not-indexed/10259 will fix the problem.
most likely solved by #48970
(In reply to Dirk Ahrnke from comment #1) > most likely solved by #48970 Ahh, makes sense! I will mark as duplicate. *** This bug has been marked as a duplicate of bug 48970 ***
The fix for Bug 48970 does two things: * prevents that additional systems run into this issue * restores UCS@school specific attribute indices But it doesn't restore the indices other apps configured.
While releasing the update for Bug 48970 today I had the idea that we could just set the UCR variables the superset of all attributes that apps may have added to the index and then run ldap_setup_index --remove-unknown to strip away the ones that are unknown in that domain. That could be a "one size fits all" solution but requires some testing.
Grepping for "ldap_setup_index" shows two attributes that we index, that might also have been lost: univentionAppID univentionUDMPropertyCopyable
This issue has been filed against UCS 4.3. UCS 4.3 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.