[ZBX-10899] Zabbix poller processes more than 75% busy (100%) Created: 2016 Jun 13  Updated: 2019 Mar 21  Resolved: 2016 Jun 13

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Server (S)
Affects Version/s: 3.0.3
Fix Version/s: None

Type: Incident report Priority: Critical
Reporter: elias abou hamad Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Centos7 (32gb ram , cpu 12 core)


 Description   

Zabbix poller processes more than 75% busy,
StartPollers=1000,
StartTrappers=1000,
CacheSize=8000M,
CacheUpdateFrequency=60,
server cpu load average: 2.63, 3.46, 3.65

 Comments   
Comment by Aleksandrs Saveljevs [ 2016 Jun 13 ]

This tracker is for bug reports only. For troubleshooting and community support, please refer to https://www.zabbix.org/wiki/Getting_help .

If, however, you have purchased commercial support from Zabbix LLC, please move this issue to the appropriate project.

Comment by Zhang Bowen [ 2019 Mar 21 ]

Can you start zabbix_server after set StartPollers=1000?

Problems occured when i set StartPollers more than 400. And the following is my error log.

I really appreciate it if you can help.

5027:20190321:061103.652 server #623 started unreachable poller #1
5031:20190321:061103.687 server #624 started trapper #1
5033:20190321:061103.707 server #625 started trapper #2
5035:20190321:061103.714 server #626 started trapper #3
5036:20190321:061103.742 server #627 started trapper #4
5039:20190321:061103.751 server #628 started trapper #5
5042:20190321:061103.782 server #629 started icmp pinger #1
5045:20190321:061103.791 server #630 started alert manager #1
5048:20190321:061103.798 server #631 started preprocessing manager #1
4313:20190321:061104.060 cannot connect to alert manager service: Cannot connect to service "alerter": [111] Connection refused.
4315:20190321:061104.062 cannot connect to alert manager service: Cannot connect to service "alerter": [111] Connection refused.
4314:20190321:061104.071 cannot connect to alert manager service: Cannot connect to service "alerter": [111] Connection refused.
4311:20190321:061104.073 One child process died (PID:4313,exitcode/signal:1). Exiting ...
5051:20190321:061104.172 server #634 started preprocessing worker #3

Generated at Wed Jul 16 11:01:15 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.