Double Momory on Nagios XI
Double Momory on Nagios XI
Hi,
We installed Nagios XI on centos OS 5.5 couple of days back.
We installed the windows agent on a windows desktop and windows server.
We used the configuration wizard to set up monitoring.
The memory result its getting is double.
Machine 1 - Windows server 2003:
Memory usage: total:7376.23 Mb - used: 3969.53 Mb (54%) - free: 3406.70 Mb (46%)
Actual on this server is a little less than 4 gb.
Here is the service command - "check_xi_service_nsclient!advent!MEMUSE!-w 85 -c 95"
Machine 2 - Desktop - Windows 7
Memory usage: total:3580.87 Mb - used: 2252.14 Mb (63%) - free: 1328.73 Mb (37%)
check_xi_service_nsclient!advent!MEMUSE!-w 85 -c 95
Actual memory is 2 gb.
Please help.
We installed Nagios XI on centos OS 5.5 couple of days back.
We installed the windows agent on a windows desktop and windows server.
We used the configuration wizard to set up monitoring.
The memory result its getting is double.
Machine 1 - Windows server 2003:
Memory usage: total:7376.23 Mb - used: 3969.53 Mb (54%) - free: 3406.70 Mb (46%)
Actual on this server is a little less than 4 gb.
Here is the service command - "check_xi_service_nsclient!advent!MEMUSE!-w 85 -c 95"
Machine 2 - Desktop - Windows 7
Memory usage: total:3580.87 Mb - used: 2252.14 Mb (63%) - free: 1328.73 Mb (37%)
check_xi_service_nsclient!advent!MEMUSE!-w 85 -c 95
Actual memory is 2 gb.
Please help.
Re: Double Momory on Nagios XI
This appears to be a known issue with check_nt as it is pooling both the physical and virtual memory. I am creating a test server do make you a step-by-step process to help remedy this.
Re: Double Momory on Nagios XI
I will be making some extensive documentation in the future as what exists isn't very clear.
For your case we will need to enable the NRPE Listener in NSClient++
On the client machine
1. Edit C:\Program Files\NSClient++\nsc.ini
2. Uncomment the NRPEListener.dll option (around line 20)
3. Uncomment the allow_arguments option and set its value to 1
4. Save the modified nsc.ini file
5. Restart the NSClient from a command prompt with the follow commands:
From the Nagios XI server, the following command can be used to check physical memory (substitute the IP address to match your client machine)
For your case we will need to enable the NRPE Listener in NSClient++
On the client machine
1. Edit C:\Program Files\NSClient++\nsc.ini
2. Uncomment the NRPEListener.dll option (around line 20)
3. Uncomment the allow_arguments option and set its value to 1
4. Save the modified nsc.ini file
5. Restart the NSClient from a command prompt with the follow commands:
Code: Select all
net stop nsclientpp
net start nsclientpp
From the Nagios XI server, the following command can be used to check physical memory (substitute the IP address to match your client machine)
Code: Select all
/user/local/nagios/libexec/check_nrpe -H 192.168.0.1 -c CheckMem -a MaxWarn=80% MaxCrit=90% ShowAll type=physical
Re: Double Momory on Nagios XI
Thanks for your help and update. Will test and let you know.
Re: Double Momory on Nagios XI
My pleasure and update us on the progress 

Re: Double Momory on Nagios XI
I ran as you said but I get the following:
[nagios@localhost root]$ /usr/local/nagios/libexec/check_nrpe -H 10.1.1.232 -c CheckMem -a MaxWarn=80% MaxCrit=90% ShowAll type=physical
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
Please advise.
[nagios@localhost root]$ /usr/local/nagios/libexec/check_nrpe -H 10.1.1.232 -c CheckMem -a MaxWarn=80% MaxCrit=90% ShowAll type=physical
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
Please advise.
Re: Double Momory on Nagios XI
First thing you should do is check the remote server logs for an error message. This error could be
due to the following problem:
– The check_nrpe plugin was unable to complete an SSL handshake with the NRPE daemon. An error
message in the logs should indicate whether or not this was the case. Check the versions of OpenSSL that
are installed on the monitoring host and remote host. If you're running a commercial version of SSL on the
remote host there might be some compatibility problems.
This will be located on the client machine in the NSClient++ folder, "nsclient.log"
Also, you may find this helpful as well:
http://nagios.sourceforge.net/docs/nrpe/NRPE.pdf
due to the following problem:
– The check_nrpe plugin was unable to complete an SSL handshake with the NRPE daemon. An error
message in the logs should indicate whether or not this was the case. Check the versions of OpenSSL that
are installed on the monitoring host and remote host. If you're running a commercial version of SSL on the
remote host there might be some compatibility problems.
This will be located on the client machine in the NSClient++ folder, "nsclient.log"
Also, you may find this helpful as well:
http://nagios.sourceforge.net/docs/nrpe/NRPE.pdf
Re: Double Momory on Nagios XI
Thanks for pointing to the log.
[root@localhost ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.1.232 -c CheckMem -a MaxWarn=80% MaxCrit=90% ShowAll type=physical
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
Here is the data from the log.
2011-04-06 16:38:33: error:modules\NRPEListener\NRPEListener.cpp:393: Request contained arguments (not currently allowed, check the allow_arguments option).
2011-04-06 16:38:33: error:modules\NRPEListener\NRPEListener.cpp:365: NRPEException: Request contained arguments (not currently allowed, check the allow_arguments option).
Some parameter is not correct.
But when I do the following, it seems to be fine.
[root@localhost ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.1.232
I (0.3.8.75 2010-05-27) seem to be doing fine...
[root@localhost ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.1.232 -c CheckMem -a MaxWarn=80% MaxCrit=90% ShowAll type=physical
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
Here is the data from the log.
2011-04-06 16:38:33: error:modules\NRPEListener\NRPEListener.cpp:393: Request contained arguments (not currently allowed, check the allow_arguments option).
2011-04-06 16:38:33: error:modules\NRPEListener\NRPEListener.cpp:365: NRPEException: Request contained arguments (not currently allowed, check the allow_arguments option).
Some parameter is not correct.
But when I do the following, it seems to be fine.
[root@localhost ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.1.232
I (0.3.8.75 2010-05-27) seem to be doing fine...
-
- Posts: 1128
- Joined: Wed Mar 03, 2010 12:38 pm
- Location: St. Paul, MN, USA
- Contact:
Re: Double Momory on Nagios XI
allow_arguments is a setting in the NRPE configuration on the *target* system. You will have to enable that.
Re: Double Momory on Nagios XI
oppss...I uncommented the allow_arguments=1 in the external section and not in the NRPE section.
One I did it correctly, and bounced the clients ...it worked
[root@localhost ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.1.232 -c CheckMem -a MaxWarn=80% MaxCrit=90% ShowAll type=physical
WARNING: physical memory: Total: 3.37G - Used: 2.77G (82%) - Free: 617M (18%) > warning|'physical memory %'=82%;80;90; 'physical memory'=2.7G;2.69;3.03;0;3.37;
Thanks for your help.
I will try to put this check in manually, which I am still learning
.
One I did it correctly, and bounced the clients ...it worked

[root@localhost ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.1.232 -c CheckMem -a MaxWarn=80% MaxCrit=90% ShowAll type=physical
WARNING: physical memory: Total: 3.37G - Used: 2.77G (82%) - Free: 617M (18%) > warning|'physical memory %'=82%;80;90; 'physical memory'=2.7G;2.69;3.03;0;3.37;
Thanks for your help.
I will try to put this check in manually, which I am still learning
