Zabbix 7.2 upgrade fail

[Morpheus_Davis]

Hi there,
I tried to start the zabbix-web-nginx-pgsql container with a new persistent volume and that works with the zabbix-web-nginx-pgsql:latest docker image.
Issue fixed on my side with that change, no data lost at all.
Hope this help !

[binderth]

define('ZABBIX_VERSION', '7.0.6');
define('ZABBIX_API_VERSION', '7.0.6');
define('ZABBIX_EXPORT_VERSION', '7.0');

So the all docker images for the front end are still in 7.0.6. Can we expect an update soon ?

Edit: So from rage I deleted

zabbix-web

and recreated it. Everything is now fine.

Can I just kiss you!
That's great and the solution for my problem also. Zabbix-Server and the PostgreSQL worked finde, my WARN alerts came through, but the Frontend wasn't loading up. I just created a new volume and now it works as expected. Seems like a bug in the all(?) docker updates for me - because I already got this error more than once and simply re-created all of my stuff in ZABBIX again.

Hi MicelSup, what do you mean? Did you recreate the Docker container only or the Docker volume as well?

Just re-creating the container does NOT do the trick, you have to re-create the volume.

[mlazzarotto]

Just re-creating the container does NOT do the trick, you have to re-create the volume.

Yep, that did the trick!

[lukeluke1979]

I confirm this trick.

Thanks a lot

[pablo.sanchez]

Dear Zabbix Support Team,
I am in an offline environment and running PostgreSQL 16.1 on a Linux 9 operating system.
I recently upgraded Zabbix from version 7.0 to 7.2 and now I have an issue where the Zabbix server keeps indicating that the database version is not supported. The error I get is the following:
"Database error: Zabbix database version does not match the current requirements. Your database version: 7020000. Required version: 7000000.
I have verified that the database version is correctly set to 7020000, but Zabbix is still showing this error. I have also performed the following steps to try to fix it:

- I have verified that the database upgrade scripts have been executed correctly.
- I have verified that the Zabbix configuration file (`zabbix_server.conf`) is pointing to the correct database.
- I have reviewed the Zabbix and database logs, but have not found any further details that could indicate the problem.
- I have tried clearing the Zabbix cache and restarting the server, but the problem persists.

zabbix_server --version
zabbix_server: /usr/pgsql-16/lib/libpq.so.5: no version information available (required by zabbix_server)
zabbix_server (Zabbix) 7.2.2
Revision bc0d5fdf8af 6 Jan 2025, build time: 6 Jan 2025 00:00:00

I would appreciate any guidance or solution you can offer.
Kind regards,
Pablo

[PhaseIV]

Hey Pablo,

did you checked your DB Password in /etc/zabbix/zabbix_server.conf?
Pretty sure it is not set after upgrade process.

Kind Regards
Sebastian

[pkropf]

Yes! Followed the upgrade instructions at

https://www.zabbix.com/documentation/current/en/manual/installation/upgrade/packages/debian_ubuntu

and received the dreaded database mismatch error.

During the package install process, I selected Y to replace the zabbix_server.conf file which resulted in a few lost settings including the DBPassword entry. Setting that entry to the correct value restored access to my Zabbix monitoring service.

Thanks!

[MBender]

Can I just kiss you!
That's great and the solution for my problem also. Zabbix-Server and the PostgreSQL worked finde, my WARN alerts came through, but the Frontend wasn't loading up. I just created a new volume and now it works as expected. Seems like a bug in the all(?) docker updates for me - because I already got this error more than once and simply re-created all of my stuff in ZABBIX again.

Just re-creating the container does NOT do the trick, you have to re-create the volume.

I'm confused. Which volume? Because if I've got a docker configuration I do NOT want to re-create my volume and lose all my existing data. That's the whole point of an "upgrade", no?

In other words - I'm still short what the steps to fix this are if Zabbix is docker-installed.

EDIT:
Found the cause. The problem (for me) was some uncommented Java-related server setting that did nothing in the previous version but in 7.2 caused Zabbix server to look for the other Java-related settings and then complain about them not being set. In other words - for me at least, the upgrade process never really properly started.

[[email protected]]

Hi there,
I tried to start the zabbix-web-nginx-pgsql container with a new persistent volume and that works with the zabbix-web-nginx-pgsql:latest docker image.
Issue fixed on my side with that change, no data lost at all.
Hope this help !

This worked for me. 7.2 => 7.4. I owe you a beer.