When upgrading the Univention from 5.0-10 to 5.2-1 I get into a situation where slapd won’t start.
The errors are:
Apr 16 10:06:43 external slapd[31695]: 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEPVINTERFACE” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILECPUS” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILENAMEPREFIX” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEVNC” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEPVDISK” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEPVCDROM” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILERAM” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEARCH” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEVIRTTECH” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEBOOTDEVICES” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEDISKSPACE” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEINTERFACE” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEKBLAYOUT” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILERTCOFFSET” inserted. 67ff6513 UNKNOWN attributeDescription “UNIVENTIONVIRTUALMACHINEPROFILEOS” inserted. 67ff6513 backend_startup_one (type=mdb, suffix=“dc=external,dc=xxxxxxx,dc=com”): bi_db_open failed! (-1) slap_startup failed.
Apr 16 10:06:43 external systemd[1]: slapd.service: Control process exited, code=exited, status=1/FAILURE
Subject: Unit process exited
Defined-By: systemd
Support: Debian -- User Support
An ExecStart= process belonging to unit slapd.service has exited.
– The process’ exit code is ‘exited’ and its exit status is 1.
Apr 16 10:06:43 external systemd[1]: slapd.service: Failed with result ‘exit-code’.
I’ve tried to get around this issue in several ways, but could not stop it from coming back. The entries are not available on the LDAP directory to remove.
Seems linked to the “univention-virtual-machine-manager.schema” that is removed earlier during the upgrade process.
Any suggestions?
Thank you.