Elaborazione dei trigger per python-support (1.0.15.18.201403132013)...
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 578, in main
connection = open_database_connection(config_registry, pkgdbu=False)
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 482, in connect
dbtty, dbuser, dbpasswd)
pg.InternalError: could not connect to server: Connection refused
Is the server running on host "ucs-8023.cdlmvenezia.intranet" (172.16.6.55) and accepting
TCP/IP connections on port 5432?
univention-pkgdb-scan is executed after or right at the end of the upgrade to scan and submit the current package status to “ucs-8023.cdlmvenezia.intranet (172.16.6.55)”. This is because the App “Software installation monitor” (the internal name is pkgdb) is or was installed on this server. However, the PostgreSQL database that powers the “Software installation monitor” is not reachable. That’s the error.
So please check:
is the App “Software installation monitor” still installed on that server?
if not, but you want it to, re-install it
if not, and you want to leave it that way, you will need to remove the DNS SRV entry that starts with "_pkgdb"
if yes, then check if the service is actually running: service postgresql status
● postgresql.service - PostgreSQL RDBMS
Loaded: loaded (/lib/systemd/system/postgresql.service; enabled)
Active: active (exited) since mer 2017-10-25 20:43:49 CEST; 1 weeks 0 days ago
Main PID: 2949 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/postgresql.service
ott 25 20:43:49 ucs-8023 systemd[1]: Started PostgreSQL RDBMS.
2017-11-21 11:20:46 CET [1934-2] LOG: verranno utilizzate statistiche vecchie invece di quelle correnti perché il processo di raccolta statistiche non risponde
2017-11-23 07:52:38 CET [1869-2] LOG: richiesta di arresto fast ricevuta
2017-11-23 07:52:38 CET [1869-3] LOG: interruzione di tutte le transazioni attive
2017-11-23 07:52:38 CET [1934-3] LOG: arresto dell’esecutore di autovacuum
2017-11-23 07:52:38 CET [1931-1] LOG: arresto in corso
2017-11-23 07:52:39 CET [1931-2] LOG: il database è stato arrestato
2017-11-23 08:54:46 CET [2016-1] [sconosciuto]@[sconosciuto] LOG: pacchetto di avvio incompleto
2017-11-23 08:54:46 CET [2015-1] LOG: il database è stato arrestato alle 2017-11-23 07:52:39 CET
2017-11-23 08:54:47 CET [2017-1] postgres@postgres FATALE: il database si sta avviando
2017-11-23 08:54:48 CET [2029-1] postgres@postgres FATALE: il database si sta avviando
2017-11-23 08:54:48 CET [2034-1] postgres@postgres FATALE: il database si sta avviando
2017-11-23 08:54:48 CET [2015-2] LOG: le protezioni di wraparound dei membri MultiXact ora sono abilitate
2017-11-23 08:54:48 CET [1947-1] LOG: il database è pronto ad accettare connessioni
2017-11-23 08:54:48 CET [2134-1] LOG: esecutore di autovacuum avviato
Hi, i’ve look that I’ve 2 postgresql version: 9.1 and 9.4
on postgresql-9.1-main.log:
2017-11-27 09:59:02 CET LOG: pam_authenticate failed: Autentication failed
2017-11-27 09:59:02 CET FATALE: PAM failed user "ucs-7758$
this error message occurs when the machine’s password is changed i.e either the contents of the /etc/machine.secret file is changed, or a new password is entered in the UMC. The postgresql cannot identify the machine, as a result authentication failure.
The best way to solve this problem is to copy the current machine secret in the /etc/machine.secret file of your machine, and paste it in the UMC module Computers.
cat /etc/machine.secret
Select the computer in question, in your case, ucs-7758, under Advanced settings → Account paste/enter the copied password in the Password field, as shown below
Hi.
Sorry to bring back yo life this old thread but I’m facing the same problem on the latest version.
UCS Version: 4.4-3 errata456 (Blumenthal)
UMC Version: 11.0.4-57A~4.4.0.202002171325
My fresh install setup (4.4-1 ISO and upgrade when installing):
dc01: master dc (AD Compatible DC, DHCP Server, Self Service)
dc02: backup dc (AD Compatible DC, DHCP Server, Software Installation Monitor).
I was trying trying to add iSCSI (apt install open-iscsi) to be able to access a NAS with targets already configured. It installed but I got the errors the original OP mentioned in the first post.
Uninstalling “Software Installation Monitor” makes the error go away. Tested the postgres stop start, status without error. Nslookup, ping: ok. The sopy paste /etc/machine.secret did not made a difference.
Finally tried installing it in the MASTER DC and had the same behavior.
