Too many processes on Zabbix server 解決辦法

標籤：too many processes on zabbix server

新部署的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服務即可解決問題。

本文出自 “點滴積累” 部落格，請務必保留此出處http://16769017.blog.51cto.com/700711/1761002

Too many processes on Zabbix server   解決辦法