Bug 43645 - update to 4.2-0 failed with slapd bdb error
update to 4.2-0 failed with slapd bdb error
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.2
Other Linux
: P5 normal (vote)
: UCS 4.2
Assigned To: Felix Botner
Arvid Requate
https://bugs.launchpad.net/ubuntu/+so...
: interim-3
Depends on:
Blocks: 43232
  Show dependency treegraph
 
Reported: 2017-02-24 11:13 CET by Felix Botner
Modified: 2017-04-04 18:29 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2017-02-24 11:13:13 CET
UCS system installed with 1.2 updated to 4.2-0
http://jenkins.knut.univention.de:8080/job/UCS-4.2/job/UCS-4.2-0/job/Update%20Tests/test_system=update-from-1.2/

failed with slapd bdb error

[info] 58b002df OVER: Loading Translog Overlay 58b002df OVER: db_init 58b002df OVER: Configuring Translog Overlay 58b002df OVER: Configured Translog Overlay to use file "/var/lib/univention-ldap/listener/listener" 58b002df /etc/ldap/slapd.conf: line 113: warning, threads=64 larger than twice the default (2*16=32); YMMV. 58b002df bdb(dc=old,dc=test): BDB0126 mmap: Invalid argument 58b002df bdb_db_open: database "dc=old,dc=test" cannot be opened, err 22. Restore from backup! 58b002df backend_startup_one (type=bdb, suffix="dc=old,dc=test"): bi_db_open failed! (22) slap_startup failed.
invoke-rc.d: initscript slapd, action "start" failed.
dpkg: Fehler beim Bearbeiten des Paketes slapd (--configure):
Comment 1 Felix Botner univentionstaff 2017-02-28 11:06:22 CET
The slapd preinst did not backup the database due to a version mismatch in database_format_changed (checked old version 2.4.39-1, but in 4.1 we already have 2.4.42).

Patched that version to 2.4.42+dfsg-2.A~4.2.0.201702221139:
4.2-0-0-ucs/2.4.42+dfsg-2/98_database_upgrade_version.patch

slapd update worked in my tests
Comment 2 Felix Botner univentionstaff 2017-02-28 11:06:36 CET
next Problem 

Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
libblas3 (1.2.20110419-10) wird eingerichtet ...
update-alternatives: Fehler: Alternative libblas.so.3gf kann kein Slave von libblas.so.3 sein: Sie ist eine Master-Alternative
dpkg: Fehler beim Bearbeiten des Paketes libblas3 (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libblas3gf:
 libblas3gf hängt ab von libblas3; aber:
  Paket libblas3 ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes libblas3gf (--configure):
 Abhängigkeitsprobleme - verbleibt unkonfiguriert
liblapack3 (3.5.0-4) wird eingerichtet ...
update-alternatives: Fehler: Alternative liblapack.so.3gf kann kein Slave von liblapack.so.3 sein: Sie ist eine Master-Alternative
dpkg: Fehler beim Bearbeiten des Paketes liblapack3 (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von liblapack3gf:
 liblapack3gf hängt ab von liblapack3; aber:
  Paket liblapack3 ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes liblapack3gf (--configure):
 Abhängigkeitsprobleme - verbleibt unkonfiguriert
Fehler traten auf beim Bearbeiten von:
 libblas3
 libblas3gf
 liblapack3
 liblapack3gf
Comment 3 Arvid Requate univentionstaff 2017-02-28 11:17:56 CET
Sounds like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776633 ?
Comment 4 Felix Botner univentionstaff 2017-03-01 15:37:11 CET
update preup:

remove alternative liblapack.so.3gf|libblas.so.3gf is exists
Comment 5 Ingo Sieverdingbeck univentionstaff 2017-03-03 13:38:19 CET
Due to the modified version for the database_format_changed all UCS-4.1 installation would be forced into the slapcat/slapadd even if they use the MDB backend, which should be unaffected by the modified BDB version.

Please check if it is possible to include also the used backend into database_format_changed.
Comment 6 Felix Botner univentionstaff 2017-03-07 11:15:42 CET
(In reply to Ingo Sieverdingbeck from comment #5)
> Due to the modified version for the database_format_changed all UCS-4.1
> installation would be forced into the slapcat/slapadd even if they use the
> MDB backend, which should be unaffected by the modified BDB version.
> 
> Please check if it is possible to include also the used backend into
> database_format_changed.

Is it OK to have a UCR variable update42/slapd/database/dump=false to disable the dump?
Comment 7 Ingo Sieverdingbeck univentionstaff 2017-03-07 12:00:32 CET
From my perspective this would be enough.
Comment 8 Felix Botner univentionstaff 2017-03-09 10:22:22 CET
(In reply to Ingo Sieverdingbeck from comment #7)
> From my perspective this would be enough.

Added 

if [ "xfalse" = "x$(ucr get update42/slapd/database/dump)" ]; then
    return 1
fi

to database_dumping_enabled. So if update42/slapd/database/dump is set to false, dumping should be disabled.
Comment 9 Arvid Requate univentionstaff 2017-03-13 17:56:01 CET
univention-ldap-server still depends on db5.1-util, I guess that is because univention-ldap/debian/control still build-depends on libdb5.1-dev.
Comment 10 Felix Botner univentionstaff 2017-03-13 18:10:51 CET
(In reply to Arvid Requate from comment #9)
> univention-ldap-server still depends on db5.1-util, I guess that is because
OK, fixed
Comment 11 Arvid Requate univentionstaff 2017-03-16 18:32:29 CET
Ok, a changelog entry is not required, I guess.
Comment 12 Stefan Gohmann univentionstaff 2017-04-04 18:29:17 CEST
UCS 4.2 has been released:
 https://docs.software-univention.de/release-notes-4.2-0-en.html
 https://docs.software-univention.de/release-notes-4.2-0-de.html

If this error occurs again, please use "Clone This Bug".