Zabbix - Migrate zabbix to a new server and major version

My original installation of Zabbix (v4.0) has been installed on centos7 and it's time to migrate it to a new el8 (v5.0) installation. I will use almalinux8 here but these steps should be identical for rockylinux or any other rhel8 clone.

I'll use postgresql and nginx for my setup, so the steps might vary when using mysql or httpd.

First, enable the postgresql module stream. Version 10 is enabled by default but I'll go for the latest available which is version 13 as of writing this.

 [root@zabbix-new ~]# yum -d 2 -y module enable postgresql:13

Now that the module stream is enabled, install the required packages:

 [root@zabbix-new ~]# yum -d 2 -y install postgresql postgresql-server postgresql-contrib

Initialize the database and start it:

 [root@zabbix-new ~]# su - postgres -c 'initdb'  
 [root@zabbix-new ~]# systemctl enable --now postgresql.service

Create the zabbix user and database in postgresql (creating the user will prompt for a password):

 [root@zabbix-new ~]# su - postgres -c 'createuser -P zabbix'  
 [root@zabbix-new ~]# su - postgres -c 'createdb -O zabbix zabbix'

Create a database backup on the old server and transfer it to the new installation:

 [root@zabbix-new]# nc -lvnp 8080 | bzip2 -cdv9 | psql -h 127.0.0.1 -p 5432 -d zabbix -U zabbix -W  
 [root@zabbix-old]# pg_dump -h 127.0.0.1 -p 5432 -d zabbix -U postgres -w | bzip2 -cv9 | nc -v zabbix-new.archyslife.lan 8080

Depending on the amount of data, this can take a minute.

Once the database transfer is done, we'll continue with the nginx setup on the new server. I'll use nginx v1.20 and php v7.4 which requires enabling a few modules again:

 [root@zabbix-new ~]# yum -d 2 -y module enable nginx:1.20 php:7.4

Now that all requirements are met, add the zabbix repo and install the packages:

 [root@zabbix-new ~]# rpm -Uvh https://repo.zabbix.com/zabbix/5.0/rhel/8/x86_64/zabbix-release-5.0-1.el8.noarch.rpm  
 [root@zabbix-new ~]# yum -d 2 -y install zabbix-server-pgsql zabbix-web-pgsql zabbix-nginx-conf zabbix-agent

These packages will generate the required configs for php-fpm and nginx. Before finally restarting the services, we'll need to adjust the 'listen' and 'server_name' directive in '/etc/nginx/conf.d/zabbix.conf' config and the timezone in '/etc/php-fpm.d/zabbix.conf'

 [root@zabbix-new ~]# sed -i 's/^#\ \ \ \ \ \ \ \ listen\ \ \ \ \ \ \ \ \ \ 80;/    listen 80;/g' /etc/nginx/conf.d/zabbix.conf  
 [root@zabbix-new ~]# sed -i "s/^#\ \ \ \ \ \ \ \ server_name\ \ \ \ \ example.com;/    server_name $(hostname -f);/g" /etc/nginx/conf.d/zabbix.conf  
 [root@zabbix-new ~]# sed -i 's/^; php_value\[date\.timezone\] = Europe\/Riga/php_value[date.timezone] = Europe\/Prague/g' /etc/php-fpm.d/zabbix.conf

With all configs set, restart the zabbix-server php-fpm and nginx to make them use the adjusted configs:

 [root@zabbix-new ~]# systemctl restart zabbix-server.service php-fpm.service nginx.service

Also make sure they're enabled so that they start automatically after a reboot:

 [root@zabbix-new ~]# systemctl enable --now zabbix-server.service php-fpm.service nginx.service

If you are using SELinux (which I highly encourage), you'll have to set a few booleans to allow zabbix to operate as expected:

 [root@zabbix-new ~]# setsebool -P httpd_builtin_scripting on  
 [root@zabbix-new ~]# setsebool -P httpd_can_connect_zabbix on  
 [root@zabbix-new ~]# setsebool -P httpd_can_network_connect_db on  
 [root@zabbix-new ~]# setsebool -P httpd_can_sendmail on  
 [root@zabbix-new ~]# setsebool -P httpd_enable_cgi on  
 [root@zabbix-new ~]# setsebool -P zabbix_can_network on

In order to finish the installation, connect to the WebUI on your server (http://your_server_ip_or_fqdn/)

Feel free to comment and / or suggest a topic.

Comments

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but for a detailed comparison check out this article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). recently went over my network configuration and I noticed that I've never put my My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key&quo

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the

Archy's Blog

Search This Blog