Univention-pkgdb-scan did not work any more

Apps & App Center
#1

Hello all,

after Update to 4.4-7 on some servers the the package database can’t be updated anymore. Errormessage:

Traceback (most recent call last):
  File "/usr/sbin/univention-pkgdb-scan", line 37, in <module>
    univention.pkgdb.main()
  File "/usr/lib/python2.7/dist-packages/univention/pkgdb.py", line 579, in main
    connection = open_database_connection(config_registry, pkgdbu=False)
  File "/usr/lib/python2.7/dist-packages/univention/pkgdb.py", line 561, 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:  Passwort-Authentifizierung für Benutzer »darkdevil$« fehlgeschlagen

So i have set the machine password manualy. But i get the same error mesage. What’s going wrong, and what should i do?

Very Thanks and best Regards
Boospy

#3

Is there a way to solve this? By for example delte the whole database?

1 Like
#4

This is an UCS in-house app and no one can help? I can buy believe that I am the only one here with the topic…

#5

Hello all,

maybe i have fixed it. What have i done?

Logged into pgsqlserver on the master and changed all the machinepasswords by the pgsqlusers manualy. Example:

sudo su - postgres -c 'psql'
\du  #list the users
ALTER USER superserver$ WITH PASSWORD 'blablabla';
\q

After this an
univention-pkgdb-scan
Runs successfully again.

Strange is, 2 machines worked until today. All others threw in the log this error on the PGSQL server.

2021-02-19 21:44:50 CET [20431-2] superserver$@pkgdb DETAIL:  Benutzer »superserver$« hat kein Passwort zugewiesen.
        Verbindung stimmte mit pg_hba.conf-Zeile 98 überein: »host    all         all        192.2.2.2/16          md5«

I think normaly Pgsql should connect via LDAP, because there is an configfile:
/etc/postgresql/pam_ldap.conf
I hope with the next password rotation this goes in the PGSQL again automatically with.

#6

So wie es aussieht, wurde hier Lizenz technisch einiges verändert. Denn trotz meine Änderung funktioniert es nun schon wieder nicht mehr. Ich hab ein Screenshot angehängt. Hier sieht man sehr gut dass dieses Feature kostenpflichtig geworden ist. Mein UCS läuft schon über ein Jahr. Also so lange kann das noch nicht sein.

Schade, war ein nettest Feature. Screenshot_20210227_233651

Mastodon