[ZBX-19690] system.swap.size broken when having no swap space Created: 2021 Jul 16  Updated: 2021 Jul 19  Resolved: 2021 Jul 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Agent2 plugin (G)
Affects Version/s: 4.0.32, 5.0.13, 5.4.2, 6.0.0alpha1
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Patrik Uytterhoeven Assignee: Igor Gorbach (Inactive)
Resolution: Won't fix Votes: 2
Labels: usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux and maybe other systems as well



 Description   

create a linux server with 0 swap

create an item for example system.swap.size[,free] 

 

the item will become unsupported and return

system.swap.size[,free] [m|ZBX_NOTSUPPORTED] [Cannot be calculated because swap file size is 0.]

 

so preprocessing cant be used 

 

i would have expected to have seen the value of 0

as this is what linux returns to me when running free 

 

free -m
total used free shared buff/cache available
Mem: 1998 408 509 123 1081 1283
Swap: 0 0 0

 



 Comments   
Comment by Igor Gorbach (Inactive) [ 2021 Jul 19 ]

Hello!

ZBX - is a bug tracker for identifying and fix some issues in Zabbix functionality
Situation, that you described is not a sign of incorrect work of Zabbix.
If this is a critical problem for you - you can make feature request for improving the functionality in ZBXNEXT and if a large number of users vote for it, then the development team will definitely take it into consideration for adding or changing the functionality in new versions of Zabbix

Comment by Patrik Uytterhoeven [ 2021 Jul 19 ]

hmm this item is reporting the wrong information literally making unsupported items using up pollers where it should not.

Preprocessing should be handled on the proxy or zabbix server site not on the agent. The OS returns the value 0 so agent should imho report 0 as well or an indication that the swap doesn't exist like with a special value not return the items just unsupported 

for me more a bug then a feature. But if that is what it takes i will open a feature request for it 

 https://support.zabbix.com/browse/ZBXNEXT-6784

Generated at Wed Jun 18 08:45:07 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.