As an alternative to setting up manually or reusing existing server for Zabbix, users may download Zabbix appliance.
To get started, boot the appliance and point your browser at the IP it has received over DHCP.
Zabbix appliance versions are based upon the following OpenSUSE versions:
|Zabbix appliance version||OpenSUSE version|
It is available in the following formats:
It has Zabbix server configured and running on MySQL, as well as frontend available.
The appliance has been built using SUSE Studio.
Most notably, all utility names and file names have been changed to use a dash instead of an underscore to comply with distribution guidelines. See changes to Zabbix configuration for more information.
There are some changed applied to the base OpenSUSE configuration.
By default the appliance uses DHCP to obtain IP address. To specify a static IP address:
To configure DNS, add nameserver entries in /etc/resolv.conf, specifying each nameserver on its own line: nameserver 192.168.1.2.
Alternatively, just use yast configuration utility to update network settings.
By default the appliance uses UTC for the system clock. To change the time zone, copy appropriate file from /usr/share/zoneinfo to /etc/localtime, for example:
cp /usr/share/zoneinfo/Europe/Riga /etc/localtime
Appliance Zabbix setup has the following passwords and other configuration changes:
To change the database user password it has to be changed in the following locations:
If you are running live CD version of the appliance or for some other reason can't have persistent storage, you can create a backup of whole database, including all configuration and gathered data.
To create the backup, run:
mysqldump zabbix | bzip2 -9 > dbdump.bz2
Now you can transfer file dbdump.bz2 to another machine.
To restore from the backup, transfer it to the appliance and execute:
bzcat dbdump.bz2 | mysql zabbix
Access to frontend by default is allowed from:
Root (/) is redirected to /zabbix on the webserver, thus frontend can be accessed both as http://<host> and http://<host>/zabbix.
This can be customised in /etc/apache2/conf.d/zabbix.conf. You have to restart webserver after modifying this file. To do so, log in using SSH as root user and execute:
service apache2 restart
By default, only ports 22 (SSH), 80 (HTTP) and 443 (HTTPS) are open. To open additional ports - for example, Zabbix server and agent ports - modify iptables rules with SuSEfirewall2 utility:
SuSEfirewall2 open EXT TCP zabbix-trapper zabbix-agent
Then reload the firewall rules:
Zabbix server is compiled with support for the following:
In the provided configuration Zabbix server itself is monitored with the help of locally installed agent for some base parameters, additionally Zabbix frontend is monitored as well using web monitoring.
Basic MySQL monitoring is demonstrated using user parameters. Operations per second and bandwidth graphs are provided.
Starting with Zabbix 2.4, the appliance packages may be upgraded. To do so, run:
zypper ref zypper up
The last command will prompt to accept repository signing key (this has to be done only once):
New repository or package signing key received: Key ID: 6F1385F1A0875A36 Key Name: home:zabbix OBS Project <home:firstname.lastname@example.org> Key Fingerprint: DF41712BF09B250CF033AC2D6F1385F1A0875A36 Key Created: Thu 11 Sep 2014 12:36:12 EEST Key Expires: Sat 19 Nov 2016 11:36:12 EET Repository: home:zabbix_openSUSE_13_1 Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a
Accept the key by entering 'a'. Confirm package upgrade. After the upgrade, it is necessary to manually restart Zabbix daemons. To do so, run:
rczabbix-server restart rczabbix-agentd restart
Bash completion for Zabbix daemons and utilities has been included since the appliance version 2.4.6, but was not included with the previous versions. To install it, run:
zypper in zabbix24-bash-completion
Confirm the installation and close your login session, then log in again.
Appropriate init scripts are provided. To control Zabbix server, use any of these:
service zabbix-server status rczabbix-server status
Replace server with agentd for Zabbix agent daemon.
Available diskspace on the appliance might not be sufficient. In that case it is possible to expand the disk. To do so, first expand the block device in your virtualisation environment, then follow these steps.
Start fdisk to change the partition size. As root, execute:
This will start fdisk on disk sda. Next, switch to sectors by issuing:
Then delete the existing partition and create new one with desired size. In majority of cases you will accept the available maximum, which will expand the filesystem to whatever size you made available for the virtual disk. To do so, enter the following sequence in fdisk prompt:
d n p 1 (accept default 63) (accept default max)
If you wish to leave some space for additional partitions (swap etc), you can enter another value for last sector. When done, save the changes by issuing:
Reboot the virtual machine (as the partition we modified is in use currently). After reboot, filesystem resizing can take place.
That's it, filesystem should be grown to the partition size now.
To use images in Xen server, run:
xm create -c file-with-suffix.xenconfig
See the following pages for more information on using Xen images:
Converting image for XenServer
To use Xen images with Citrix Xenserver you have to convert the disk image. To do so:
xe vdi-list params=all
xe vdi-import filename="image.raw" uuid="<UUID>"
Instructions from Brian Radford blog.
The images in vmdk format are usable directly in VMware Player, Server and Workstation products. For use in ESX, ESXi and vSphere they must be converted using VMware converter.
See http://en.opensuse.org/openSUSE:SUSE_Studio_Disc_Image_Howtos for more information on disk images.
Windows archive management software is known to mishandle the appliance archives. If extraction fails, try different software. Open source tool 7-zip might work.
In some environments, the appliance might obtain IPv6 addresses (for example, for operating system updates), but be unable to use IPv6. To disable IPv6, add net.ipv6.conf.all.disable_ipv6 = 1 in /etc/sysctl.conf and restart the appliance.
If appliance seems to stop booting while loading initrd, more memory might be needed - 256MB has been shown to be too little. At least 512MB of memory is suggested.