Zabbix 7.0.0rc3 Update issues

[cm_llp]

We are trying to update our HA cluster to Zabbix 7.0.0rc3. We have all other nodes shutdown and HANodeName is commented out on the primary server to perform the db upgrade but in the logs the server is complaining about being unable to update when the nodes are in HA mode.

23047:20240530:004123.616 using configuration file: /etc/zabbix/zabbix_server.conf
23047:20240530:004123.758 current database version (mandatory/optional): 06050256/06050256
23047:20240530:004123.907 required mandatory version: 06050305
23047:20240530:004123.908 mandatory patches were found
23047:20240530:004123.914 cannot perform database upgrade in HA mode: all nodes need to be stopped and Zabbix server started in standalone mode for the time of upgrade.
23047:20240530:004123.914 Zabbix Server stopped. Zabbix 7.0.0rc3 (revision 53cc53f4056).
23063:20240530:004134.128 Starting Zabbix Server. Zabbix 7.0.0rc3 (revision 53cc53f4056). zz0.jtilbus34czz

Why does the server still think its in HA mode when its clearly disabled? All other nodes are definitely powered down. With the server running if we ran ' zabbix_server -R ha_status' you get no results either.

Any ideas?

[Markku]

If you think you are following the correct procedure and it doesn't work, go to the Zabbix support portal and open an issue there. It is possible that there is a bug in the rc code.

Markku

[Markku]

Support portal is at support.zabbix.com.

Markku

[cisk]

It seems I have a similar issue, upgrading docker-compose from 7.0.2beta to 7.0.3. I have a complaint that the database has not been upgraded.



Zabbix server log cycling:

      7:20240602:221125.938 Starting Zabbix Server. Zabbix 7.0.0rc3 (revision ab98c9e).
         7:20240602:221125.938 ****** Enabled features ******
         7:20240602:221125.938 SNMP monitoring: YES
         7:20240602:221125.938 IPMI monitoring: YES
         7:20240602:221125.938 Web monitoring: YES
         7:20240602:221125.938 VMware monitoring: YES
         7:20240602:221125.939 SMTP authentication: YES
         7:20240602:221125.939 ODBC: YES
         7:20240602:221125.939 SSH support: YES
         7:20240602:221125.939 IPv6 support: YES
         7:20240602:221125.939 TLS support: YES
         7:20240602:221125.939 ******************************
         7:20240602:221125.939 using configuration file: /etc/zabbix/zabbix_server.conf
         7:20240602:221126.735 current database version (mandatory/optional): 06050257/06050257
         7:20240602:221126.735 required mandatory version: 07000000
         7:20240602:221126.735 mandatory patches were found
         7:20240602:221126.745 starting automatic database upgrade
         7:20240602:221126.748 [Z3005] query failed: [1419] You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) [create trigger proxy_group_insert after insert on proxy_group
         for each row
         insert into changelog (object,objectid,operation,clock)
         values (20,new.proxy_groupid,1,unix_timestamp())]
         7:20240602:221126.749 database upgrade failed on patch 06050258, exiting in 10 seconds
        7:20240602:221126.900 Zabbix Server stopped. Zabbix 7.0.0rc3 (revision ab98c9e).​

[cisk]

Sorry, it seems I was able to solve this by uncommenting the line in compose_databeses.yaml (as I;m running from docker_compose)

- --log_bin_trust_function_creators=1

[db100]

i am having the same issue ... how to perform an upgrade on kubernetes ?

i have tried strating the node with HANODE env variable and the config file is getting it, but still refusing to upgrade i have tried to manually remove the reocrd from the ha_node table but still no luck ... i am using this chart upgrading from 6.4.4 to 7.0.0 https://artifacthub.io/packages/helm...y/zabbix/5.0.0

[cisk]

i am having the same issue ... how to perform an upgrade on kubernetes ?

i have tried strating the node with HANODE env variable and the config file is getting it, but still refusing to upgrade i have tried to manually remove the reocrd from the ha_node table but still no luck ... i am using this chart upgrading from 6.4.4 to 7.0.0 https://artifacthub.io/packages/helm...y/zabbix/5.0.0

Have you got it sorted?

[db100]

indeed, i did get it sorted ... but i honestly forgot how