手撕zabbix server報錯等若干問題

關於zabbix server出現的告警情況解釋及處理方法

More than 100 items having missing data for more than 10 minutes

中文解釋:超過100項數據丟失超過10分鐘

原因分析:

    1.server端與proxy端時間不同步

    2.server端分配的緩存不夠

    3.server端分配的線程不夠

4.server端負載比較大{CPU,IO,MEM}

解決辦法:1、增大線程 2、增大緩存 具體修改參數如下

[root@localhost zabbix]#  vim /usr/local/zabbix/etc/zabbix_server.conf

StartPollers=500  # zabbix server 的進程數

StartPollersUnreachable=50 

StartTrappers=30

StartDiscoverers=6  # 自動發現數量

CacheSize=1G  # 緩存

CacheUpdateFrequency=300  # 更新頻率(單位s)

StartDBSyncers=20   # 預先foke DB Syncers的數量

HistoryCacheSize=512M  #歷史記錄緩存大小,用於存儲歷史記錄

TrendCacheSize=256M  # 歷史數據緩存大小

HistoryTextCacheSize=80M  # 取值範圍:128K-2G 文本類型歷史記錄的緩存大小,存儲character, text 、log歷史記錄.

ValueCacheSize=1G  # 0表示禁用,history value緩存大小,當緩存超標了,將會每隔5分鐘往server日誌裏面記錄。

 

 

二、Too many processes on 10.9.19.217(zabbix server)

中文解釋:10.9.19.217(zabbix服務器)上的進程太多

可能有以下兩種情況:

1、檢查此服務器上進程是否有些無用進程,關閉即可

2、當你在此服務器上啓動的進程確實很多,此時需要去調高觸發器的值,如下圖

三、Zabbix housekeeper processes more than 75% busy

housekeeper是什麼呢,我們從配置文件(如下)來研究

### Option: HousekeepingFrequency
#       How often Zabbix will perform housekeeping procedure (in hours).
#       Housekeeping is removing outdated information from the database.
#       To prevent Housekeeper from being overloaded, no more than 4 times HousekeepingFrequency
#       hours of outdated information are deleted in one housekeeping cycle, for each item.
#       To lower load on server startup housekeeping is postponed for 30 minutes after server start.
#       With HousekeepingFrequency=0 the housekeeper can be only executed using the runtime control option.
#       In this case the period of outdated information deleted in one housekeeping cycle is 4 times the
#       period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.
#
# Mandatory: no
# Range: 0-24
# Default:
HousekeepingFrequency=12

### Option: MaxHousekeeperDelete
#       The table "housekeeper" contains "tasks" for housekeeping procedure in the format:
#       [housekeeperid], [tablename], [field], [value].
#       No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])
#       will be deleted per one task in one housekeeping cycle.
#       SQLite3 does not use this parameter, deletes all corresponding rows without a limit.
#       If set to 0 then no limit is used at all. In this case you must know what you are doing!
#
# Mandatory: no
# Range: 0-1000000
# Default:
MaxHousekeeperDelete=1000000

翻譯過來大概就是說從數據庫中刪除過期的歷史數據。然後HousekeepingFrequency是清理的頻率,這裏我設置爲12小時清理一次,MaxHousekeeperDelete就是一個閾值,每次輪到刪除過期歷史數據這個任務的時候,最多刪除這個閾值的行數。其實
就是對mysql進行刪除數據操作。

四、Zabbix poller processes more than 75% busy

中文解釋:zabbix輪詢的進程超過75%繁忙

告警原因:

1.某個進程卡住了,

2.殭屍進程出錯,太多,導致慢了

3.網絡延遲(可忽略)

4.zabbix消耗的內存多了

解決辦法:

修改zabbix-server.conf文件中的StartPollerszabbix server 的進程數參數,

發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章