Too many processes on Zabbix server 解决办法

23123

新部署的zabbix服务器，上线后在mointoring 页面就有“Too many processes on Zabbix server”的告警。在网上查看了很多资料没能解决。只能按照经验处理
1 ps -axf 查看进程情况，观察一下什么进程比较多。
16838 ?        S      0:00  \_ /usr/local/sbin/zabbix_server: configuration syncer [waiting 60 sec for processes]
16839 ?        S      0:00  \_ /usr/local/sbin/zabbix_server: db watchdog [synced alerts config in 0.001120 sec, idle 60 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 30 sec]
16863 ?        S      0:00  \_ /usr/local/sbin/zabbix_server: housekeeper [deleted 2757 hist/trends, 0 items, 0 events, 0 sessions, 0 alarms, 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 in 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 60 sec]
16867 ?        S      0:00  \_ /usr/local/sbin/zabbix_server: discoverer #2 [processed 0 rules in 0.000576 sec, idle 60 sec]
16868 ?        S      0:00  \_ /usr/local/sbin/zabbix_server: discoverer #3 [processed 0 rules in 0.000486 sec, idle 60 sec]
16869 ?        S      0:00  \_ /usr/local/sbin/zabbix_server: discoverer #4 [processed 0 rules in 0.000771 sec, idle 60 sec]
16870 ?        S      0:00  \_ /usr/local/sbin/zabbix_server: discoverer #5 [processed 0 rules in 0.000450 sec, idle 60 sec]

观察我自己的服务器的时候，发现进程最多的居然就是zabbix自己的服务。
2 按照以往的经验，服务启动的进程数应该都可以在配置文件中配置。于是查看zabbix的配置文件，果然找到类似配置参数

#高级参数
### Option: StartPollers
#   Number of pre-forked instances of pollers.
#
# Mandatory: no
# Range: 0-1000
# Default:
#说明;初始化时，启动子进程数量，数量越多，则服务端吞吐能力越强，对系统资源消耗越大
# StartPollers=5

### Option: StartDiscoverers
#   Number of pre-forked instances of discoverers.
#
# Mandatory: no
# Range: 0-250
# Default:
说明：用于设置自动发现主机的线程数量，若单台代理所管理机器超过500台，可以考虑加大此数值（仅适用于直接AGENT场景）
# StartDiscoverers=1
类似以上的一些参数，具体情况要看ps的结果来对照参数处理。我的这些参数不知道什么原因导致的，都特别的高，实际上应该按照需要调整。

把对应进程的参数调整好后，重启zabbix服务即可解决问题。