check_nt Memory

[braindope]

Hi Everyone,

I'm using check_nt to monitor my memory, one thing that i noticed is that it's not accurate.


Memory usage: total:37631.87 MB - used: 2263.38 MB (6%) - free: 35368.49 MB (94%)
Above is my reading on my first server, the total should be 32GB only


Memory usage: total:75264.20 MB - used: 2283.17 MB (3%) - free: 72981.03 MB (97%)
Above is my reading on my second server, the total should be 64GB only

why is it that the readings are much higher than the actual?

[hsmith]

What version of NSClient are you using?

[braindope]

Hi,

below is the client version

NSClient++ 0.4.3.143 2015-04-29

[Box293]

What you are seeing here is a combination of physical memory and the page file. This is a limitation of CHECKMEM in check_nt.

To check the physical memory you need to use check_nrpe instead and enable the NRPE module in NSClient++.

Here is some information:
http://sites.box293.com/nagios/guides/c ... mory-usage
http://sites.box293.com/nagios/guides/n ... dows/0-4-x
http://sites.box293.com/nagios/guides/n ... t-ini-file

Does this make sense?

[braindope]

Hi Box,

Can nrpe installed instead of enabling it in the nsclient? ,unfortunately i don't control on the server . It is much easier for me to request the installation of nrpe. is there any problem running nsclient and nrpe at the same time?

[Box293]

NPPE is another type of communication method and is just another module in NSClient++. It's a matter of adjusting the nsclient.ini file to enable the NRPE module and restarting the service.

[braindope]

Will this result in a downtime of the server? ,I mean when adjusting the nsclient?

[Box293]

No.

All you need to do is run these commands in a command prompt on your windows server:

Code: Select all

cd "\Program Files\NSClient++\"
nscp settings --activate-module NRPEServer --add-defaults
nscp settings --path /settings/NRPE/server --key "allow arguments" --set true
nscp settings --path /settings/NRPE/server --key "allow nasty characters" --set true
nscp settings --path /settings/NRPE/server --key insecure --set true

Then restart the NSClient++ service.

[braindope]

Thanks,

I will endorsed your solution to our SysAd. Hope this will fixed my issue

[hsmith]

Let us know if there is anything we can do to further help.

Thanks!