Univention Bugzilla – Bug 46055
postgresql not running during setup - pkgdb installations fails
Last modified: 2018-03-14 14:38:13 CET
Created attachment 9347 [details] pkgdb.png See screenshot, univention-pkgdb creates psql users in the postinst, but postgresql seems to be not running Installation from DVD with pkgdb
Probably the same issue as Bug #45905?! The service is started via "invoke-rc.d" and therefore not started by systemd because the debian installer runs in a chroot environment.
(In reply to Florian Best from comment #1) > Probably the same issue as Bug #45905?! > The service is started via "invoke-rc.d" and therefore not started by > systemd because the debian installer runs in a chroot environment. probably, this was an installation and i got the error in the system setup step (before the first reboot)
We need this for the install tests!
fixed in univention-postgresql (as in Bug #45905)
still not working, the join of univention-pkgdb during the installation fails 22.01.18 00:50:56.135 LISTENER ( WARN ) : finished initializing module libvirtd-acl with rv=0 22.01.18 00:50:56.135 LISTENER ( WARN ) : initializing module pkgdb Traceback (most recent call last): File "/usr/sbin/univention-pkgdb-scan", line 37, in <module> univention.pkgdb.main() File "/usr/lib/pymodules/python2.7/univention/pkgdb.py", line 576, in main connection = open_database_connection(config_registry, pkgdbu=True) File "/usr/lib/pymodules/python2.7/univention/pkgdb.py", line 560, in open_database_connection connection = pgdb.connect(database=connectstring) File "/usr/lib/python2.7/dist-packages/pgdb.py", line 1615, in connect cnx = _connect(dbname, dbhost, dbport, dbopt, dbuser, dbpasswd) pg.InternalError: FATAL: Peer-Authentifizierung für Benutzer »pkgdbu« fehlgeschlagen
univention-pkgdb 69d22ad71b750db2b61d10c04e0a9dae77091ba2 restart postgresql in postinst
OK, works. Changelog: OK
UCS 4.3 has been released: https://docs.software-univention.de/release-notes-4.3-0-en.html https://docs.software-univention.de/release-notes-4.3-0-de.html If this error occurs again, please use "Clone This Bug".