Closed exa-mk closed 3 years ago
This looks like an integer overflow. Windows uses an uint32 in Megabytes to report the current swap usage. We converted Megabytes into bytes but still using a uint32 which results in a maximum swap filesize of 4GB. I think this is the issue.
I will change this to an uint64
Fixed with 3.0.6: https://github.com/it-novum/openitcockpit-agent-go/releases/tag/3.0.6
Agent Mode:
Versions
Operating system Windows Server 2019 Datacenter
Describe the bug In some circumstances then swap usage is calculated wrong somehow:
There is more free than total and used together... ;) (Usage 150% :D )
To Reproduce Good question... no idea. It's a Windows Terminal Server with some web services. On our other Windows Servers it seems to be fine.
Expected behavior Proper calculation; no misleading alarms.