I'm going to upgrade to zabbix server 5.4.
Can I use zabbix 5.4 only in CentOS8?
I don't think there's a centos7 version in repo.
Can I use zabbix 5.4 only in CentOS8?
I don't think there's a centos7 version in repo.
-
-
Zabbix 5.4 server cannot be built using official Zabbix package on CentOS 7.
https://blog.zabbix.com/staying-up-t...ackages/12806/ -
Hello -
We're on CentOS7 using MariaDB (5.x). Database is roughly 200-300GB
What would be the recommended upgrade path to get away from CentOS7 while retaining our Database?
If I wanted to say migrate to Ubuntu & keep using MariaDB is that going to be a nightmare?
I was hoping we might be able to build new Zabbix Servers & import\restore the Database into MariaDB but not sure how that, or the upgrade of the DB, would look like, since we're a bit stuck being on CentOS7.Comment
-
The combination of IBM/RedHat's changes to CentOS 8 and Zabbix's discontinuing support for CentOS/RHEL 7 on Zabbix server have caused the same dilemma for a lot of sites, I think.
What I haven't seen from the Zabbix developers (maybe they've posted somewhere, but I haven't seen it) is whether they plan to support either AlmaLinux or RockyLinux, which are the spiritual successors to CentOS. Having an answer to that question would be useful for many sites.
If you choose a Ubuntu version that has a MariaDB version that's similar to what you're currently running, you shouldn't have much trouble migrating. It's basically just a dump & re-load for the database. Keep in mind that later versions of Zabbix require more recent versions of MariaDB, so if you can find a version that provides you with some flexibility on which MariaDB versions you choose, you'll have an easier time upgrading.
If you start with something like MariaDB 10.0.x or 10.1.x, I recommend you investigate setting ROW_FORMAT=DYNAMIC before you import your SQL dump from your current MariaDB 5.5.x server. Several people have run into issues with certain Zabbix upgrades when their database was originally created with ROW_FORMAT=COMPACT , especially when upgrading to MariaDB 10.2.x. Some searching on these forums will probably get you more info on that issue.Comment
-
This is my 2nd month working with Zabbix\CentOS7 so I'm happy to read your post. I have made progress since my last post & ended up doing basically what you describe. During the Database upgrade I did run into some table issues & ended up setting a few to Dynamic, which you touch on. I've not gotten the front end up and running yet & in fact I may need to put the project on hold in favor of a different route, but since I've gotten this far I may just keep at it since I'm sick in the head & enjoy suffering.
Until I'm looking at solid Data & a working frontend this could all be for nothing, but the Database is upgraded & thus far I'm on track to get frontend up.
Steps were to set up Ubuntu, MariaDB (I just used latest versions).
I set up MariaDB the same as our Production as close as I could, passwords and all.
I restored the Database, ensured logs were removed. Set permissions.
SQL came up. I reset passwords for the DB for good measure.
Kept an eye on Zabbix Server log & set tables to Dynamic that it complains about. I may just set them all to Dynamic - still researching this.
Upgrade was successful.
I applied the SQL Patch from 4.2-5.0 since the log complained about it. (double.sql)
That's about where I'm at. I still need to get the frontend set up & hopefully connected, but feel good that the Database is running.
My goal is to complete this upgrade successfully & then apply this process to production. (or just break out my lab Zabbix server into a distro & use it).
I'd rather just start over with new Servers & a new Database. Then hit the old Zabbix for old Data, or somehow connect the Database as a 2nd Database & view archive\legacy Data but not sure how to achieve that. -
All the steps you've taken sound good. I think you're well on your way to having the database successfully moved.
My feeling is that you should change every table to ROW_FORMAT=DYNAMIC. It is the new default for more recent versions of MariaDB. Mixing COMPACT and DYNAMIC in your database will (I think) increase the chances you run into problems some time in the future.
What problem are you running into with the front end?
-
-
We've taken a step back to evaluate & decide how we want to proceed.
I got to the point where it kicked off some alert emails. I think if I would have gotten the PHP\Web issues sorted out it would have been successful, but I was told to bring it down & haven't been back to work on it since. It certainly seems doable but we might sub it out to someone who's more familiar with Linux\Postgres, Web Servers, etc.Comment
Comment