Database error, Zabbix upgrade from 6.4.X to latest 7.0.2.

[Steve.]

Hello everyone,

I have a Zabbix installation 6.4.11 on Ubuntu 22.04.
I don't have experience with Linux OS, just basic knowledge and for everything else I go to Google.
I follow the official upgrade path and I type all the commands as in the article https://www.zabbix.com/documentation.../debian_ubuntu
After the update, all commands seem to execute without errors.
When I type the command

apt list --installed | grep zabbix

I get the output below

zabbix-agent/zabbix,now 1:7.0.2-1+ubuntu22.04 amd64 [installed]
zabbix-apache-conf/zabbix,now 1:7.0.2-1+ubuntu22.04 all [installed]
zabbix-frontend-php/zabbix,now 1:7.0.2-1+ubuntu22.04 all [installed]
zabbix-release/zabbix,now 1:7.0-2+ubuntu22.04 all [installed]
zabbix-server-pgsql/zabbix,now 1:7.0.2-1+ubuntu22.04 amd64 [installed]
zabbix-sql-scripts/zabbix,now 1:7.0.2-1+ubuntu22.04 all [installed]

But when I go to my Zabbix GUI I get an error.

Database error
The Zabbix database version does not match current requirements.
Your database version: 6040000. Required version: 7000000.
Please contact your system administrator.

I read on other posts about DB username and passwords, I checked and those are ok.
I did a restart on the server with no fix on the error.

Can anyone help me on this error and how I can fix it?

As my installation is new I thought to do a clean install but I would like to do a little troubleshooting and check the upgrade process.

Kind regards,
Steve.

[Markku]

But when I go to my Zabbix GUI I get an error.

Database error
The Zabbix database version does not match current requirements.
Your database version: 6040000. Required version: 7000000.
Please contact your system administrator.

This means that you have upgraded the UI files but Zabbix server process has not upgraded the database yet.

Check zabbix_server.log what's happening (or, if you haven't restarted the process yet, restart it with "sudo systemctl restart zabbix-server", it should start upgrading the database automatically).

Markku

[Markku]

But when I go to my Zabbix GUI I get an error.

Database error
The Zabbix database version does not match current requirements.
Your database version: 6040000. Required version: 7000000.
Please contact your system administrator.

This means that you have upgraded the UI files but Zabbix server process has not upgraded the database yet.

Check zabbix_server.log what's happening (or, if you haven't restarted the process yet, restart it with "sudo systemctl restart zabbix-server", it should start upgrading the database automatically).

Markku

[Steve.]

Thank you Markku,

The restart service, probably, did the work. I don't know as I restarted the server (VM) 3 or 4 times.
Now I ca see the GUI but I have a notification

Zabbix server is not running

I checked the Queue overview with the details below

Cannot display item queue.
Connection to Zabbix server "127.0.0.1:10051" refused. Possible reasons:
1. Incorrect "NodeAddress" or "ListenPort" in the "zabbix_server.conf" or server IP/DNS override in the "zabbix.conf.php";
2. Security environment (for example, SELinux) is blocking the connection;
3. Zabbix server daemon not running;
4. Firewall is blocking TCP connection.
Connection refused

Running the command

tail -f /var/log/zabbix/zabbix_server.log

I get the information below.

4453:20240807:103356.959 Starting Zabbix Server. Zabbix 7.0.2 (revision d1b0c3308ce).
4453:20240807:103356.959 ****** Enabled features ******
4453:20240807:103356.959 SNMP monitoring: YES
4453:20240807:103356.959 IPMI monitoring: YES
4453:20240807:103356.959 Web monitoring: YES
4453:20240807:103356.959 VMware monitoring: YES
4453:20240807:103356.959 SMTP authentication: YES
4453:20240807:103356.959 ODBC: YES
4453:20240807:103356.959 SSH support: YES
4453:20240807:103356.959 IPv6 support: YES
4453:20240807:103356.959 TLS support: YES
4453:20240807:103356.959 ******************************
4453:20240807:103356.959 using configuration file: /etc/zabbix/zabbix_server.conf
4453:20240807:103356.996 current database version (mandatory/optional): 07000000/07000002
4453:20240807:103356.996 required mandatory version: 07000000
4455:20240807:103357.003 starting HA manager
4455:20240807:103357.028 HA manager started in active mode
4453:20240807:103357.029 server #0 started [main process]
4457:20240807:103357.030 server #1 started [service manager #1]
4458:20240807:103357.031 server #2 started [configuration syncer #1]
4458:20240807:103357.429 __mem_malloc: skipped 0 asked 48 skip_min 18446744073709551615 skip_max 0
4458:20240807:103357.430 === memory statistics for configuration cache ===
4458:20240807:103357.430 free chunks of size 24 bytes: 3
4458:20240807:103357.430 free chunks of size 32 bytes: 1
4458:20240807:103357.430 free chunks of size 40 bytes: 3
4458:20240807:103357.430 min chunk size: 24 bytes
4458:20240807:103357.430 max chunk size: 40 bytes
4458:20240807:103357.430 memory of total size 29132592 bytes fragmented into 276342 chunks
4458:20240807:103357.430 of those, 224 bytes are in 7 free chunks
4458:20240807:103357.430 of those, 29132368 bytes are in 276335 used chunks
4458:20240807:103357.430 of those, 4421456 bytes are used by allocation overhead
4458:20240807:103357.430 ================================
4458:20240807:103357.430 === Backtrace: ===
4458:20240807:103357.432 12: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_backtrace+0x52) [0x55e9d0457232]
4458:20240807:103357.432 11: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](__zbx_shmem_malloc+0x68) [0x55e9d036ee08]
4458:20240807:103357.433 10: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_insert_ext+0xbe) [0x55e9d039ba9e]
4458:20240807:103357.433 9: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x273926) [0x55e9d02d9926]
4458:20240807:103357.433 8: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_dc_sync_configuration+0x4abd) [0x55e9d02f51ed]
4458:20240807:103357.433 7: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dbconfig_thread+0x115) [0x55e9d013dc05]
4458:20240807:103357.433 6: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_thread_start+0x24) [0x55e9d03782b4]
4458:20240807:103357.433 5: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0xd117b) [0x55e9d013717b]
4458:20240807:103357.433 4: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](MAIN_ZABBIX_ENTRY+0xec9) [0x55e9d0138789]
4458:20240807:103357.433 3: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](main+0x392) [0x55e9d012c5e2]
4458:20240807:103357.433 2: /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7fb2ca1f5d90]
4458:20240807:103357.433 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7fb2ca1f5e40]
4458:20240807:103357.433 0: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](_start+0x25) [0x55e9d01339c5]
4458:20240807:103357.433 [file:dbconfig.c,line:239] __zbx_shmem_malloc(): out of memory (requested 48 bytes)
4458:20240807:103357.433 [file:dbconfig.c,line:239] __zbx_shmem_malloc(): please increase CacheSize configuration parameter
4453:20240807:103357.442 One child process died (PID:4458,exitcode/signal:1). Exiting ...
4455:20240807:103357.442 HA manager has been paused
4455:20240807:103357.452 HA manager has been stopped
4453:20240807:103357.456 Zabbix Server stopped. Zabbix 7.0.2 (revision d1b0c3308ce).

Do you have any idea why this is happening?

Thank you very much for your time!

[Markku]

please increase CacheSize configuration parameter

it says, so I guess that's the first idea to try

Markku

[Steve.]

Yeap! Increasing the CacheSize to 64M did the trick!
Thank you for your help!