7.0.0 Beta 3 Update: The Zabbix database version 6050229. Required version: 6050256.

[Captain_Bear]

Greetings,
We recently installed Zabbix on what we thought was a stable release (6.5.1). Per our scheduled maintenance plan, the Ubuntu 22.04 server was updated with APT. After performing these updates, we have now discovered that we are on 7.0.0 Beta 3 and our database version is preventing us from launching the monitoring platform as expected. Your database version: 6050229. Required version: 6050256.

zabbix_server (Zabbix) 7.0.0beta3
Revision 11b4728fed8 17 April 2024, compilation time: Apr 17 2024 07:57:28

When we run "cat /var/log/zabbix/zabbix_server.log |grep database"

The output is as follows:
1124:20240424:101723.890 current database version (mandatory/optional): 06050229/06050256

When we run " tail /var/log/zabbix/zabbix_server.log"

The output is as follows:
1161:20240425:071125.577 [Z3005] query failed: [1054] Unknown column 'lifetime_type' in 'field list' [select hostid,key_,evaltype,formula,lifetime_type,lifetim e,enabled_lifetime_type,enabled_lifetime from items where itemid=39807]
1161:20240425:071125.577 invalid discovery rule ID [39807]

What is installed: "apt list |grep zabbix"

pcp-export-pcp2zabbix/jammy 5.3.6-1build1 amd64
pcp-export-zabbix-agent/jammy 5.3.6-1build1 amd64
python3-pyzabbix/jammy,jammy 0.8.2-1 all
zabbix-agent-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-agent2-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-agent2-plugin-mongodb/zabbix 1:7.0.0~beta3-1+ubuntu22.04 amd64
zabbix-agent2-plugin-mssql/zabbix 1:7.0.0~beta3-1+ubuntu22.04 amd64
zabbix-agent2-plugin-postgresql/zabbix 1:7.0.0~beta3-1+ubuntu22.04 amd64
zabbix-agent2/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-agent/zabbix,now 1:7.0.0~beta3-4+ubuntu22.04 amd64 [installed]
zabbix-apache-conf/zabbix,now 1:7.0.0~beta3-4+ubuntu22.04 all [installed]
zabbix-frontend-php/zabbix,now 1:7.0.0~beta3-4+ubuntu22.04 all [installed]
zabbix-get-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-get/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-java-gateway/zabbix 1:7.0.0~beta3-4+ubuntu22.04 all
zabbix-js-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-js/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-nginx-conf/zabbix 1:7.0.0~beta3-4+ubuntu22.04 all
zabbix-proxy-mysql-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-proxy-mysql/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-proxy-pgsql-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-proxy-pgsql/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-proxy-sqlite3-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-proxy-sqlite3/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-release/zabbix,now 1:6.5-1+ubuntu22.04 all [installed]
zabbix-sender-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-sender/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-server-mysql-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-server-mysql/zabbix,now 1:7.0.0~beta3-4+ubuntu22.04 amd64 [installed]
zabbix-server-pgsql-dbgsym/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-server-pgsql/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64
zabbix-sql-scripts/zabbix,now 1:7.0.0~beta3-4+ubuntu22.04 all [installed]
zabbix-web-service/zabbix 1:7.0.0~beta3-4+ubuntu22.04 amd64

We have run through the process of making the zabbix db accout privileged, changed mysql to "SET GLOBAL log_bin_trust_function_creators = 1;"

Any assistance would be greatly appreciated.

[tim.mooney]

Greetings,
We recently installed Zabbix on what we thought was a stable release (6.5.1).

For future reference, you want to stick with X.<even #>.Z releases, for example 6.0.27 or 6.2.# or 6.4.#. Going as far back as I can remember with Zabbix, there's never been a "stable release" that is X.5.Z. For the past few major releases, X.5.Z is the alpha or beta for the next major LTS version.

The problem with applying "SET GLOBAL ..." and any other database config changes you've made now is that they are likely too late. You needed those changes in place before the attempted upgrade.

You can try restarting zabbix_server. It will notice that there are still database changes that need to be made and re-attempt the next one that is still pending, but I kind of doubt that is going to work. Usually when a database change fails to apply on upgrade it's because there are previous changes that either didn't apply fully or correctly.

If you have an experienced DBA on staff that can help you and you're really, really invested in your current install, then follow up in this thread. Either I or maybe someone else that beats me to it can point to where the actual failing SQL is in the source code. You could have your DBA examine your existing DB and try figure out what's wrong and make any manual changes they think are appropriate to get the database to the structure that the upgrade is expecting, and then restart zabbix_server and let it proceed with the remaining updates.

Since you've apparently just started with Zabbix, though, it might be a lot easier to do a re-install on a supported stable version.

[Captain_Bear]

Thank you for the information regarding the version numbering.