Install and use Zabbix 3.2 on CentOS 7 or RHEL 7

Zabbix is a monitoring tool which is widely used in all kinds of environments. Zabbix is very flexible, information can be retrieved using HTTP/SNMP or by installing a Zabbix agent on the machines to monitor, and allows a lot of customisation. Unfortunately this also means that the learning curve can be rather high. This post will go a little deeper into the installation process and the first steps in Zabbix.

Zabbix can be installed from most standard repositories in a variety of Linux distributions. For this post, I’m using CentOS 7 and I decided to use the official Zabbix repository to ensure that we’re using the latest version of Zabbix. Zabbix requires a database backend and for this post, I will use MariaDB (a fork of MySQL).

This post has been completely reviewed and updated where needed on 08/2017 to make sure everything is still working and is correct.

Add the Zabbix repository and install the packages

The first step is to enable the Zabbix official repository by creating a file in /etc/yum.repos.d:

The packages in the standard CentOS repositories have the version number in their name. (zabbix22 for version 2.2) so they will not conflict with the packages from the repository which we added.

To be sure, we can check if we really are installing the latest version:

As you can see, the packages for Zabbix are for version 3.2.7 and it will be taken from the repository which we just added, named Zabbix.

Besides the Zabbix-repository, you will also need the EPEL repository for some dependencies. If you haven’t done so, add that repo too:

Now that we are sure that Yum has access to the correct packages, let’s install what is necessary:

Configure the database

After installing the packages, we need to initialise MariaDB and set the root password. Don’t get confused with all the references to MySQL in the commands below. MariaDB is a fork of MySQL and clearly branding wasn’t very high on the priority list :)

Now that MariaDB is running and initialised, we can add a database for Zabbix, named zabbix, and create a user that has access to that DB. Use the root-password which you changed in the previous step when asked for a password and replace secretpassword with your own password for the zabbix database user.

Now that the database and user are ready, it’s time to create the database schema for Zabbix in the DB which we just added. The schema is delivered with Zabbix in /usr/share/doc/zabbix-server-mysql-<version>/create.sql.gz. (If you would install the packages from the standard repositories, the schema can be found in /usr/share/zabbix-mysql/.)

Be aware that, for this post, I’m leaving the rest of the MariaDB configuration at it’s default. For a production environment you really need some tuning in MariaDB to optimise the database system. To do so, I recommend using Zabbix for a while and then use on a regular basis to tune the database parameters. This approach is very straightforward and delivers very good results with a minimal effort.

Configure the webserver

At this point, our database is ready so the next step is to configure the webserver (Apache) and PHP.

The default parameters of PHP need some tuning for Zabbix:

The above commands just replace lines in /etc/php.ini by a line with the correct value. You can also edit the file by hand if you would like to.

Next up is Apache. The Yum-installation, created a file for Apache in /etc/httpd/conf.d/zabbix.conf. Edit this file to look similar to this:

Configure Zabbix parameters:

Next in the list, is the Zabbix configuration file for the server. It needs to know the password which we set for the zabbix database user earlier. Replace secretpassword with your own password which you set for the zabbix database user:

In order to avoid some warnings like: “Less than 25% free in the configuration cache” or “Zabbix icmp pinger processes more than 75% busy”, set some more parameters in the file:

Security considerations

Before we can really use Zabbix, we need to open up the firewall to allow access to the Apache webserver and the webinterface of Zabbix. I’m assuming that outgoing traffic is allowed, otherwise you also need to open up UDP 161 for SNMP and TCP 10050 for the Zabbix agent.

With firewalld:

With iptables:

When using SELinux, we need to allow Apache to communicate with Zabbix:

Start and initialize Zabbix

At this point, most of the configuration should be completed. The only thing that is left is to start the services related to Zabbix and finish the configuration by using the webinterface:

Start the services:

At the time of writing, there was an issue with starting the Zabbix components in combination with SELinux on CentOS 7. This is being fixed but if you experience the following error:

The fix is as follows (more information on:

After starting the services, browse to the following URL: http://<ip or hostname>/zabbix (for example: If all goes well, you should see something like this:

Click next and check if everything is marked with OK:

In the next step, enter the details about the MariaDB user which we created (named zabbix and password secretpassword):

Continue to the next step and provide the desired hostname and instance name:

Go through the pre-installation summary and click next to end the installation:

After clicking finish, you should see the login screen to your new Zabbix installation:

The default username is admin and the default password for that user is zabbix.

At this point the Zabbix server is ready to use.

Basic actions for hosts to monitor:

Now that we have our Zabbix server up and running, we need to have something to monitor. For several types of hosts, there is an agent available. The agent is listening for requests on TCP port  10050 so make sure that this port is open from the Zabbix server to the host to monitor

Install the Zabbix agent on Linux:

Unfortunately, the Zabbix-agent that is part of the base repositories is quite old (version 2.2) and you need to add the Zabbix repositories to the hosts where you would like to install the Zabbix agent.

First add the repositories:

Next, install the agent:

After the installation, set the hostname of the Zabbix-server in /etc/zabbix/zabbix_agentd.conf to match your configuration. Replace by the IP or hostname of your Zabbix-server:

To disable the active checks, clear the value of the ServerActive parameter:

Enable the service and make it persistent:

In case you’re having issues starting the Zabbix agent service, related to permissions for setting the resource limits, please refer to the provide fix above in the installation section for the Zabbix server (last part).

Install the Zabbix agent on Windows

To install the Zabbix agent on a Windows machine, you can find pre-compiled agents for most of the (popular) platforms on the Zabbix website:

The Zabbix 3.2 agent for Windows can be downloaded here:

You can simply extract the archive and edit the following line in the file conf/

Replace it with the hostname or IP of your Zabbix server.

After changing, you can run the following commands (or use them to create a batch file) to install the Zabbix agent as a service:

Enable snmp on Linux

Besides using the Zabbix agent, you can also monitor hosts using SNMP. SNMP isn’t always as fast and flexible as the agent but does the job. Also SNMP can be used for devices that can’t have an agent installed (like a switch):

Install the net-snmp package:

Create the snmpd.conf file in /etc/snmpd/snmpd.conf:

The community string is set as public in the above file, change it to something else if you prefer to.

After configuring, start and enable the service:

Add a host in Zabbix

After installing SNMP or a Zabbix agent on your systems, you can add them in Zabbix as follows:

Log on to the web interface by browsing to http://<ip or hostname>/zabbix (for example: and log in.

Go to Configuration – Hosts and click on “Create host”:

In the next screen, enter a host name, add the host to a group by selecting it on the right side and clicking <<.

When the host has the agent installed, enter the DNS-name or IP for the host in the Agent interfaces. For SNMP, remove the Agent interface and add an SNMP interface containing the same information.

On the templates tab, add ICMP ping and a template that matches the host (for example “Template OS Linux” for a Linux host with a Zabbix agent or “Template SNMP OS Linux” for a Linux host with SNMP).

When using SNMP, you need to enter the community string which you have chose (public in my example above) on the Macros tab:

Finally click Add and the host should be monitored. Don’t panic if you don’t see information immediately give Zabbix some time to discover all items that are relevant for the host.

This should be all it takes to get started with Zabbix. Take some time to explore Zabbix’ functionality and experiment to discover all features.

50 thoughts on “Install and use Zabbix 3.2 on CentOS 7 or RHEL 7

  1. Hello,
    Dependencies are not downloadable…

    [jensd@zab ~]$ sudo yum -y install zabbix-server-mysql zabbix-agent zabbix-web-mysql mysql mysql-server httpd php
    Error: Package: zabbix-server-mysql-2.4.3-1.el7.x86_64 (Zabbix)
    Error: Package: zabbix-server-2.4.3-1.el7.x86_64 (Zabbix)
    Requires: iksemel
    Error: Package: zabbix-server-2.4.3-1.el7.x86_64 (Zabbix)
    Requires: fping >= 3

    • Those packages should be in EPEL, I forgot to mention that you need to add that repository too. I changed my post to include this.

      Thanks for pointing this out.

  2. An excellent and comprehensive post. Zabbix installs come with so many nuances and you covered them all. Great walkthrough!

  3. hello,
    command not run,

    [root@localhost~]# sudo systemctl start mariadb
    failed to issue method call: Unit mariadb.service failed to load; no such file or directory.

    • Did you succesfully install the mysql-server or mariadb packages?
      You can check that with: [jensd@cen ~]$ rpm -qa|grep mariadb

      • Had the same problem, fixed this with :

        yum update -y
        yum install mariadb-server

        Very great tutorial !!! Thank you

        • Hi,

          Thanks for pointing this out, no idea why it worked correctly at the time of writing the post. I edited this.

  4. Hi, you tutorial is great!
    i follow step by step your tutorial but when i try to run zabbix in mozilla to my local server or http://localhost/zabbix we recive a error message
    The requested URL /zabbix was not found on this server.

    i don’t have any problem in the install process.
    Can you help me?
    Thanks you very much
    Greeting from Chile.

    • Hi,

      Are you sure that the webserver is running? Try a netstat -tlpn and look for port 80, check the output of systemctl status httpd or check the contents of /var/log/httpd/.
      If the webserver is running, check if the file /etc/httpd/conf.d/zabbix.conf exists and that it isn’t a security-related problem (like SELinux or permissions on directories listed in /etc/httpd/conf.d/zabbix.conf).
      You could try to temporary disable SELinux with setenforce 0

  5. Best guide for fedora-21 with zabbix-2.2.8. Up and running now on 2nd attempt after wrestling with lesser guides.

    Much thanks for a comprehensive zabbix installation tutorial.

  6. I have done zabbix installation, but I got error Zabbix server is not running: The information display may not be current.

    • This is probably related to SELinux. Did you run sudo setsebool -P httpd_can_connect_zabbix=1 ? Can you try to (temporarily) turn of SELinux and try again?

  7. The install went without issue. However using Zabbix 2.4.4, I receive the following error when starting the Zabbix Server for the first time:

    Process: 14313 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=killed, signal=SEGV)
    CGroup: /system.slice/zabbix-server.service
    └─14316 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf

    I have created a second virtual machine and run the install a second time and received the same result so at least what I am doing is consistent.

    Thanks for the help.


  8. I install zabbix but I receive the following error:

    [root@srv-nms02 /]# systemctl start zabbix-server
    Job for zabbix-server.service failed. See ‘systemctl status zabbix-server.service’ and ‘j
    ournalctl -xn’ for details.

    [root@srv-nms02 /]# systemctl status zabbix-server.service
    zabbix-server.service – Zabbix Server
    Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; disabled)
    Active: failed (Result: start-limit) since Tue 2015-04-07 00:54:14 CEST; 6s ago
    Process: 13940 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=killed, signal=SEGV

    Apr 07 00:54:14 srv-nms02 systemd[1]: Failed to start Zabbix Server.
    Apr 07 00:54:14 srv-nms02 systemd[1]: Unit zabbix-server.service entered failed state.
    Apr 07 00:54:14 srv-nms02 systemd[1]: zabbix-server.service holdoff time over, sche…rt.
    Apr 07 00:54:14 srv-nms02 systemd[1]: Stopping Zabbix Server…
    Apr 07 00:54:14 srv-nms02 systemd[1]: Starting Zabbix Server…
    Apr 07 00:54:14 srv-nms02 systemd[1]: zabbix-server.service start request repeated …rt.
    Apr 07 00:54:14 srv-nms02 systemd[1]: Failed to start Zabbix Server.
    Apr 07 00:54:14 srv-nms02 systemd[1]: Unit zabbix-server.service entered failed state.
    Hint: Some lines were ellipsized, use -l to show in full.

    [root@srv-nms02 /]# journalctl -xn
    — Logs begin at Thu 2015-04-02 12:49:28 CEST, end at Tue 2015-04-07 00:55:16 CEST. —
    Apr 07 00:55:16 srv-nms02 systemd[1]: zabbix-server.service: control process exited, code
    Apr 07 00:55:16 srv-nms02 systemd[1]: Failed to start Zabbix Server.
    — Subject: Unit zabbix-server.service has failed
    — Defined-By: systemd
    — Support:

    — Unit zabbix-server.service has failed.

    — The result is failed.
    Apr 07 00:55:16 srv-nms02 systemd[1]: Unit zabbix-server.service entered failed state.
    Apr 07 00:55:16 srv-nms02 kernel: zabbix_server[13998]: segfault at 18 ip 00007ff445c9bc0
    Apr 07 00:55:16 srv-nms02 systemd[1]: zabbix-server.service holdoff time over, scheduling
    Apr 07 00:55:16 srv-nms02 systemd[1]: Stopping Zabbix Server…
    — Subject: Unit zabbix-server.service has begun shutting down
    — Defined-By: systemd
    — Support:

    — Unit zabbix-server.service has begun shutting down.
    Apr 07 00:55:16 srv-nms02 systemd[1]: Starting Zabbix Server…
    — Subject: Unit zabbix-server.service has begun with start-up
    — Defined-By: systemd
    — Support:

    — Unit zabbix-server.service has begun starting up.
    Apr 07 00:55:16 srv-nms02 systemd[1]: zabbix-server.service start request repeated too qu
    Apr 07 00:55:16 srv-nms02 systemd[1]: Failed to start Zabbix Server.
    — Subject: Unit zabbix-server.service has failed
    — Defined-By: systemd
    — Support:

    — Unit zabbix-server.service has failed.

    — The result is failed.
    Apr 07 00:55:16 srv-nms02 systemd[1]: Unit zabbix-server.service entered failed

    can you hel me?


  9. The problem is gnutls.
    I used gnutls-3.1.18-10.el7_0.x86_64.rpm version and working properly.

    [root@srv-nms02 /]# systemctl status zabbix-server.service
    zabbix-server.service – Zabbix Server
    Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; disabled)
    Active: active (running) since Wed 2015-04-08 09:47:20 CEST; 2min 6s ago
    Process: 7496 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
    Main PID: 7498 (zabbix_server)

  10. I tried to downgrade the gnutls and I get error saying “no package gnutls-3.1.18-10.el7_0.x86_64.rpm available”…. please help on how to get this correct package downloaded so I can start Zabbix server on centOS 7. Thanks.

  11. I too struggled with the CentOS 7 install and gnutls. Here’s what I had to do:

    1. Get the CentOS 7 DVD or Everything iso and mount it in /media/CentOS. Make
    sure you can list the contents.
    2. Create a .repo file in /etc/yum.repos.d. Call it something like local.repo. It should
    contain the following:
    name=Local Repository
    3. As sudo, do: yum downgrade gnutls and it should respond with something like:
    Resolving Dependencies
    –> Running transaction check
    —> Package gnutls.x86_64 0:3.1.18-10.el7_0 will be a downgrade
    —> Package gnutls.x86_64 0:3.3.8-12.el7 will be erased

    4. Disable the local repo by setting enabled=0 in your local.repo from #2 above.

    After a lot of googling and head scratching, this worked for me. Hope it helps
    someone else.

    Good luck.

    • Oops! I forgot. Put this in /etc/yum.conf:
      If you dont (I didn’t:-0), gnutls will be upgraded to the non-usable one.

      By the way Jens, this is probably one of the most helpful posts I’ve seen to date. Thank you for sharing.

  12. Hello I tried following your step by step installation for zabix.
    I am stuck here :
    [root@src-install-01 ~]# sudo yum -y install zabbix-server-mysql zabbix-web-mysql mysql mariadb-server httpd php

    Error: Package: zabbix-web-2.4.5-1.el7.noarch (zabbix)
    Requires: php >= 5.3
    Error: Package: zabbix-web-2.4.5-1.el7.noarch (zabbix)
    Requires: php-gd
    Error: Package: zabbix-web-mysql-2.4.5-1.el7.noarch (zabbix)
    Requires: php-mysql
    Error: Package: zabbix-web-2.4.5-1.el7.noarch (zabbix)
    Requires: php-mbstring
    Error: Package: zabbix-web-2.4.5-1.el7.noarch (zabbix)
    Requires: php-xml
    Error: Package: zabbix-web-2.4.5-1.el7.noarch (zabbix)
    Requires: dejavu-sans-fonts
    Error: Package: zabbix-web-2.4.5-1.el7.noarch (zabbix)
    Requires: php-bcmath

    Please help.

    • Hi, these missing packages are part of the standard CentOS 7 Base and update repositories so my guess is that something’s wrong with your repo configuration.

      You could try to verify the files in /etc/yum.repos.d or do a yum clean all to be sure.

  13. cat > /etc/yum.repos.d/zabbix.repo <<!EOF

    • This depends of the version of Zabbix that gets installed. I can’t update this post for every new version :)

  14. Hi,
    Using all the incredible information in this post I have been able to install and configure Zabbix 2.4.5 on CentOS 7.0. Thanks everyone. I tried CentOS 7.0 as I too was having trouble with gnutls and couldn’t resolve it and for now want to get up and running with Zabbix to trail and learn Zabbix.

    However, when I restart my server Mariadb, Zabbix-Server, and Httpd don’t seem to have automatically started. If I go to terminal and enter the start commands listed in this post I can then connect to Zabbix. I struggle a bit with Linux. Could someone point me in the right direction to have these services automatically start after a server reboot. I don’t think I missed anything in the post as I have now been through it many times to get this far.

    Any help would be appreciated,
    Many thanks

    • Hi,

      You can enable the services (start on boot) as follows:
      [jensd@zab ~]$ sudo systemctl enable zabbix-agent
      [jensd@zab ~]$ sudo systemctl enable zabbix-server
      [jensd@zab ~]$ sudo systemctl enable httpd

      I forgot to mention this in my post.

    • Hi,

      I know that Zabbix works fine with PostgreSQL too. It’s not a big difference from the setup in this post but I don’t plan to especially write it.

  15. i followed all step, it doesn’t work fine for me.
    i used centOS server, on the server i have created three folder on var/www , ,

    i wanted to create zabbix inside the

    so i created zabbix folder inside, which mean when access will point open up the zabbix interface.

    please advice me how to do it..
    Appreciate that if you could guild me.

    • You’ll have to adjust your Apache config in /etc/httpd/ to add an alias for You’ll need to point it to the same directory as in “/etc/httpd/conf.d/zabbix.conf” (/usr/share/zabbix)

  16. i followed all the step except SELinux. It doesn’t work for me.
    should i enable SELinux or anyway to solve this?

    Looking forward to get the answer soon..
    Thank you

    • Either you need to execute the steps listed in the post to allow certain SELinux restrictions or disable SELinux completely.

  17. for zabbix-server does not start” problem if you cannot downgrade gnutls package try upgrading trousers package , find the newer one related to your distribution from rpmfind website and update it with rpm -Uvh package it solved my problem.

  18. Job for zabbix-server.service failed. See ‘systemctl status zabbix-server.service’ and ‘journalctl -xn’ for details.

    i need help with this

  19. This was very helpful. Thank you!

    Quick question. when I restart the CentOS machine Zabbix doesn’t automatically load. Even after I give it the commands to start the Zabbix server I still cannot connect. Could it be that I need to start MariaDB?

    • I think I forgot to mention this in my post but you should enable the following services to start at boot:
      $ systemctl enable httpd
      $ systemctl enable zabbix-server
      $ systemctl enable zabbix-agent
      $ systemctl enable mariadb

  20. Just wanted to say thanks for a fantastic article that really saved me a whole bunch of time!!!

  21. Wow, thanks for that!! I had installed it before on Centos 6.5 and the first time was a real pain. Wanted to try on 7 and found this post. Worked like a charm

  22. Dear all,
    How are you all? I am facing a problem during configuration of zabbix 3.0 in my rhel7.2
    I have configured all the steps of zabbix 3.0 but when i tried to start the zabbix-server there is an error message shown that is
    “Job for zabbix-server.service failed because the control process exited with error code. See “systemctl status zabbix-server.service” and “journalctl -xe” for details.”

    systemctl status zabbix-server -l
    ● zabbix-server.service – Zabbix Server
    Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
    Active: activating (auto-restart) (Result: exit-code) since Sun 2016-04-17 20:18:03 BDT; 909ms ago
    Process: 17817 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=127)
    Apr 17 20:18:03 rhel7 systemd[1]: Failed to start Zabbix Server.
    Apr 17 20:18:03 rhel7 systemd[1]: Unit zabbix-server.service entered failed state.
    Apr 17 20:18:03 rhel7 systemd[1]: zabbix-server.service failed

    can anyone help me to find out the problem,thnx in advance

    • Hi,

      I have included the fix for this issue in the post.
      Here’s a summary:
      [jensd@zab ~]$ sudo yum install -y policycoreutils-python

      [jensd@zab ~]$ sudo cat /var/log/audit/audit.log | grep zabbix_agentd | grep denied | tail -1 | audit2allow -M zabbix_agent_resourcelimit
      ******************** IMPORTANT ***********************
      To make this policy package active, execute:

      semodule -i zabbix_agent_resourcelimit.pp

      [jensd@zab ~]$ sudo semodule -i zabbix_agent_resourcelimit.pp
      [jensd@zab ~]$ sudo systemctl start zabbix-agent
      [jensd@zab ~]$ sudo cat /var/log/audit/audit.log | grep zabbix_server | grep denied | tail -1 | audit2allow -M zabbix_server_resourcelimit
      ******************** IMPORTANT ***********************
      To make this policy package active, execute:

      semodule -i zabbix_server_resourcelimit.pp

      [jensd@zab ~]$ sudo semodule -i zabbix_server_resourcelimit.pp
      [jensd@zab ~]$ sudo systemctl start zabbix-server

Leave a Reply

Your email address will not be published. Required fields are marked *