Output during package installation ("univention-install univention-self-service"): [...] Creating selfservice user Kein Passworteintrag für Benutzer »postgres« Could not create selfservice postgres user. Joinscript 35univention-self-service-passwordreset-umc.inst finished with exitcode 1 Restarting univention-directory-listener (via systemctl): univention-directory-listener.service. This hosts mail system must be configured so it can send away. Please consider the UCS documentation on the topic of a relay host: EN: http://docs.software-univention.de/manual-4.2.html#mail::serverconfig::relay DE: http://docs.software-univention.de/handbuch-4.2.html#mail::serverconfig::relay univention-self-service (4.0.3-9A~4.4.0.201904291701) wird eingerichtet ... Enabling site univention-self-service. To activate the new configuration, you need to run: systemctl reload apache2 Create umc/web/hooks/univention-self-service [...] The URLs to the UCS manual are outdated. Maybe we can use $version_version within the URL?
The link is already fixed in git with commit 5c81c970, Bug was #50205. Will be published with the next package build
While doing QA for Bug #52229 I noticed this problem again: (In reply to Sönke Schwardt-Krummrich from comment #0) > [...] > Creating selfservice user > Kein Passworteintrag für Benutzer »postgres« > Could not create selfservice postgres user. > Joinscript 35univention-self-service-passwordreset-umc.inst finished with > exitcode 1 "35univention-self-service-passwordreset-umc.inst" is accessing "user:postgres", which is part of "bin:univention-self-service-passwordreset-umc", but the dependency for "univention-postgresql" is from "bin:univention-self-service-master". This happens when "bin:univention-self-service" is installed by "apt-get install" (or "univention-install"), but "bin:univention-self-service-master" not not installed before.
This issue has been filed against UCS 4.4. UCS 4.4 is out of maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide information on how this issue is affecting you.