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|
* Initial 2.0.4 appliance builds were with OpenSUSE 12.1, final builds are with OpenSUSE 12.2.
It is available in the following formats:
* Since appliance 2.0.5.
It has Zabbix server configured and running on MySQL, as well as frontend available.
The appliance has been built using SUSE Studio.
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:
If you change frontend password, do not forget to update password setting web monitoring (Configuration → Web).
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
Make sure that Zabbix server is stopped while performing the restore.
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 two ports are open - 22 (SSH) and 80 (HTTP). 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:
SuSEfirewall2 stop SuSEfirewall2 start
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.
|<| |<| |-|
Note that web frontend monitoring logs in - this can add lots of entries to the audit log.
Appropriate init scripts are provided. To control Zabbix server, use any of these:
service zabbix_server status rczabbix_server status /etc/init.d/zabbix_server status
Replace server with agentd for Zabbix agent daemon.
There is a scheduled script, run from the crontab every 10 minutes that restarts Zabbix server if it is not running, /var/lib/zabbix/bin. It logs timestamped problems and starting attempts at /var/log/zabbix/server_problems.log.
Make sure to disable this crontab entry if stopping of Zabbix server is desired.
Create a backup of all data before attempting any of the steps.
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:
Don't disable DOS compatibility mode by entering c. Proceeding with it disabled will damage the partition.
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.
/usr/share/zabbix/locale/make_mo.sh rcapache2 restart