Shulou(Shulou.com)06/03 Report--

Question 1 Zabbix alerter processes more than 75% busy

The cause of the problem:

The zabbix server mail process is busy, usually because the interval between setting actions is too short. Under special circumstances, a large number of alarms will be generated, such as when the server sends tens of thousands of e-mails, the mail process fails.

Solution:

01. Delete database solution (risky, not recommended)

02. Modify the mail script, change the action of the message to print time, and wait for the message to be fully released before changing it back, as follows

[root@m01 ~] # cat / usr/lib/zabbix/alertscripts/sms 2 3 #! / bin/bash 4 5 echo date > > / tmp/sms.txt

Question 2 Zabbix discoverer processes more than 75% busy

The cause of the problem:

01. The discovery auto-discovery task is configured, and each configured discovery task takes up 1 process in a certain period of time, while the default configuration in zabbix_server.conf has only 1 discovery (annotated, effective by default)

02. To quickly verify the auto-discovery effect, set the "Delay" of the discovery task from the default 3600s to 60s.

Solution:

01. Modify the number of StartDiscoverers processes in the configuration file, cancel the previous # and change the value to 5, and finally restart the service

(note: depending on the hardware configuration of the system, it can be set to a higher value, but the range is 0mm 250)

[root@m01] # grep 'StartDiscoverers' / etc/zabbix/zabbix_server.conf 2 3 # Option: StartDiscoverers 4 5 StartDiscoverers=5 6 7 [root@m01] # systemctl restart zabbix-server.service

02. Write scheduled task scripts to restart zabbix_server to reduce load

[root@m01] # crontab-e 2 3 @ daily service zabbix-server restart > / dev/null 2 > & 14 5 # plans to automatically restart the Zabbix service every day to end zombie processes and clean up memory, etc.

Question 3 Zabbix poller processes more than 75% busy

The cause of the problem:

01. The device that collects data through Zabbix agent crashes or other reasons cause zabbix agent to die and server cannot get the data.

It takes too long for server to obtain data from agent, which exceeds the timeout time set by server

Solution:

01. Increase the number of processes initialized at Zabbix Server startup Option: StartPollers 2 3 StartPollers=10 # depends on the performance of the server and the number of monitoring, and can be set higher if there is enough memory

02. Modify the template auto-discovery rule to retain lost resources for a period of 0

Question 4 Zabbix housekeeper processes more than 75% busy

The cause of the problem:

In order to prevent the continuous growth of the database, zabbix has a mechanism for automatically deleting historical data, namely housekeeper, while when mysql deletes data, the performance will degrade and an error will be reported.

Solution:

Adjust HousekeepingFrequency parameters

HousekeepingFrequency=12 # interval 2 3 MaxHousekeeperDelete=1000000 # maximum deletion

Problem 5 Zabbix server memory overflow, unable to start

The cause of the problem:

After zabbix has been used for a period of time, join a batch of switch monitoring again, and zabbix-server will fail to start. The view log is shown as follows (prompt for memory overflow, need to adjust zabbix server configuration zabbix_server.conf)

2816 out of memory 20170725 file:dbconfig.c,line:652 174352.675 [file:dbconfig.c,line:652] zbx_mem_realloc (): out of memory (requested 162664 bytes) 2 3 2816 purl 20170725 requested 174352.675 [file:dbconfig.c,line:652] zbx_mem_realloc (): please increase CacheSize configuration parameter

Solution:

Vim zabbix_server.conf 2 3 CacheSize=1024M # defaults to 8m

Question 6 PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 11 bytes)

The cause of the problem:

Some pages of zabbix cannot be opened. Check the php log and find that when you visit this page, you are out of memory.

Solution:

It is not clear whether there is a memory leak. The easiest way is to increase the available memory of the php process.

[root@zabbix-master ~] # grep 'memory_limit' / etc/httpd/conf.d/zabbix.conf 2 3 php_value memory_limit 512m # default 128m

Question 7 cannot create semaphore set: [28] No space left on device

Reason for reporting an error:

The kernel.sem parameter setting is too small.

Shared memory: you can view the parameter limits of the current system shared memory through the ipcs-lm command

Cat / proc/sys/kernel/sem

250 32000 32 128

Modify the file vi / etc/sysctl.conf

Kernel.sem = 500 64000 64 128

Execute sysctl-p / etc/sysctl.conf

Question 8 1710 cannot send list of active checks to 20190710 cannot send list of active checks to "192.168.160.26": not found [192.168.177.37]

The cause of the problem:

1 inconsistency of hostname and web interfaces on zabbix agent

2 caused by the failure of the agent side to stop after the host is deleted

Solution:

Modify the hostname in the hostname or web interface on the agent side

Close the agent client that deletes the host

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.