UCS ships with "univention-bacula", but it's state does not meet my expectations: - there is no integration into UMC (like the minimal one with Nagios) - the documentation still references version 5.2 - Debian-Stretch has 7.4 - we removed Kolab from UCS-3 to allow OX, Kopano - we should do the same with Bacula as bacula, Bareos, SEP sesam are all better maintained in the App Center
changelog-5.0-0.xml 236a05689652 | Bug #46588: Remove univention-bacula
The manual still mentions univention-bacula. And please remove the bacula product test (do not change 4.4, create a new 5.0 wiki page and change that one)
(In reply to Felix Botner from comment #2) > The manual still mentions univention-bacula. [5.0-0] 3c0b1d2ce5 Bug #46588 doc: Remove backup with bacula doc/manual/backup-de.xml | 539 --------------------------------------------------- doc/manual/backup-en.xml | 513 ------------------------------------------------ doc/manual/handbuch-5.0.xml | 1 - doc/manual/illustrations44/bacula.png | Bin 93139 -> 0 bytes doc/manual/illustrations44/bacula.svg | 1 - doc/manual/illustrations44/bacula_en.png | Bin 91631 -> 0 bytes doc/manual/illustrations44/bacula_en.svg | 1 - doc/manual/manual-5.0.xml | 1 - 8 files changed, 1056 deletions(-) > And please remove the bacula product test (do not change 4.4, create a new > 5.0 wiki page and change that one) https://hutten.knut.univention.de/mediawiki/index.php/Produkttests_UCS_5.0
OK
Jan tested this again, the 5.0-0 upgrade failed: https://taiga.knut.univention.de/media/attachments/8/d/e/2/68d3038223de08de36d2998473f460dae4d392ce854a89c313967f0533ef/screenshot-from-2021-03-15-11-38-04.png
The complete log from the update can be found here: https://taiga.knut.univention.de/media/attachments/5/f/c/a/1cf2735e4b1e06ce8a1b50a9b59248aaa7a3e75f781ca044e76f35e1c059/updater.log
This may be the postgresql issue: error encountered processing /usr/share/dbconfig-common/data/bacula-director-pgsql/upgrade/pgsql/9.0.0 (translated: /tmp/dbconfig-common.HXt3oB): psql: FATAL: Passwort-Authentifizierung für Benutzer »bacula« fehlgeschlagen Passwort wurde aus Datei »/tmp/dbconfig-common.psql_home.ib0LNg/.pgpass« gelesen FATAL: Passwort-Authentifizierung für Benutzer »bacula« fehlgeschlagen Passwort wurde aus Datei »/tmp/dbconfig-common.psql_home.ib0LNg/.pgpass« gelesen dbconfig-common: bacula-director-pgsql configure: aborted. dbconfig-common: flushing administrative password dpkg: Fehler beim Bearbeiten des Paketes bacula-director-pgsql (--configure): »installiertes bacula-director-pgsql-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Or, more reasonable: /etc/postgresql/9.4/main/pg_hba.conf is now missing local @%@bacula/psql/database@%@ @%@bacula/psql/user@%@ password
OK: pg_lsclusters OK: su -c 'psql bacula' postgres OK: Upgrade blocked by `preup.sh`: > old_packages: > WARNING: The following packages from UCS-4 are still installed, which are no longer supported with UCS-5: > univention-bacula > > Use "univention-remove --purge" with the packages as following arguments to remove them > > This check can be disabled by setting the UCR variable 'update50/ignore_old_packages' to 'yes'. OK: ucr set update50/ignore_old_packages=yes OK: univention-remove --purge univention-bacula Nothing was changes, both scenarios worked for me. Probably Bug #52790 fixed it.
OK - update with univention-bacula is blocked OK - update with univention-bacula and ucr set update50/ignore_old_packages=yes FAIL - univention-remove --purge univention-bacula and update to 5.0 during the update univention-postgresql-9.6 gets auto-removed but not postgresql-9.6, postgresql-9.6 can't start after the update is this OK? Seems that the removal of univention-postgresql-9.6 deletes /etc/postgresql/9.6/main/pg_hba.conf but does not revert /etc/postgresql/9.6/main/pg_hba.conf.debian -> dpkg -l| grep postgres ii postgresql-9.6 9.6.20-0+deb9u1 amd64 object-relational SQL database, version 9.6 server ii postgresql-client 11+200+deb10u4 all front-end programs for PostgreSQL (supported version) ii postgresql-client-11 11.11-0+deb10u1 amd64 front-end programs for PostgreSQL 11 ii postgresql-client-9.6 9.6.20-0+deb9u1 amd64 front-end programs for PostgreSQL 9.6 ii postgresql-client-common 200+deb10u4 all manager for multiple PostgreSQL client versions ii postgresql-common 200+deb10u4 all PostgreSQL database-cluster manager ii postgresql-contrib-9.6 9.6.20-0+deb9u1 amd64 additional facilities for PostgreSQL rc univention-postgresql 11.0.1-3A~4.4.0.202004161257 all UCS - PostgreSQL configuration rc univention-postgresql-9.6 11.0.1-3A~4.4.0.202004161257 all -> service postgresql restart Apr 23 13:41:50 master systemd[1]: Starting PostgreSQL Cluster 9.6-main... Apr 23 13:41:50 master postgresql@9.6-main[30448]: The PostgreSQL server failed to start. Please check the log output: Apr 23 13:41:50 master postgresql@9.6-main[30448]: 2021-04-23 13:41:50.508 CEST [30453] LOG: konnte Konfigurationsdatei »/etc/postgresql/9.6/main/pg_hba.conf« nicht öffnen: Datei oder Verzeichnis nicht gefunden Apr 23 13:41:50 master postgresql@9.6-main[30448]: 2021-04-23 13:41:50.508 CEST [30453] FATAL: konnte pg_hba.conf nicht laden Apr 23 13:41:50 master postgresql@9.6-main[30448]: 2021-04-23 13:41:50.509 CEST [30453] LOG: Datenbanksystem ist heruntergefahren Apr 23 13:41:51 master systemd[1]: postgresql@9.6-main.service: Can't open PID file /run/postgresql/9.6-main.pid (yet?) after start: No such file or directory Apr 23 13:41:51 master systemd[1]: postgresql@9.6-main.service: Failed with result 'protocol'. Apr 23 13:41:51 master systemd[1]: Failed to start PostgreSQL Cluster 9.6-main. Apr 23 13:41:51 master systemd[1]: Starting PostgreSQL RDBMS... Apr 23 13:41:51 master systemd[1]: Started PostgreSQL RDBMS.
In preup.sh [5.0-0 795ae0a768] Bug #46588: mark univention-postgresql as manually installed I was able to reproduce this issue. auto-remove at the end of the upgrade removes univention-postgresql as it was only depended by univention-bacula. But: postgresql-9.6 stays installed. I do not know why. I could not find the package that keeps it installed. Had the user auto-removed before the upgrade, postgresql would have been uninstalled. So I went for the safe route and keep univention-postgresql if installed.
OK - univention-remove --purge univention-bacula and update to 5.0, postgres still works after the update
UCS 5.0 has been released: https://docs.software-univention.de/release-notes-5.0-0-en.html https://docs.software-univention.de/release-notes-5.0-0-de.html If this error occurs again, please use "Clone This Bug".