Re: [Nagios-users] check_nt - MEMORY USAGE - incorrect results

2013-01-10 Thread omar saddiki
this because in your server 2008 you will see that there is a virtual memory activated, go to Computer proprieties and see in performences you will have for exemple for R2 (x64) server box (has SQL installed on it) – 12GB ram installed 12GB of virtual memory.Finaly, Nagios take the some of

Re: [Nagios-users] check_nt - MEMORY USAGE - incorrect results

2013-01-10 Thread Matthew Jurgens
Try www.edcint.co.nz/checkwmiplus using the checkmem mode and see if it works ok for you On 10/01/2013 7:55 PM, omar saddiki wrote: this because in your server 2008 you will see that there is a virtual memory activated, go to Computer proprieties and see in performences you will have for

Re: [Nagios-users] check_nt - MEMORY USAGE - incorrect results

2013-01-10 Thread C. Bensend
Not entirely accurate. I just started troubleshooting a Win2008 R2 system yesterday - it has 16GB of physical RAM + 16 GB pagefile for a total of 32GB of virtual memory. The system is using 10.9GB of physical RAM, yet check_nt tells me it's using 2.69GB. Completely wrong, even if check_nt was

Re: [Nagios-users] check_nt - MEMORY USAGE - incorrect results

2013-01-10 Thread Scott Wilkerson
check_nt 's MEMUSE includes the page file. If you use checkMem via NRPE you can choose only physical http://www.nsclient.org/nscp/wiki/CheckSystem/checkMem Scott Wilkerson Technical Support Specialist ___ Email: swilker...@nagios.com Web: www.nagios.com On 1/9/2013 11:55 AM, Andrew

Re: [Nagios-users] check_nt - MEMORY USAGE - incorrect results

2013-01-10 Thread FTL Nagios
Thankyou I will look at this instead. Thanks to all for your input and help From: Scott Wilkerson [mailto:swilker...@nagios.com] Sent: 10 January 2013 14:03 To: Nagios Users List Subject: Re: [Nagios-users] check_nt - MEMORY USAGE - incorrect results check_nt 's MEMUSE includes the

[Nagios-users] New check_openmanage error after updating to OMSA 7.2.0-4

2013-01-10 Thread Steve Jenkins
Updated to OMSA 7.2.0.4 on a CentOS 6.3 x86_64 box today, and just got this new error when trying to run the check_openmanage nagios plugin: # /usr/local/nagios/libexec/check_openmanage Memory module 2 [DIMM3, 4096 MB]: Single-bit warning error rate exceeded, Single-bit failure error rate

Re: [Nagios-users] New check_openmanage error after updating to OMSA 7.2.0-4

2013-01-10 Thread Steve Jenkins
On Thu, Jan 10, 2013 at 11:39 AM, Steve Jenkins stevejenk...@gmail.comwrote: I see the latest version is 3.7.9 on Trond's website. Any ideas if that will fix the issue? Googling the error produced nothing. And... to answer my own question, yes - 3.7.9 does indeed fix this. New version is

Re: [Nagios-users] New check_openmanage error after updating to OMSA 7.2.0-4

2013-01-10 Thread Trond Hasle Amundsen
Steve Jenkins stevejenk...@gmail.com writes: And... to answer my own question, yes - 3.7.9 does indeed fix this. New version is probably already in the repos, waiting out the testing period. Not sure which repos you're referring to, but I'll assume Fedora and/or Fedora EPEL. I didn't get

Re: [Nagios-users] New check_openmanage error after updating to OMSA 7.2.0-4

2013-01-10 Thread Steve Jenkins
On Thu, Jan 10, 2013 at 1:39 PM, Trond Hasle Amundsen t.h.amund...@usit.uio.no wrote: Not sure which repos you're referring to, but I'll assume Fedora and/or Fedora EPEL. Yep - those are the ones I was referring to. :) I didn't get around to submitting updates until today. They should

[Nagios-users] Service Alert History - No history information was found for this service in this archived log file

2013-01-10 Thread Samuel Kidman
Hello I am having an issue where Nagios is not finding alert history in the nagios log files. eg. I have a service called cpu on host PR-GGM-CR-DC01. prl@PR-PRO-CR-NAG02:/usr/local/nagios/var/archives$ grep 'PR-GGM-CR-DC01;cpu' nagios-01-11-2013-00.log [1357747200] CURRENT SERVICE STATE: