Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory Health/Occupation Linux Machines: cached memory is not considered free/available #5660

Closed
zxyz opened this issue Jan 29, 2017 · 5 comments

Comments

@zxyz
Copy link

zxyz commented Jan 29, 2017

In LibreNMS unter Health - Memory the Physical Memory and Virtual Memory all my Linux VMs Memory is marked red, due to a very high occupation. The VM named monitor below shows the following output:

monitor Physical memory 7.650GB / 7.800GB 151.520MB 98%
monitor Virtual memory 7.650GB / 7.800GB 151.520MB 98%

This is correct, when buffered and cached memory is regarded as occupied.

free -h on monitor shows:

total used free shared buff/cache available
Mem: 7.8G 1.8G 152M 86M 5.9G 5.6G

So actually, monitor is quite happy with its memory. I would suggest to no use the free value but the available value for indication (on Linux machines).

Thanks for LibreNMS!

(latest LibreNMS, ubuntu 16.04)

@laf
Copy link
Member

laf commented Jan 29, 2017

Most likely a duplicate of #3179 please read it and see

@zxyz
Copy link
Author

zxyz commented Jan 29, 2017

oh, yes it is a dupicate. It flipped through my search. sry for that.

@zxyz zxyz closed this as completed Jan 29, 2017
@laf
Copy link
Member

laf commented Jan 29, 2017

The other issue is closed as well. Does it answer your question as we've not changed how we do memory graphs since then afaik

@zxyz
Copy link
Author

zxyz commented Jan 29, 2017

@laf thanks for asking. It answered my question.
I see the point of @paulgear regarding the use of snmp data.

Unfortunately there is no available memory (as in free -h) value in the Detailed Memory Usage graph (probably beacuse this is not provided by snmp) which would imho be a much better reference as the free value. While available might be "wrong" in some cases regarding system health/alerting, free ist "wrong" in this way most of the times (at least for machines which don't have heaps of memory).

@lock
Copy link

lock bot commented May 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

@lock lock bot locked as resolved and limited conversation to collaborators May 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants