Upgrade v2.4.8 to latest v5 - HOW?

[kberrien]

I recently noticed the age of our Zabbix install, the repo we were using didn't provide any post v2 releases.

I reviewed what I could find about possible upgrade paths and it appears v5 will detect and upgrade v2.4 - however, how that might be accomplished is missing. The package files / structure is vastly different, there isn't a zabbix-server or server-mysql and so forth. I don't even see a web package.

There are: Agent, Agent2, Get, Sender

I can find install info, but very little about upgrading - what are dependencies such as PHP version, etc.., what do I remove, what do I install? How do I kick up any upgrade process??

If possible, I'd most like to build a new server with new Centos (our old still runs v6) and migrate my zabbix config into a fresh install.

Does anyone know were to find specific upgrade info, or could point me in the right direction somehow?

thanks!

[isaqueprofeta]

1) Install a new CentOS8
2) Install the same zabbix version that you currently have
3) Recover a version of your database in this new CentOS8 install (if you using a separated database server, make sure you have a backup)
4) Review and confirm that everything is working with new CentOS and same zabbix version
5) Proceed with upgrade (https://www.zabbix.com/documentation...es/rhel_centos):
5.1) Update packages using yum
5.2) Start server to upgrade the zabbix v2 database to v5
5.3) Start webserver
6) Pay yourself a beer

[kberrien]

I have since discovered that the repository folder I was looking in for https://repo.zabbix.com/zabbix/5.0/rhel/6/i386/ does not have all the normal files, and looking at other combinations, such as https://repo.zabbix.com/zabbix/5.0/rhel/8/x86_64/ I see more of what I had expected.

I've installed a clean 5.0.2 on Centos 8 - to get a feel for the newer version - and I'm leaning not towards an upgrade but rather rebuilding my configuration (it will take a bit of time) which will allow me to clean up / organize and improve things.

[tim.mooney]

If you can spare the time to take that approach, it's a good way to go. Having the old monitoring environment available as an example and to do monitoring while you transition to the "new and improved environment" is a good situation to be in.

Also, the new official templates are a *huge* improvement over the old templates that shipped with 2.x. You'll want to spend some time looking at the new templates and how customizable they are. Even if you don't end up using any of them (they monitor a lot of stuff by default, and some environments like to "keep it simple"), the templates serve as an *excellent* example of what's possible and how to use macros well in your own templates.

Be advised that there have been a number of people that have run into certain web front-end issues with 5.0.2, so when 5.0.3 is released, you'll want to upgrade to that.