Zabbix 8 stopped connecting to database following apt upgrade

[spyro]

Hi,

My zabbix-server has stopped connecting to the postgres database since updating to the current version.

The database is available only via unix sockets, and is running on a nonstandard "port" (5433, not 5432).

It appears to be ignoring the DBPort variable in the configuration file, wheras previously it would use this value to determine the correct unix socket path (which for postgres seems to incorporate the port number (even if you dont listen on tcp).

This was working perfectly prior to the update, and the database is still accessible from the command line.

Is there a known fix for this?

The log contains messages such as:

[Z3001] connection to database 'zabbix' failed: [0] connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: password authentication failed for user "zabbix"

(note the incorrect socket path, it should be /var/run/postgresql/.s.PGSQL.5433)

[spyro]

Update:

I've reverted the config to use a TCP connection to the database - this still works, so I know that my overall configuration is correct, and my server is up and running again.

It seems to be now be impossible to set up a zabbix 8 server to use postgresql, if your database socket is not at the default location (/var/run/postgresql/.s.PGSQL.5432) anymore.

This is either a regression, or an undocumented change in the configuration syntax, as nothing else had changed when this broke.

Would it not make more sense to use the DBSocket config parameter, in a similar manner to the MySQL config? It seems perverse to have an option to specify a unix socket path for one database, but to generate the unix socket path based on a port number for a TCP socket (which does not exist)... Or at least allow either method of configuration?

[cyber]

Zabbix v8 is in beta. It can still contain bugs. It does not even have full functionality yet... Use it on your own risk in non prod env, just to keep up with changes and search for bugs...