[ZBX-8734] Zabbix ipmi poller processes more than 75% busy Created: 2014 Sep 10  Updated: 2017 May 30  Resolved: 2014 Sep 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.4.0rc2
Fix Version/s: 2.4.0rc3

Type: Incident report Priority: Blocker
Reporter: Areg Vrtanesyan Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: ipmi
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Busy processes - ipmi - v2.4.0rc2.PNG    

 Description   

Hi

In recent 2.4.0rc2 and couple of previous versions I have noticed that the IPMI Poller busy data is not correct.

It always show that the pollers are 100% busy even there are no IPMI items configured in the system and all the hosts monitoring is disabled.

https://www.zabbix.com/forum/showthread.php?p=155241

Regards,
Areg

 Comments   
Comment by Aleksandrs Saveljevs [ 2014 Sep 10 ]

This problem is only present in trunk (2.4.0rc1) and is not present in 2.2 branch. It got broken when ZBXNEXT-101 was merged, which introduced the following code in get_process_info_by_thread() in server.c:

...
else if (server_num <= (server_count += CONFIG_IPMIPOLLER_FORKS))
{
	*process_type = ZBX_PROCESS_TYPE_SNMPTRAPPER;
	*process_num = server_num - server_count + CONFIG_IPMIPOLLER_FORKS;
}
...

Note the SNMPTRAPPER typo instead of IPMIPOLLER. I fixed that for proxy.c in 48519, but missed the same case in server.c.

Comment by Aleksandrs Saveljevs [ 2014 Sep 10 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-8734 .

Comment by Andris Zeila [ 2014 Sep 10 ]

Successfully tested

Comment by Aleksandrs Saveljevs [ 2014 Sep 10 ]

Fixed in pre-2.4.0rc3 (trunk) r48910.

Generated at Thu Jan 09 21:02:30 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.