Upgrade di Zabbix 4.x a 6.2: Difference between revisions

From RVM Wiki
Jump to navigation Jump to search
Created page with "{{sTUB}} *[https://www.zabbix.com/forum/zabbix-help/443739-help-restoring-a-zabbix-server-without-the-history-trend-tables Help Restoring a Zabbix Server without the History..."
(No difference)

Revision as of 16:54, 2 February 2023

Template:STUB


mysqldump --no-data zabbix > zabbix_backup.sql

mysqldump --no-create-info --ignore-table=zabbix.history --ignore-table=zabbix.history_uint --ignore-table=zabbix.history_text --ignore-table=zabbix.history_log --ignore-table=zabbix.history_str --ignore-table=zabbix.trends --ignore-table=zabbix.trends_uint zabbix >> zabbix_backup.sql


docker compose exec mysql-server /bin/bash

password root_pwd

  • import DB


UPDATE mysql.user SET Super_Priv='Y' WHERE user='zabbix1' AND host='%';


7:20230126:110733.090 [Z3005] query failed: [1

419] You do not have the SUPER privilege and binary logging is enabled (you *might* wan t to use the less safe log_bin_trust_function_creators variable) [create trigger hosts_ insert after insert on hosts zabbix-zabbix-server-1 | for each row zabbix-zabbix-server-1 | insert into changelog (object,objectid,operation,clock) zabbix-zabbix-server-1 | values (1,new.hostid,1,unix_timestamp())] zabbix-zabbix-server-1 | 7:20230126:110733.091 database upgrade failed zabbix-zabbix-server-1 | 7:20230126:110733.103 database could be upgraded to use primary keys in history tables

vi env_vars/.env_srv ZBX_CACHESIZE=2G



UPDATE users SET passwd = '$2a$10$ZXIvHAEP2ZM.dLXTm6uPHOMVlARXX7cqjbhM6Fn0cANzkCQBWpMrS' WHERE username = 'Admin';

After running this query, the user's password will be set to zabbix. Make sure to change the default password on the first login.

PROXY

Installare 6.2

pfsense

rm /var/db/zabbix-proxy/zabbix.db