Re: Incorrect memory reported by Win 2008 R2 client
Posted: Fri May 21, 2010 6:12 am
Is it planned to fix it - check_nt command or default config wizard in Nagios XI? I'm concidering license purchace for Nagios XI mostly because of wizards future and posibility to "outsource" basic config tasks to support personel with no in-depth knowledge in Nagios. It would be rather difficult (but possible - yes) with this kinds of bugs.tonyyarusso wrote:We were able to confirm that it is checking a combination of all virtual memory - physical plus pagefile. This is a limitation of the check_nt command used by default. If you would like to separate that out it is possible, but will require changing the check command to use check_nrpe instead. Additionally, you will need to modify the NSClient++ config file on the target machine to allow arguments in the NRPE section. You can modify the check command from within the Core Config Manager, and make it read something like this:
check_nrpe -H 192.168.5.9 -p 5666 -c CheckMEM -a MaxWarn=80% MaxCrit=90% ShowAll type=physical
The "type=physical" part will restrict it to just RAM. See http://nsclient.org/nscp/wiki/CheckMem for more documentation on this check command.