gary_ford wrote:also I have this on my commands page..
Last database update: 2010-03-23 12:43:28
Last change of the configuration file: 2010-03-17 10:30:56
Warning: configuration file is out of date!
and if i look at the commands.cfg file I do not see the command I entered for check_mem
looks like the gui thinks the command has been "uploaded" to the file but it actually hasnt.
windows server memory check is showing physical+page
Re: windows server memory check is showing physical+page
Re: windows server memory check is showing physical+page
An issue similar to this has been reported recently in the Customer Support Forum. We will take a closer look.
Thank you.
Thank you.
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: windows server memory check is showing physical+page
I have had similar issues. To determine if you are getting the same problem as me try this:gary_ford wrote:gary_ford wrote:also I have this on my commands page..
Last database update: 2010-03-23 12:43:28
Last change of the configuration file: 2010-03-17 10:30:56
Warning: configuration file is out of date!
and if i look at the commands.cfg file I do not see the command I entered for check_mem
looks like the gui thinks the command has been "uploaded" to the file but it actually hasnt.
- Login to Core Configuration Manager (CCM)
On the right click Tools and then click Write Config Files
Click the Go button for Write monitoring data
Underneath it will display the results.
Access the Console of your Nagios XI server or use Putty to connect to it remotely
Type chmod o+w /usr/local/nagios/etc/*.cfg and press Enter
If you click the Go button for Write monitoring data it should now be successfull.
However if the problem still exists try the following:
Type chown root:root /usr/local/nagios/etc/*.cfg and press Enter
And click the Go button for Write monitoring data
Hopefully this fixes your problem and if it does can you please confirm which command (or both) fixed the problem.
Thanks
Troy
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: windows server memory check is showing physical+page
i found the original post, i did both commands just to be safe! it did indeed fix it for me.
Re: windows server memory check is showing physical+page
Just make sure all the form data you submit is correct. Sounds like you are just needing to enter a positive value into "check time period" for Service 'Memory Usage' on host 'sqltest.a4egroup.co.uk'. You may also have not correctly configured your new Check Command, missing forum fields can ruin your hole day.
Re: windows server memory check is showing physical+page
its working fine now.. my major issue now is no emails being sent since updating to latest rc,... (3 threads down)
Incorrect memory reported by Win 2008 R2 client
Hi, I started to look at Nagios XI by adding Windows Server 2008 R2 Std host running as vmware sphere 4 virtual machine with 8 Gb of memory, but Nagios XI (or nsclient++) reports all memory amounts (total and used) multiplied by 2 - eg 16 gb in total instead og 8 gb, used 8 gb insted of 4 gb.
I am running Nagios XI 2009R1.1H downloaded as virtual machine on vmware 4, nssclient++ 0.3.7 64 bit on Windows.
Any ideas? I am quite experienced Nagios 2x and 3.x, NagiosQL etc user, so I beleive it´s rather software bug than install/config...
I am running Nagios XI 2009R1.1H downloaded as virtual machine on vmware 4, nssclient++ 0.3.7 64 bit on Windows.
Any ideas? I am quite experienced Nagios 2x and 3.x, NagiosQL etc user, so I beleive it´s rather software bug than install/config...
Last edited by Kári on Wed May 19, 2010 10:21 am, edited 1 time in total.
-
tonyyarusso
- Posts: 1128
- Joined: Wed Mar 03, 2010 12:38 pm
- Location: St. Paul, MN, USA
- Contact:
Re: Incorrect memory reported by Win 2008 R2 client
Interesting... A couple possibilities that spring to mind:
Is the amount of memory available to your VM "burstable" in any way?
Could the pagefile be included in those figures, returning total virtual memory instead of just RAM?
Is the *used* memory amount *exactly* double? (That might help narrow things down at least.)
Also, could you clarify, is just Nagios XI a VM or are both XI and the Windows server in VMs?
Is the amount of memory available to your VM "burstable" in any way?
Could the pagefile be included in those figures, returning total virtual memory instead of just RAM?
Is the *used* memory amount *exactly* double? (That might help narrow things down at least.)
Also, could you clarify, is just Nagios XI a VM or are both XI and the Windows server in VMs?
Re: Incorrect memory reported by Win 2008 R2 client
This virtual machine has 8 GB (8192 MB) of virtual memory dedicated to it (it is enought of phisical memory in this vmware cluster)Is the amount of memory available to your VM "burstable" in any way?
It possible, becouse page file is 8 GB at the momentCould the pagefile be included in those figures, returning total virtual memory instead of just RAM?
I looked better on it - no, it´s not. There are 6692 MB (85%) in use as reported by Win Resource Manager but Nagios reports 7860.28 Mb (48%) for used memoryIs the *used* memory amount *exactly* double? (That might help narrow things down at least.)
Both machines are VMs inside one vmware Datacenter (but not inside the same cluster)Also, could you clarify, is just Nagios XI a VM or are both XI and the Windows server in VMs?
Regards, Kári
-
tonyyarusso
- Posts: 1128
- Joined: Wed Mar 03, 2010 12:38 pm
- Location: St. Paul, MN, USA
- Contact:
Re: Incorrect memory reported by Win 2008 R2 client
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.
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.