Solve the problem of “ZABBIX discoverer processes 75% busy” in CentOS

Pioneers published in operation and maintenance experience sharing subscription

253

Tencent cloud server annual payment 3 fold

The first purchase of cloud server is at least 3 fold, with super high cost performance

Limited time rush purchase

In the process of using ZABBIX, when the auto discovery protocol is turned on, the alarm message “ZABBIX discoverer processes more than 75% busy” frequently appears, as follows:

Trigger: Zabbix discoverer processes more than 75% busy
Trigger status: PROBLEM
Trigger severity: Average
Trigger IP: 61.172.253.59
Item values:
1. Zabbix busy discoverer processes, in % (192.168.1.222:zabbix[process,discoverer,avg,busy]): 100 %
Original event ID: 4690

After searching on the Internet, there are many main reasons for the alarm: 1. MySQL supporting ZABBIX is stuck; 2. Io of ZABBIX server is stuck; 3. ZABBIX process is not allocated enough memory; 4. The target server is not connected to the network. Therefore, consider increasing the number of initialization processes when ZABBIX server starts, and directly increasing the polling load to avoid this kind of error. Modify/etc/ZABBIX/ZABBIX_ server.conf , find startpollers

### Option: StartPollers

# Number of pre-forked instances of pollers.

#

# Mandatory: no

# Range: 0-1000

# Default:

StartPollers=5

According to the system hardware configuration, it can be set to a higher value. Another solution is to restart ZABBIX server regularly. It can be configured by timing script as follows:

crontab -e

@daily service zabbix-server restart &> /dev/null 2&>&1

For reprint, please note: knowledge base solves the problem of “ZABBIX discoverer processes 75% busy” in CentOS

(adsbygoogle = window.adsbygoogle || []).push({});