代码改变世界

Zabbix icmp pinger processes more than 75% busy

  潇湘隐者  阅读(6638)  评论(0编辑  收藏  举报

Zabbix icmp pinger processes more than 75% busy

 

Zabbix server"Zabbix icmp pinger processes more than 75% busy",之所以出现这个错误,因为昨天将模板Template Module ICMP Ping链接到Template OS Windows by Zabbix agent模板下和Template OS Linux by Zabbix agent模板下去了,而又忘记修改参数StartPingers,此时由于只有默认的一个线程在在ping,所以出现了这个告警。具体过程如下:

 

检查发现参数StartPingers没有配置,使用默认的值为1,此参数用于设置启用icmp协议PING主机方式启动线程数量。如果线程数量太小,监控的服务器数量过多的话,那么它有可能处于非常繁忙的状态。我们可以适当的调整其大小值

 

#grep StartPingers /etc/zabbix/zabbix_server.conf 
 
### Option: StartPingers
 
# StartPingers=1

 

  调整参数大小后,重启Zabbix-Server服务,发现出错。具体情况如下所示: 

 

 

# systemctl restart zabbix-server
 
Job for zabbix-server.service failed because the control process exited with error code.
 
See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

 

 检查错误信息,发现是参数设置错误,正确的参数是StartPingers,但是我漏掉了一个s,设置成StartPinger,出现了下面错误。修改后,重启Zabbix-Server服务,解决问题。

 

 

# journalctl -xe
..............................................
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 20 10:13:26 xxxxxx systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit zabbix-server.service has finished shutting down.
Aug 20 10:13:26 xxxxxx systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit zabbix-server.service has begun starting up.
Aug 20 10:13:26 xxxxxx zabbix_server[2873831]: zabbix_server [2873831]: unknown parameter "StartPinger" in config file "/etc/zabbix/zabbix_server.conf", line 242
Aug 20 10:13:26 xxxxxx systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
Aug 20 10:13:26 xxxxxx systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
Aug 20 10:13:26 xxxxxx systemd[1]: Failed to start Zabbix Server.
-- Subject: Unit zabbix-server.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit zabbix-server.service has failed.
-- 
-- The result is failed.
编辑推荐:
· 一个费力不讨好的项目,让我损失了近一半的绩效!
· .NET Core 托管堆内存泄露/CPU异常的常见思路
· PostgreSQL 和 SQL Server 在统计信息维护中的关键差异
· C++代码改造为UTF-8编码问题的总结
· DeepSeek 解答了困扰我五年的技术问题
阅读排行:
· 一个费力不讨好的项目,让我损失了近一半的绩效!
· 清华大学推出第四讲使用 DeepSeek + DeepResearch 让科研像聊天一样简单!
· 实操Deepseek接入个人知识库
· CSnakes vs Python.NET:高效嵌入与灵活互通的跨语言方案对比
· Plotly.NET 一个为 .NET 打造的强大开源交互式图表库
历史上的今天:
2019-08-20 crontab中部署Python脚本注意事项
2019-08-20 TypeError: expected string or bytes-like object
2016-08-20 杂想闲思录
2016-08-20 ORACLE AWR结合ASH诊断分析enq: TX - row lock contention
2015-08-20 Linux的NTP配置总结
2014-08-20 虚拟机备份克隆导致SQL SERVER 出现IO错误案例
点击右上角即可分享
微信分享提示