Page 1 of 1
Incorrect memory reporting
Posted: Thu Jul 27, 2017 6:59 am
by sdecker
Why does Nagios report memory of 26639.72 when only 163840 is assigned to a VM of the 163840, 4096 is reserved
Re: Incorrect memory reporting
Posted: Thu Jul 27, 2017 10:21 am
by bolson
Hello sdecker, can you please provide us with more information? Which plugin are you're using to report memory usage?
Re: Incorrect memory reporting
Posted: Thu Jul 27, 2017 3:21 pm
by sdecker
check_xi_service_nsclient!XXXXXXXX!MEMUSE!-w 70 -c 90!!!!!
Re: Incorrect memory reporting
Posted: Thu Jul 27, 2017 3:43 pm
by bolson
Can you post the complete output of this check command?
Re: Incorrect memory reporting
Posted: Fri Jul 28, 2017 6:53 am
by sdecker
Agilence memory.JPG
Ok
Memory usage: total:26639.72 MB - used: 5111.17 MB (19%) - free: 21528.54 MB (81%)
Re: Incorrect memory reporting
Posted: Fri Jul 28, 2017 10:22 am
by bolson
check_nt 's MEMUSE includes the page file. Check to confirm this.
If you use checkMem via NRPE you can choose only physical
Re: Incorrect memory reporting
Posted: Fri Jul 28, 2017 10:44 am
by sdecker
I have never used NRPE is there a guide
Re: Incorrect memory reporting
Posted: Fri Jul 28, 2017 10:54 am
by bolson
Re: Incorrect memory reporting
Posted: Fri Jul 28, 2017 10:54 am
by mcapra
Step 1 is setting up NSClient++ to listen to check_nrpe connections. The official documentation is pretty good for that:
https://docs.nsclient.org/howto/nrpe/
@box293 has some very useful examples of leveraging check_nrpe with NSClient++ listed on his website:
http://sites.box293.com/nagios/guides/common-checks
The top example on this page shows a check against a machine using NSClient++ that only looks at the physical usage:
http://sites.box293.com/nagios/guides/c ... mory-usage
Re: Incorrect memory reporting
Posted: Fri Jul 28, 2017 11:05 am
by bolson
Thanks for your insights Matt!