[ZBX-24653] configuration options to limit zabbix agent 2 memory usage Created: 2024 Jun 13 Updated: 2025 Mar 19 Resolved: 2025 Mar 19 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent2 plugin (G) |
Affects Version/s: | 6.4.14 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Critical |
Reporter: | atpk | Assignee: | Zabbix Support Team |
Resolution: | Fixed | Votes: | 0 |
Labels: | Agent2, memoryleak, plugins | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Zabbix Agent 2 is slowly eating away all the available memory and swap resulting oom killer and possible system crashes, so introduce a configuration option to preallocate fixed amount of memory to zabbix agent 2 similar to zabbix server. |
Comments |
Comment by Edgar Akhmetshin [ 2024 Jun 14 ] |
Memory leak should be fixed, which metrics you are using with Agent 2? You can see full list of metrics with a runtime control: Also to find metrics causing the memory leak issue try to disable items from template/host, like disabling all passive checks, or only mysql checks, or oracle checks. |
Comment by atpk [ 2024 Jun 23 ] |
On server side, we are not using any passive checks, the only templates we are using are "Linux by zabbix agent active", "Systemd by zabbix agent 2". On agent side, we added one user parameter to return host metadata for autoregistration process. |
Comment by Vladislavs Sokurenko [ 2025 Jan 30 ] |
Please see |
Comment by Vladislavs Sokurenko [ 2025 Mar 19 ] |
Closing this as duplicate of |