Skip to main content

Setting up Zabbix with PostgreSQL 9.6 on Debian9

I recently decided to change my internal monitoring at home from nagios to Zabbix. The main reason was that I won't have to write config files with zabbix.

I used a raspberry pi 3 running raspbian 9 which I had idling around and for homeuse this should be enough since I will only monitor around 4-5 devices using the agent. The shown steps should be the same on a updated debian9 system. Anyway, I'd suggest to push the database (in my case postgresql) to a separate HDD or anything else not on the sd-card since the db will have a lot of write-cycles which will tear the flash down very quickly.

I checked the internet for some good HowTo's but even the documentation on the zabbix page was missing some information. So I decided to write down the steps it took me to get up and running with zabbix.

First you'll have to install the zabbix-server-pgsql package and if you want the webfrontend, also install the zabbix-webfrontend-php package.
 [archy@zabbix ~]$ sudo apt-get -y install zabbix-server-pgsql zabbix-frontend-php  
Once the installation is finished, we can continue setting up the database.
 [archy@zabbix ~]$ sudo su - postgres  
 [postgres@zabbix ~]$ psql  
 postgres=# create user zabbix with password 'secure_password';  
 postgres=# create database zabbix;  
 postgres=# alter database zabbix owner to zabbix;  
Now that we have the zabbix-database and zabbix-user which owns the database, it's time to feed it informations and schemes.
 [archy@zabbix ~]$ zcat /usr/share/zabbix-server-pgsql/schema.sql.gz | psql -h 127.0.0.1 -p 5432 -U zabbix -W zabbix 
 Password for user zabbix:  
 [archy@zabbix ~]$ zcat /usr/share/zabbix-server-pgsql/images.sql.gz | psql -h 127.0.0.1 -p 5432 -U zabbix -W zabbix 
 Password for user zabbix:  
 [archy@zabbix ~]$ zcat /usr/share/zabbix-server-pgsql/data.sql.gz | psql -h 127.0.0.1 -p 5432 -U zabbix -W zabbix 
 Password for user zabbix:  
If the databasepreparation is finished, we'll have to make the server aware of the config changes.
Note that I'm hosting the postgres-instance responsible for zabbix on the same server as the zabbix-server itself.
 [archy@zabbix ~]$ sudo vim /etc/zabbix/zabbix_server.conf  
 LogFile=/var/log/zabbix-server/zabbix_server.log  
 PidFile=/var/run/zabbix/zabbix_server.pid  
 DBHost=127.0.0.1  
 DBName=zabbix  
 DBUser=zabbix  
 DBPassword=secure_password  
 Timeout=4  
 AlertScriptsPath=/etc/zabbix/alert.d/  
 FpingLocation=/usr/bin/fping  
 LogSlowQueries=3000  
 Include=/etc/zabbix/zabbix_server.conf.d/*.conf  
Next, we'll have to adjust the zabbix-frontend.php config with our timezone. For my usecase I'll leave the rest of the config default for now.
 [archy@zabbix ~]$ sudo vim /usr/share/zabbix/conf/zabbix.conf.php  
 <IfModule mod_alias.c>  
   Alias /zabbix /usr/share/zabbix  
 </IfModule>  
 <Directory "/usr/share/zabbix">  
   Options FollowSymLinks  
   AllowOverride None  
   Require all granted  
   <IfModule mod_php5.c>  
     php_value max_execution_time 300  
     php_value memory_limit 128M  
     php_value post_max_size 16M  
     php_value upload_max_filesize 2M  
     php_value max_input_time 300  
     php_value always_populate_raw_post_data -1  
     php_value date.timezone Europe/Prague  
   </IfModule>  
   <IfModule mod_php7.c>  
     php_value max_execution_time 300  
     php_value memory_limit 128M  
     php_value post_max_size 16M  
     php_value upload_max_filesize 2M  
     php_value max_input_time 300  
     php_value date.timezone Europe/Prague  
   </IfModule>  
 </Directory>  
 <Directory ~ "^/usr/share/zabbix/(conf|app|include|local)/">  
   Require all denied  
   <files *.php>  
     Require all denied  
   </files>  
 </Directory>  
Now that the config for the site is done, we'll have to make apache aware of the site. You can do that by creating a file in /etc/apache2/sites-available/ or by simply copying the file like I did.
 [archy@zabbix ~]$ sudo cp /usr/share/doc/zabbix-frontend-php/examples/apache.conf /etc/apache2/sites-available/zabbix.conf  
Now let's make apache aware of the site:
 [archy@zabbix ~]$ sudo ln -s /etc/apache2/sites-available/zabbix.conf /etc/apache2/sites-enabled/zabbix.conf  
Make sure the necessary services are enabled so they get started at boot by systemd:
 [archy@zabbix ~]$ sudo systemctl enable zabbix-server.service  
 [archy@zabbix ~]$ sudo systemctl enable apache2.service  
 [archy@zabbix ~]$ sudo systemctl enable postgresql.service  
To finish, make the services aware of the config changes:
 [archy@zabbix ~]$ sudo systemctl restart zabbix-server.service  
 [archy@zabbix ~]$ sudo systemctl restart apache2.service  
 [archy@zabbix ~]$ sudo systemctl restart postgresql.service  

That concludes the setup on a debian9 based system. You can now login to your zabbix-instance by pointing your browser to the fqdn / ip of the server you've configured zabbix on.

You'll be greeted by this gui:

Feel free to comment and / or suggest a topic.

Comments

Popular posts from this blog

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 ). 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"; controls { inet 172.31.0.1 port 953 allow { 172.31.0.5; } keys ...

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...