After upgrade to Univention "4.2-0 errata29 getting floods of CRON JOB failure emails

After upgrade to Univention "4.2-0 errata29 getting floods of CRON JOB failure emails.

Cron root@bebucsbdcsvrp1 if [ -x /usr/sbin/univention-pkgdb-check ]; then /usr/sbin/univention-pkgdb-check; fi

Traceback (most recent call last):
File “/usr/sbin/univention-pkgdb-scan”, line 37, in
File “/usr/lib/pymodules/python2.7/univention/”, line 576, in main
connection = open_database_connection(config_registry, pkgdbu=True)
File “/usr/lib/pymodules/python2.7/univention/”, line 560, in open_database_connection
connection = pgdb.connect(database=connectstring)
File “/usr/lib/python2.7/dist-packages/”, line 482, in connect
dbtty, dbuser, dbpasswd)
pg.InternalError: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket “/var/run/postgresql/.s.PGSQL.5432”?

check the postgres installation, the command ‘univention-pkgdb-scan --test-superuser’ failed

This so far ONLY shows up on our one of our backup domain controllers for UCS. (Hostname: bebucsbdcsvrp1) but not on any other backup domain controller, member server OR slave domain controller on the network.

We are getting about 1 cron email failure alarm every 15 to 30 minutes.

This was NOT happening before the update to Univention 4.2-0 errata29.

Any suggestions on how to correct this issue? Otherwise is it OK to just remove the cron job?

I reckon the following also not works:

root@ucs-7906:/usr/sbin# ./univention-pkgdb-scan

Do you use the software-monitor? “univention-pkgdb”

No it does not.

and Yes we do use it.

hm, maybe it is an option to reinstall it (software monitor). The removal of the cron job may defeat the purpose of the software monitor. The problem lies with the underlying postgres installation.