Univention Bugzilla – Bug 55066
postgresql@11-main.service masked despite postgres11/autostart=yes
Last modified: 2022-08-09 19:02:54 CEST
We discovered, that the postgresql@11-main.service is unable to start after an update from UCS 4.4-9 to UCS 5.0-1 and following the steps from https://help.univention.com/t/updating-from-postgresql-9-6-or-9-4-to-postgresql-11/17531 Reasons: 1. Although postgres11/autostart is set to 'yes', the service is masked. Workaround: systemctl unmask postgresql@11-main.service 2. On our system, the service "...failed because the service did not take the steps required by its unit configuration" caused by the missing folder /etc/postgresql/11/main/conf.d/. Workaround: see linked help article Expectation: these two steps should be assured in the package univention-posrgresql-11 (or any following version)
Upgrading PostgreSQL *always* requires manual steps: You can install multiple versions of PostgreSQL at the same time, but only one can bind to TCP port 5432. On upgrades you have to at least disable the old version 9.[46] en enable the ne version 11. You also have to migrate the data whenever the major version changes. This is to fragile for full automation and *always* needs manual inspection. It may also leads to a down-time (depending on the size of your database), which an Administrator should schedule. Therefore the installation of the new version and performing the upgrade are two separate steps. Because of that we have that help article. If steps are missing there update it. There is nothing to change in univention-postgresql-11 as it works for *new* installations; for *upgrades* the required steps must be performed manually.
systemctl unmask postgresql@11-main.service has been added to the help article. Worksforme
> Although postgres11/autostart is set to 'yes', the service is masked. Workaround: systemctl unmask postgresql@11-main.service This is unexpected behavior and should be analyzed. Does it affect other services too?