Too many processes on Zabbix server workaround

Newly deployed Zabbix server, on the Mointoring page after the launch, there is "Too many processes on Zabbix server" alarm. There's a lot of information on the Internet that can't be solved. Can only be handled according to experience

1 PS-AXF Review the process and see what process is more.

16838? S 0:00 \_/usr/local/sbin/zabbix_server:configuration Syncer [Waiting sec for processes]

16839? S 0:00 \_/usr/local/sbin/zabbix_server:db watchdog [Synced Alerts config in 0.001120 sec, idle sec]

16840? S 0:00 \_/usr/local/sbin/zabbix_server:poller #1 [got 0 values in 0.000004 sec, idle 1 sec]

16842? S 0:00 \_/usr/local/sbin/zabbix_server:poller #2 [got 0 values in 0.000004 sec, idle 1 sec]

16843? S 0:00 \_/usr/local/sbin/zabbix_server:poller #3 [got 0 values in 0.000004 sec, idle 1 sec]

16844? S 0:00 \_/usr/local/sbin/zabbix_server:poller #4 [got 0 values in 0.000004 sec, idle 1 sec]

16845? S 0:00 \_/usr/local/sbin/zabbix_server:poller #5 [got 3 values in 0.001429 sec, idle 1 sec]

16846? S 0:00 \_/usr/local/sbin/zabbix_server:poller #6 [got 0 values in 0.000004 sec, idle 1 sec]

16847? S 0:00 \_/usr/local/sbin/zabbix_server:poller #7 [got 0 values in 0.000004 sec, idle 1 sec]

16848? S 0:00 \_/usr/local/sbin/zabbix_server:poller #8 [got 0 values in 0.000003 sec, idle 1 sec]

16849? S 0:00 \_/usr/local/sbin/zabbix_server:poller #9 [got 0 values in 0.000004 sec, idle 1 sec]

16850? S 0:00 \_/usr/local/sbin/zabbix_server:poller #10 [got 0 values in 0.000003 sec, idle 1 sec]

16851? S 0:00 \_/usr/local/sbin/zabbix_server:unreachable poller #1 [got 0 values in 0.000027 sec, idle 5 sec]

16852? S 0:00 \_/usr/local/sbin/zabbix_server:trapper #1 [processed data in 0.000000 sec, waiting for connection]

16853? S 0:00 \_/usr/local/sbin/zabbix_server:trapper #2 [processed data in 0.000000 sec, waiting for connection]

16854? S 0:00 \_/usr/local/sbin/zabbix_server:trapper #3 [processed data in 0.100752 sec, waiting for connection]

16855? S 0:00 \_/usr/local/sbin/zabbix_server:trapper #4 [processed data in 0.000000 sec, waiting for connection]

16856? S 0:00 \_/usr/local/sbin/zabbix_server:trapper #5 [processed data in 0.000000 sec, waiting for connection]

16857? S 0:00 \_/usr/local/sbin/zabbix_server:icmp pinger #1 [got 0 values in 0.000004 sec, idle 5 sec]

16858? S 0:00 \_/usr/local/sbin/zabbix_server:icmp pinger #2 [got 0 values in 0.000004 sec, idle 5 sec]

16859? S 0:00 \_/usr/local/sbin/zabbix_server:icmp pinger #3 [got 0 values in 0.000004 sec, idle 5 sec]

16860? S 0:00 \_/usr/local/sbin/zabbix_server:icmp pinger #4 [got 0 values in 0.000005 sec, idle 5 sec]

16861? S 0:00 \_/usr/local/sbin/zabbix_server:icmp pinger #5 [got 0 values in 0.000003 sec, idle 5 sec]

16862? S 0:00 \_/usr/local/sbin/zabbix_server:alerter [sent alerts:0 success, 0 fail in 0.000436 sec, idle [sec]

16863? S 0:00 \_/usr/local/sbin/zabbix_server:housekeeper [deleted 2757 hist/trends, 0 items, 0 events, 0 sessions, 0 ala RMS, 0 Audit it

16864? S 0:00 \_/usr/local/sbin/zabbix_server:timer #1 [processed 0 triggers, 0 events in 0.000000 sec, 0 maint.periods I N 0.000000 sec,

16865? S 0:00 \_/usr/local/sbin/zabbix_server:http poller #1 [got 0 values in 0.001521 sec, idle 5 sec]

16866? S 0:00 \_/usr/local/sbin/zabbix_server:discoverer #1 [processed 0 rules in 0.000441 sec, idle sec]

16867? S 0:00 \_/usr/local/sbin/zabbix_server:discoverer #2 [processed 0 rules in 0.000576 sec, idle sec]

16868? S 0:00 \_/usr/local/sbin/zabbix_server:discoverer #3 [processed 0 rules in 0.000486 sec, idle sec]

16869? S 0:00 \_/usr/local/sbin/zabbix_server:discoverer #4 [processed 0 rules in 0.000771 sec, idle sec]

16870? S 0:00 \_/usr/local/sbin/zabbix_server:discoverer #5 [processed 0 rules in 0.000450 sec, idle sec]

Observing my own server, I found that the most process is Zabbix own service.

2 According to previous experience, the number of processes started by the service should be configurable in the configuration file. Then look at the Zabbix configuration file, and sure enough to find similar configuration parameters

#Advanced parameters
# # Option: startpollers
# Number of pre-forked instances of pollers.
## Mandatory: no
# range: 0-1000
# Default:
#Description; When initializing, the number of child processes started, the more the number, the more throughput capacity of the service side, the greater the consumption of system resources

# startpollers=5

# # Option:startdiscoverers

# Number of pre-forked instances of discoverers.

#

# Mandatory:no

# range:0-250

# Default:

Note: To set the number of threads for the Autodiscover host, consider increasing this value if the single agent manages more than 500 machines (only for direct agent scenarios)

# Startdiscoverers=1

Similar to some of the parameters, the specific situation depends on the results of PS to control parameter processing. My parameters do not know what causes, are particularly high, should actually be adjusted as needed.

After adjusting the parameters of the corresponding process, restarting the Zabbix service can solve the problem.

This article is from the "bit accumulation" blog, please be sure to keep this source http://16769017.blog.51cto.com/700711/1761002

Too many processes on Zabbix server workaround