Hello guys,
we are running last version of Zabbix 5.0 LTS on Debian 10 with backend of Mariadb/Galera cluster (10.4.latest on Debian 10).. (Whole database has about 520GB, it has partitioned history/trend tables, about 1k2 hosts, 270k items, 106k triggers).. We've decided it's time to upgrade to Deb 11 as well as Zabbix 6.0 LTS so first part was to prepare galera cluster which went OK, now Galera VM's are upgraded Debian 11 with 10.5 Mariadb/Galera working - all upgrades/clean-ups went fine..
Next I upgraded the Deb 10/Zabbix 5.0 LTS first to Deb 11/Zabbix 5.0 LTS - went OK.. Actually at this point my coleagues notices that once I've upgraded all VMs from Deb10 -> Deb11 and upgraded Galera/Mariadb from 10.4 to 10.5 whole system and responsivness become much better..
Next thing was upgrading actuall Zabbix 5.0 binaries/configs on existing Deb11 VM - that went also OK but when I finally start server in order to upgrade databases I've received this:
2475:20220825:165858.670 Starting Zabbix Server. Zabbix 6.0.7 (revision 442920c8f69).
2475:20220825:165858.670 ****** Enabled features ******
2475:20220825:165858.670 SNMP monitoring: YES
2475:20220825:165858.670 IPMI monitoring: YES
2475:20220825:165858.670 Web monitoring: YES
2475:20220825:165858.670 VMware monitoring: YES
2475:20220825:165858.670 SMTP authentication: YES
2475:20220825:165858.670 ODBC: YES
2475:20220825:165858.670 SSH support: YES
2475:20220825:165858.670 IPv6 support: YES
2475:20220825:165858.670 TLS support: YES
2475:20220825:165858.670 ******************************
2475:20220825:165858.671 using configuration file: /etc/zabbix/zabbix_server.conf
2475:20220825:165858.687 current database version (mandatory/optional): 05000000/05000005
2475:20220825:165858.687 required mandatory version: 06000000
2475:20220825:165858.687 optional patches were found
That was on 25th of August ;-) since then no additional info is in the zabbix-server log, nothing about upgrading database.. _however_ there is something going on on the database.. I see data comming to/from zabbix server towards database.. Now I see only these repeating all the time:
s...
5.5.5-10.5.17-MariaDB-1:10.5.17+maria~deb11-log..I..^Rap2D>L...-...............BFvB$-R9er-(.mysql_native_password.............-.......................zabbix..a.....R....}...{c). .zabbix.mysql_native_password..._client_name.mysql nd._server_host.A.B.C.D................SET AUTOCOMMIT=1...........-....SHOW VARIABLES LIKE "character_set_database".....d....def.information_schema.SESSION_VARIABLES .SESSION_VARIABLES
Variable_name
VARIABLE_NAME.-...........]....def.information_schema.SESSION_VARIABLES.SESSI ON_VARIABLES.Value.VARIABLE_VALUE.-.. ..............."......character_set_database.utf8. ......"......SET NAMES utf8................SHOW TABLES LIKE 'dbversion'.....d....def.information_schema.TABLE_NAMES.TABLE _NAMES.Tables_in_zabbix (dbversion)
TABLE_NAME.!..................".
... dbversion.......".&....SELECT dv.mandatory FROM dbversion dv.....9....def.zabbix.dv dbversion mandatory mandatory.?.................."......5030198....... "......
Current DB version as responded in the dumps:
MariaDB [zabbix]> select * from dbversion;
+-----------+----------+
| mandatory | optional |
+-----------+----------+
| 5030198 | 5030198 |
+-----------+----------+
Previously I've seend select and updates of triggers and such things.. now
I'd like to ask you what do you thing is a good thing to do, stop/kill zabbix-server? Try to do something else? I have no problems of installing zabbix 6 and it's database from the scratch (see P.S.) but I'd need to recover data from old database - at least in terms of hosts, configs, triggers, maps etc.. - I can live without old history..
Thanks &
BR
P.S. I'm not in hurry as I have recovered older Galera VM's as well as Zabbix VM (all on Deb11 already with 10.5 Mariadb/Galera) and it's running in parallel using set of different IP's and our department still have working enviroment..
we are running last version of Zabbix 5.0 LTS on Debian 10 with backend of Mariadb/Galera cluster (10.4.latest on Debian 10).. (Whole database has about 520GB, it has partitioned history/trend tables, about 1k2 hosts, 270k items, 106k triggers).. We've decided it's time to upgrade to Deb 11 as well as Zabbix 6.0 LTS so first part was to prepare galera cluster which went OK, now Galera VM's are upgraded Debian 11 with 10.5 Mariadb/Galera working - all upgrades/clean-ups went fine..
Next I upgraded the Deb 10/Zabbix 5.0 LTS first to Deb 11/Zabbix 5.0 LTS - went OK.. Actually at this point my coleagues notices that once I've upgraded all VMs from Deb10 -> Deb11 and upgraded Galera/Mariadb from 10.4 to 10.5 whole system and responsivness become much better..
Next thing was upgrading actuall Zabbix 5.0 binaries/configs on existing Deb11 VM - that went also OK but when I finally start server in order to upgrade databases I've received this:
2475:20220825:165858.670 Starting Zabbix Server. Zabbix 6.0.7 (revision 442920c8f69).
2475:20220825:165858.670 ****** Enabled features ******
2475:20220825:165858.670 SNMP monitoring: YES
2475:20220825:165858.670 IPMI monitoring: YES
2475:20220825:165858.670 Web monitoring: YES
2475:20220825:165858.670 VMware monitoring: YES
2475:20220825:165858.670 SMTP authentication: YES
2475:20220825:165858.670 ODBC: YES
2475:20220825:165858.670 SSH support: YES
2475:20220825:165858.670 IPv6 support: YES
2475:20220825:165858.670 TLS support: YES
2475:20220825:165858.670 ******************************
2475:20220825:165858.671 using configuration file: /etc/zabbix/zabbix_server.conf
2475:20220825:165858.687 current database version (mandatory/optional): 05000000/05000005
2475:20220825:165858.687 required mandatory version: 06000000
2475:20220825:165858.687 optional patches were found
That was on 25th of August ;-) since then no additional info is in the zabbix-server log, nothing about upgrading database.. _however_ there is something going on on the database.. I see data comming to/from zabbix server towards database.. Now I see only these repeating all the time:
s...
5.5.5-10.5.17-MariaDB-1:10.5.17+maria~deb11-log..I..^Rap2D>L...-...............BFvB$-R9er-(.mysql_native_password.............-.......................zabbix..a.....R....}...{c). .zabbix.mysql_native_password..._client_name.mysql nd._server_host.A.B.C.D................SET AUTOCOMMIT=1...........-....SHOW VARIABLES LIKE "character_set_database".....d....def.information_schema.SESSION_VARIABLES .SESSION_VARIABLES
Variable_name
VARIABLE_NAME.-...........]....def.information_schema.SESSION_VARIABLES.SESSI ON_VARIABLES.Value.VARIABLE_VALUE.-.. ..............."......character_set_database.utf8. ......"......SET NAMES utf8................SHOW TABLES LIKE 'dbversion'.....d....def.information_schema.TABLE_NAMES.TABLE _NAMES.Tables_in_zabbix (dbversion)
TABLE_NAME.!..................".
... dbversion.......".&....SELECT dv.mandatory FROM dbversion dv.....9....def.zabbix.dv dbversion mandatory mandatory.?.................."......5030198....... "......
Current DB version as responded in the dumps:
MariaDB [zabbix]> select * from dbversion;
+-----------+----------+
| mandatory | optional |
+-----------+----------+
| 5030198 | 5030198 |
+-----------+----------+
Previously I've seend select and updates of triggers and such things.. now
I'd like to ask you what do you thing is a good thing to do, stop/kill zabbix-server? Try to do something else? I have no problems of installing zabbix 6 and it's database from the scratch (see P.S.) but I'd need to recover data from old database - at least in terms of hosts, configs, triggers, maps etc.. - I can live without old history..
Thanks &
BR
P.S. I'm not in hurry as I have recovered older Galera VM's as well as Zabbix VM (all on Deb11 already with 10.5 Mariadb/Galera) and it's running in parallel using set of different IP's and our department still have working enviroment..