Zabbix: How I upgraded from 6.2.6 to 6.4.1

[tom.blackstone]

Here is how I upgraded my Zabbix from 6.2.6 to 6.4.1

Environment:
Version 6.2.6
Server: Debian 11
Componemt: Server, Frontend, Agent
Database: MySQL
Web Server: Apache

These are the steps I took to upgrade. This worked for me:

1. Take a snapshot of the server in VMware.
2. PuTTy into server at IP address with ZABBIX credentials
3. SU root and entered root password
4. Set PATH for ROOT
   PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
5. Stop the Zabbix Server
   service zabbix-server stop
6. Stop the Zabbix Server
   systemctl stop zabbix-server
7. Remove the old Zabbix Package\files
   dpkg --purge zabbix-release
8. Download the new Zabbix software
   wget https://repo.zabbix.com/zabbix/6.4/d...bian11_all.deb
9. Deploy the new Zabbix software
   dpkg -i zabbix-release_6.4-1+debian11_all.deb
10. Check for updates
    apt-get update
11. Install Zabbix software
    apt-get install --only-upgrade zabbix-server-mysql zabbix-frontend-php zabbix-agent
12. Upgrade the Apached Web Front
    apt-get install zabbix-apache-conf
13. Next, access the MYSQL database and change rights – notice the semi-colon at the end of each line, which must be included. Run one line at a time
    1. mysql -uroot -p
    2. Enter Root password
    3. mysql> grant all privileges on zabbix.* to zabbix@localhost;
    4. mysql> set global log_bin_trust_function_creators = 1;
    5. mysql> quit;
14. Reboot the server
    shutdown -r

Run this command to confirm the database upgrade has been completed
cat /var/log/zabbix/zabbix_server.log | grep database

You should see the upgrade, something like this.

782:20230418:084424.462 completed 0% of database upgrade
782:20230418:084424.488 completed 1% of database upgrade
782:20230418:084424.530 completed 2% of database upgrade
782:20230418:084424.583 completed 3% of database upgrade
782:20230418:084424.643 completed 4% of database upgrade
782:20230418:084424.693 completed 5% of database upgrade
(lines 6% through 95% deleted to shorten this example)
782:20230418:084438.152 completed 96% of database upgrade
782:20230418:084438.165 completed 97% of database upgrade
782:20230418:084438.247 completed 98% of database upgrade
782:20230418:084438.396 completed 99% of database upgrade
782:20230418:084438.402 completed 100% of database upgrade
782:20230418:084438.434 database upgrade fully completed
595:20230418:084821.642 current database version (mandatory/optional): 06040000/06040000

1. If the database looks good, access the MYSQL database again and change rights .
   Notice the semi-colon at the end of each line, which must be included.
   Run one line at a time.
   1. mysql -uroot -p
   2. Enter root password
   3. mysql> grant all privileges on zabbix.* to zabbix@localhost;
   4. mysql> set global log_bin_trust_function_creators = 0;
   5. mysql> quit;

On your Web browser, clear your cache and cookies and the access the Zabbix portal

[jtnfoley]

Cool - Thanks Tom! I'll be doing 6.x to 6.4.x upgrades in four locations very soon!

[cyber]

Why granting privileges twice in DB? If you had a zabbix instance there already, why do it at all? Shouldn't those privileges be there already ? I can get the point of that global setting (if it is already not set in config), but you should already have rest of it...
And what's that reboot for? Just to start up server (and flush DB privileges, if its on same server)? Come on... You can do better..
Depending on your DB size, upgrade can take a while... so you can run "tail -f server.log | grep database" to keep interactive log running