id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc
63,checkMem seems like not working correct,petar.kazakov@…,mickem,"when I'm checking the physical mem usage useing the 0.2.7 Version of NSClient++,
I have the follow problem.


command I use ""check_nrpe2 -H HOSTADDRES -P pass -c checkMem -a ShowAll=long type=physical MaxWarn=100M MaxCrit=1G""


it returns ""OK: physical memory: Total: 3G - Used: 517M (16%) - Free: 2.49G (84%)""
which is obviously not right, it is supposed to say critical.

I tried with %GBMK ... no luck it is still the same, each time it say ""EVERYTHING IS FINE, don't worry""



Meanwhile in the log it says : 

2007-06-11 19:42:36: debug:.\NSClient++.cpp:370: Injecting: checkMem: ShowAll=long, type=physical, MaxWarn=100M, MaxCrit=1G[[BR]]
2007-06-11 19:42:36: debug:c:\source\nscp\trunk\include\checkHelpers.hpp:675: Missing bounds for maxmin-bounds check: physical memory[[BR]]
2007-06-11 19:42:36: debug:.\CheckSystem.cpp:666: Perf data: 1:[[BR]]
2007-06-11 19:42:36: debug:.\NSClient++.cpp:390: Injected Result: OK  --  OK: physical memory: Total: 3G - Used: 514M (16%) - Free: 2.5G (84%)[[BR]]
2007-06-11 19:42:36: debug:.\NSClient++.cpp:391: Injected Performance Result:[[BR]]



I double check the parameters they are right.
So, I think it must be something in the NSClient.

The Nagios server is FreeBSD. The client is running on Windows 2003 Enterprise (same on XP Profesional and Win 2003 R2 Enterprise).",defect,closed,5,0.3.0,CheckSystem,0.2.7,Bugs,worksforme,,