[ZBX-6531] Possibly a memory leak in zabbix_agentd on AIX Created: 2013 Apr 19  Updated: 2017 May 30  Resolved: 2014 May 29

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 2.0.4
Fix Version/s: 2.0.13rc1, 2.2.4rc1, 2.3.1

Type: Incident report Priority: Minor
Reporter: Marc Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: aix, memoryleak
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AIX 6.1.0.0, Zabbix-Server/-Proxy 2.0.5, Zabbix-Agent 2.0.4


Attachments: PNG File ZBX-6531-bugfix.png     PNG File ZBX-6531-bugfix2.png     PNG File ZBX-6531-bugfix2.png     PNG File zabbix_agentd_mem_aix_1.png     PNG File zabbix_agentd_mem_aix_2.png     PNG File zabbix_agentd_mem_aix_3.png     PNG File zabbix_agentd_mem_aix_4.png     PNG File zbx-6531-2.2.0.png    
Issue Links:
Duplicate

 Description   

There is possibly a (very small) memory leak in zabbix_agentd.
Memory is collected via proc.mem[zabbix_agentd,zabbix]

 Comments   
Comment by Marc [ 2013 Apr 19 ]

I've failed to mention that every line represents an Agent on a dedicated AIX server.
Both attached images are nearly the same. The second image (zabbix_agentd_mem_aix_2.png) lacks of the servers with more than ~14 MB memory consumption.

Comment by Marc [ 2013 Apr 30 ]

After updating the agent to 2.0.6 the memory consumption appears to be constant.

At least for one AIX server.

Comment by Marc [ 2013 May 07 ]

Issue still exists in 2.0.6.
See attached zabbix_agentd_mem_aix_4.png

BTW:
Memory consumption is actually about 6 times more than displayed in the graphs. See ZBX-6527

Comment by Oleg Ivanivskyi [ 2014 May 27 ]

How to about try to reproduce this issue with a latest Zabbix agent versions (2.0.12 and 2.2.3)?

Comment by Marc [ 2014 May 28 ]

I do. For now I attached another graph for several hosts running 2.2.0 agents.

Comment by Oleg Ivanivskyi [ 2014 May 28 ]

Thank you for your help.

We have ZBX-7392. Could you try Zabbix agent 2.2.3 as well?

Comment by Marc [ 2014 May 28 ]

Right after my previous comment I upgraded the hosts seen in the last uploaded graph to 2.2.3.
It's to early to make a serious prediction but this are the values so far for one of those hosts:

Timestamp Value Change
2014.May.28 15:29:13 6676480 -
2014.May.28 15:29:42 6688768 12288
2014.May.28 15:30:42 6705152 16384
2014.May.28 15:49:13 6737920 32768
2014.May.28 15:50:12 6746112 8192
2014.May.28 16:00:12 6750208 4096
2014.May.28 16:49:12 6782976 32768
2014.May.28 16:50:12 6799360 16384

Edit:

Memory utilization with 2.2.3 agent measured every second:

Timestamp Value Change
Wed May 28 19:39:36 CEST 2014 6823936 -
Wed May 28 20:48:58 CEST 2014 6832128 8192
Wed May 28 21:48:58 CEST 2014 6844416 12288
Wed May 28 22:48:58 CEST 2014 6856704 12288
Wed May 28 23:48:58 CEST 2014 6873088 16384
Thu May 29 00:48:58 CEST 2014 6885376 12288
Thu May 29 01:48:58 CEST 2014 6901760 16384
Thu May 29 02:48:57 CEST 2014 6914048 12288
Thu May 29 03:48:57 CEST 2014 6926336 12288
Thu May 29 04:48:57 CEST 2014 6942720 16384
Thu May 29 05:48:58 CEST 2014 6955008 12288
Thu May 29 06:48:57 CEST 2014 6967296 12288
Thu May 29 07:48:58 CEST 2014 6979584 12288
Thu May 29 08:48:57 CEST 2014 6995968 16384
Thu May 29 09:48:58 CEST 2014 7012352 16384
Thu May 29 10:48:57 CEST 2014 7024640 12288
Comment by Juris Miščenko (Inactive) [ 2014 May 29 ]

Fix for 2.0 implemented in svn://svn.zabbix.com/branches/dev/ZBX-6531

Comment by Marc [ 2014 May 29 ]

File system discovery is set to every second in colorized areas.
The first one without and the second one with interim patch applied.

Comment by Juris Miščenko (Inactive) [ 2014 May 29 ]

Fixed merged in 2.0.13rc1 r46035, 2.2.4rc1 r46036, 2.3.1 (trunk) r460357

Generated at Fri Apr 26 04:16:30 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.