Zabbix server: Difference between revisions

From Phobos Wiki
Jump to navigation Jump to search
(Uus lehekülg: '= Martem Zabbix Server = == Intro == There is a Zabbix server PC located in the "server room" (near the fridge). Zabbix software itself is run in a vmware virtual machine on th...')
 
No edit summary
Line 3: Line 3:
== Intro ==
== Intro ==


There is a Zabbix server PC located in the "server room" (near the fridge). Zabbix software itself is run in a vmware virtual machine on that PC in the background. It is started a system boot from /etc/rc.local by the line
There is a Zabbix server PC located in the "server room" (near the fridge). Zabbix software itself is run in a VMware virtual machine on that PC in the background. It is started a system boot from /etc/rc.local by the line.


<pre>
<pre>
Line 9: Line 9:
</pre>
</pre>


Note that for some reason running that line in text mode (no gui) (f.ex. Ctrl + Alt + F1) wont work. The process will be seeen in the background. but the vm won't respond (You will be unable to ping 10.0.0.177 - static ip assigned to the virtual machine).
Note that for some reason running that line in text mode (no gui) (f.ex. Ctrl + Alt + F1) wont work. The process will be seen in the background. but the vm won't respond (You will be unable to ping 10.0.0.177 - static ip assigned to the virtual machine).


== Zabbix server info ==
== Zabbix server info ==
Line 15: Line 15:
IP: 10.0.0.159
IP: 10.0.0.159


Has tightvnc installed which is run at system boot. script location: /etc/init/vncserver
Has tightvnc installed which is run at system boot. Script location: /etc/init/vncserver
 
vnc port: 5901
vnc port: 5901


This machine has 2x2TB HDD in RAID1+0 w/ far fetched layout with LVM over them
This machine has 2x2TB HDD in RAID1+0 w/ far fetched layout with LVM.


<pre>
<pre>
Line 61: Line 62:
Linux zabbixsrv 3.2.0-75-generic #110-Ubuntu SMP Tue Dec 16 19:11:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Linux zabbixsrv 3.2.0-75-generic #110-Ubuntu SMP Tue Dec 16 19:11:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
</pre>
</pre>
== Known issues ==
Right after the installation the update was run, which successfully updated the kernel version from 3.2.0.75 to 3.2.0.76 and as usual grub boot loader was updated accordingly (3.2.0.76 as default and 3.2.0.75 was moved to the previous versions subcategory). After that the system stopped booting giving a black screen with no error codes. After manually booting to
the old kernel version I modified /boot/grub/grub.cfg file and set the default boot option from 0 (the first one on the list) to "2>0", which means first option in the third item (a subcategory in our case). This means that the older version is being loaded at the moment. Such modification isn't dynamic, as soon as some one updates to a newer kernel, the not working 3.2.0.76 will be as the first option in the third item and the system might not boot again.


== Zabbix virtual machine info ==
== Zabbix virtual machine info ==
Line 91: Line 97:
</pre>
</pre>


[[Kasutaja:MarkTomm|MarkTomm]] 12. veebruar 2015, kell 16:08 (EET)
[[Kasutaja:MarkTomm|MarkTomm]] 12. veebruar 2015, kell 16:22 (EET)

Revision as of 14:22, 12 February 2015

Martem Zabbix Server

Intro

There is a Zabbix server PC located in the "server room" (near the fridge). Zabbix software itself is run in a VMware virtual machine on that PC in the background. It is started a system boot from /etc/rc.local by the line.

vmrun -T player start /zabbix/Zabbix/Zabbix2.4.vmx nogui &

Note that for some reason running that line in text mode (no gui) (f.ex. Ctrl + Alt + F1) wont work. The process will be seen in the background. but the vm won't respond (You will be unable to ping 10.0.0.177 - static ip assigned to the virtual machine).

Zabbix server info

IP: 10.0.0.159

Has tightvnc installed which is run at system boot. Script location: /etc/init/vncserver

vnc port: 5901

This machine has 2x2TB HDD in RAID1+0 w/ far fetched layout with LVM.

roland@zabbixsrv:~$ lsblk
NAME                                       MAJ:MIN RM   SIZE RO TYPE   MOUNTPOINT
sda                                          8:0    0   1.8T  0 disk   
|-sda1                                       8:1    0     1M  0 part   
|-sda2                                       8:2    0    14G  0 part   
| `-md1                                      9:1    0    14G  0 raid10 [SWAP]
`-sda3                                       8:3    0   1.8T  0 part   
  `-md0                                      9:0    0   1.8T  0 raid10 
    |-zabbix-root (dm-0)                   252:0    0  46.6G  0 lvm    /
    |-zabbix-home (dm-1)                   252:1    0 139.7G  0 lvm    /home
    |-zabbix-var (dm-2)                    252:2    0 139.7G  0 lvm    /var
    |-zabbix-tmp (dm-3)                    252:3    0  18.6G  0 lvm    /tmp
    `-zabbix-zabbix_virtual_machine (dm-4) 252:4    0   200G  0 lvm    /zabbix
sdb                                          8:16   0   1.8T  0 disk   
|-sdb1                                       8:17   0     1M  0 part   
|-sdb2                                       8:18   0    14G  0 part   
| `-md1                                      9:1    0    14G  0 raid10 [SWAP]
`-sdb3                                       8:19   0   1.8T  0 part   
  `-md0                                      9:0    0   1.8T  0 raid10 
    |-zabbix-root (dm-0)                   252:0    0  46.6G  0 lvm    /
    |-zabbix-home (dm-1)                   252:1    0 139.7G  0 lvm    /home
    |-zabbix-var (dm-2)                    252:2    0 139.7G  0 lvm    /var
    |-zabbix-tmp (dm-3)                    252:3    0  18.6G  0 lvm    /tmp
    `-zabbix-zabbix_virtual_machine (dm-4) 252:4    0   200G  0 lvm    /zabbix

At first the ide was to migrate zabbix from its virtual machine to this PC so the root /home /var and /tmp logical volumes were made with their sepicific sizes. Later it was decided that zabbix will run in its virtual machine, so I made a 200GB /zabbix logical volume and put everything related to the vm there.

General Info

roland@zabbixsrv:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 12.04.5 LTS
Release:        12.04
Codename:       precise
roland@zabbixsrv:~$ uname -a
Linux zabbixsrv 3.2.0-75-generic #110-Ubuntu SMP Tue Dec 16 19:11:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Known issues

Right after the installation the update was run, which successfully updated the kernel version from 3.2.0.75 to 3.2.0.76 and as usual grub boot loader was updated accordingly (3.2.0.76 as default and 3.2.0.75 was moved to the previous versions subcategory). After that the system stopped booting giving a black screen with no error codes. After manually booting to the old kernel version I modified /boot/grub/grub.cfg file and set the default boot option from 0 (the first one on the list) to "2>0", which means first option in the third item (a subcategory in our case). This means that the older version is being loaded at the moment. Such modification isn't dynamic, as soon as some one updates to a newer kernel, the not working 3.2.0.76 will be as the first option in the third item and the system might not boot again.

Zabbix virtual machine info

All the files related to zabbix virtual machine are located at /zabbix

The software used to run the virtual machine:

VMware-Workstation-Full-11.0.0-2305329.x86_64

Install binary should be located at /home/roland

Using WMware Player + WMware VIX utilities as suggested in most tutorials gave an error, because of some misconfigurations in some conf file. It seemed like the latest versions were buggy at that time.

General Info

IP: 10.0.0.177

martem@zabbix:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 12.04.4 LTS
Release:        12.04
Codename:       precise
martem@zabbix:~$ uname -a
Linux zabbix 3.2.0-63-generic #95-Ubuntu SMP Thu May 15 23:05:57 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

MarkTomm 12. veebruar 2015, kell 16:22 (EET)