Univention Bugzilla – Bug 49822
univentionAppID added to LDAP index in 30univention-appcenter.inst (second slapindex after LDAP replication)
Last modified: 2019-07-05 16:28:51 CEST
see also Bug #49821 The same problem we i guess the same solution Together with Bug #49821 this is the second! slapdindex after the LDAP replication during the slave/backup join.
(In reply to Felix Botner from comment #0) > see also Bug #49821 > > The same problem we i guess the same solution NOOOOOOOOOOOO! Read Bug #49821 comment #1: > You *must not* do that when the schema is only later registered using the UDM schema extension mechanism. $ git grep univention-app.schema -- management/univention-appcenter/ management/univention-appcenter/30univention-appcenter.inst: --schema /usr/share/univention-appcenter/univention-app.schema
(In reply to Philipp Hahn from comment #1) > (In reply to Felix Botner from comment #0) > > see also Bug #49821 > > > > The same problem we i guess the same solution > > NOOOOOOOOOOOO! Read Bug #49821 comment #1: > > You *must not* do that when the schema is only later registered using the UDM schema extension mechanism. > > $ git grep univention-app.schema -- management/univention-appcenter/ > management/univention-appcenter/30univention-appcenter.inst: --schema > /usr/share/univention-appcenter/univention-app.schema we could check if the univentionAppID attribute is already known in the local schema (which it should be on an backup/slave) and add it to the index in 01univention-ldap-server-init.inst from my point of view the index should be configured before the LDAP replication, so that we no longer need to slapindex during the "initial" join
The problem on this bug applies to backup/slave only. On the UCS master the ldap database is "empty" during the initial join and a additional slapindex in not expensive, but on backup and slaves this could take while