landscape-sysinfo reports wrong memory utilization

Can you please paste or attach an up-to-date output of landscape-sysinfo together with the contents of /proc/meminfo?

landscape-sysinfo uses the contents of /proc/meminfo to calculate the memory usage value.

Interesting, I just asked about this on AskUbuntu but I tihnk I figured out the issue.

/proc/meminfo reports the same memory info that landscape-sysinfo does.

Here's the thing, 'free' reports a lot of memory info. To get the data supplied by 'free' to match both landscape-sysinfo and /proc/meminfo, the calculation is:

(used - [-/+ buffers/cache]) / total

the -/+ buffers/cache value is the one right below 'used'

Now your % free should match what is reported by landscape-sysinfo

So this is not a real bug. It's rather a question, something like "How does memory usage reported by /proc/meminfo or landscape-sysinfo relate to the one provided by the command 'free' "

That's not what I'm seeing John; the amount reported by landscape-sysinfo does not appear to match either with or without counting buffers/cache.

free also gets its info from /proc/meminfo, but here's the full thing:

MemTotal: 2060368 kB
MemFree: 518948 kB
Buffers: 160748 kB
Cached: 1213604 kB
SwapCached: 0 kB
Active: 498024 kB
Inactive: 940096 kB
Active(anon): 63896 kB
Inactive(anon): 508 kB
Active(file): 434128 kB
Inactive(file): 939588 kB
Unevictable: 0 kB
Mlocked: 0 kB
HighTotal: 1182600 kB
HighFree: 15388 kB
LowTotal: 877768 kB
LowFree: 503560 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 32 kB
Writeback: 0 kB
AnonPages: 63684 kB
Mapped: 13580 kB
Shmem: 636 kB
Slab: 84508 kB
SReclaimable: 74376 kB
SUnreclaim: 10132 kB
KernelStack: 896 kB
PageTables: 2348 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1030184 kB
Committed_AS: 115740 kB
VmallocTotal: 122880 kB
VmallocUsed: 3916 kB
VmallocChunk: 100752 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 34808 kB
DirectMap2M: 878592 kB

Okay, you're right. I was having the same issue but I saw somewhere to do the calculation I gave you and it worked for me. Doesn' t seem to apply to your server. Hopefully, someone familiar with the subject comes along. For now I changed the status of the bug back to confirmed.

No, it is a bug, not a question. The value being reported is not correct.

It appears that ladscape is calculating the amount of free memory by subtracting the active list from the total, which is wildly incorrect. Patching now.