Zabbix usage summary, zabbix Summary

Zabbix usage summary, zabbix Summary

1. Failed to start zabbix-server on CentOS 7. The error message in/var/log/messages is as follows:

Feb 22 12:56:43 mysql-server1 systemd: Starting Zabbix Server with MySQL DB...Feb 22 12:56:43 mysql-server1 kernel: zabbix_server[1599]: segfault at 18 ip 00007fce09ca6bd0 sp 00007fffa39b7808 error 4 in libpthread-2.17.so[7fce09c9d000+16000]Feb 22 12:56:43 mysql-server1 systemd: zabbix-server-mysql.service: control process exited, code=killed status=11Feb 22 12:56:43 mysql-server1 systemd: Failed to start Zabbix Server with MySQL DB.Feb 22 12:56:43 mysql-server1 systemd: Unit zabbix-server-mysql.service entered failed state.

Solution:

# Rpm-Uvh -- force ftp://bo.mirror.garr.it/1/slc/centos/7.0.1406/updates/x86_64/Packages/gnutls-3.1.18-10.el7_0.x86_64.rpm

Retrieving ftp://bo.mirror.garr.it/1/slc/centos/7.0.1406/updates/x86_64/Packages/gnutls-3.1.18-10.el7_0.x86_64.rpmPreparing...                          ################################# [100%]Updating / installing...   1:gnutls-3.1.18-10.el7_0           ################################# [ 50%]Cleaning up / removing...   2:gnutls-3.3.8-12.el7              ################################# [100%]

The RPM package is:

Http://rpm.pbone.net/index.php3/stat/4/idpl/27966545/dir/centos_7/com/gnutls-3.1.18-10.el7_0.x86_64.rpm.html

 

2. Zabbix official sources and epel sources for CentOS 7

# Rpm-ivh http://repo.zabbix.com/zabbix/2.2/rhel/7/x86_64/zabbix-2.2.11-1.el7.x86_64.rpm

# Rpm-ivh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm

The former is the official source of Zabbix, and the latter is epel. The former only installs zabbix, and the latter is the yum source of epel. The epel source contains the software package of zabbix, the two can only use one of them. If both are installed, conflicts will be reported during subsequent installation.

Transaction check error:  file /var/log/zabbix from install of zabbix22-agent-2.2.11-1.el7.x86_64 conflicts with file from package zabbix-2.2.11-1.el7.x86_64

The zabbix package contained in epel is as follows:

zabbix20.x86_64                                             2.0.16-1.el7                               epel              zabbix20-agent.x86_64                                       2.0.16-1.el7                               epel              zabbix20-proxy.noarch                                       2.0.16-1.el7                               epel              zabbix20-proxy-mysql.x86_64                                 2.0.16-1.el7                               epel              zabbix20-proxy-pgsql.x86_64                                 2.0.16-1.el7                               epel              zabbix20-proxy-sqlite3.x86_64                               2.0.16-1.el7                               epel              zabbix20-server.noarch                                      2.0.16-1.el7                               epel              zabbix20-server-mysql.x86_64                                2.0.16-1.el7                               epel              zabbix20-server-pgsql.x86_64                                2.0.16-1.el7                               epel              zabbix20-web.noarch                                         2.0.16-1.el7                               epel              zabbix20-web-mysql.noarch                                   2.0.16-1.el7                               epel              zabbix20-web-pgsql.noarch                                   2.0.16-1.el7                               epel              zabbix22.x86_64                                             2.2.11-1.el7                               epel              zabbix22-agent.x86_64                                       2.2.11-1.el7                               epel              zabbix22-dbfiles-mysql.noarch                               2.2.11-1.el7                               epel              zabbix22-dbfiles-pgsql.noarch                               2.2.11-1.el7                               epel              zabbix22-dbfiles-sqlite3.noarch                             2.2.11-1.el7                               epel              zabbix22-proxy.noarch                                       2.2.11-1.el7                               epel              zabbix22-proxy-mysql.x86_64                                 2.2.11-1.el7                               epel              zabbix22-proxy-pgsql.x86_64                                 2.2.11-1.el7                               epel              zabbix22-proxy-sqlite3.x86_64                               2.2.11-1.el7                               epel              zabbix22-server.noarch                                      2.2.11-1.el7                               epel              zabbix22-server-mysql.x86_64                                2.2.11-1.el7                               epel              zabbix22-server-pgsql.x86_64                                2.2.11-1.el7                               epel              zabbix22-web.noarch                                         2.2.11-1.el7                               epel              zabbix22-web-mysql.noarch                                   2.2.11-1.el7                               epel              zabbix22-web-pgsql.noarch                                   2.2.11-1.el7                               epel    

 

3. Use zabbix_get to verify whether the Agent configuration is correct.

# zabbix_get -s 192.168.244.144 -p 10050 -k system.uanmeZBX_NOTSUPPORTED

ZBX_NOTSUPPORTED indicates that the monitoring metrics are faulty.

# zabbix_get -s 192.168.244.144 -p 10050 -k agent.ping1

 

4. 59635: 20160223: 161315.258 no active checks on server [192.168.244.146: 10051]: host [192.168.244.146] not found

Cause: Hostname in/etc/zabbix_agentd.conf does not match the Name on the zabbix web page Monitoring-> Configuration-> Hosts page

 

5. The error "ZBX_NOTSUPPORTED" is reported when system. run is executed.

[root@localhost ~]# zabbix_get -s 192.168.244.10 -k system.run['df -h']ZBX_NOTSUPPORTED

Cause: the default EnableRemoteCommands value in the configuration file of the client is 0.

After enabling,

[root@localhost ~]# zabbix_get -s 192.168.244.10 -k system.run['df -h']Filesystem      Size  Used Avail Use% Mounted on/dev/sda3        18G  8.7G  8.0G  53% /tmpfs           238M     0  238M   0% /dev/shm/dev/sda1       190M   27M  154M  15% /boot

 

6. Differences between passive mode and Active Mode

Passive Mode:

1> Server opens a TCP connection

2> the Server sends an agent key. ping \ n

3> the Agent receives the request and then responds to the data <HEADER> <DATALEN> 1

4> the Server processes the received data.

5> close TCP Connection

Active Mode:

1> the Agent establishes a TCP connection to the Server.

2> list of data to be detected by the Agent request

3> Server responds to the Agent and sends an Items list (item key, delay)

4> the Agent responds to the request.

5> close TCP Connection

6> the Agent starts to periodically collect data.

7> the Agent recommends a TCP connection to the Server.

8> the Agent sends the data to the Server during the collection period.

9> the Server processes the data sent by the Agent.

10> disable TCP Connection

 

7. How to disable Zabbix reinstallation

Before disabling:

How to disable:

# Vim/usr/share/zabbix/include/menu. inc. php

/**,                        array(                                'url' => 'setup.php',                                'label' => _('Installation')                        )**/

After disabling:

If the database remains unchanged, the reinstallation of the database will not be affected, and the previous data will be displayed.

 

8. How to set the refresh time of the zabbix front-end page

Profile-> User-> Refresh (in seconds) in the upper right corner)