Nagios Support Forum

I solved the problem. I had to add a password to the NSC.ini file and Nagios. It only worked if I removed the host from Core Config then readded it. I also had to remove the /usr/local/nagios/etc/hosts/server.cfg file Glad to hear it. check_nt -v MEMUSE shows the complete memory (physical memory + ...

I solved the problem. I had to add a password to the NSC.ini file and Nagios. It only worked if I removed the host from Core Config then readded it. I also had to remove the /usr/local/nagios/etc/hosts/server.cfg file

So, now that you have the listener working, what do you get when you run # cd /usr/local/nagios/libexec # ./check_nt -H <your_target_machine_IP_address> -s <your_password> -p 12489 -v MEMUSE -w 80 -c 90 [root@localhost libexec]# ./check_nt -H 192.168.1.xx -p 12489 -v MEMUSE -w 80 -c 90 could not fe...

scottwilkerson wrote:

whitetree wrote: There is no password set for this machine as it is internal.

Ludmil was referring to the passphrase in the nsc.ini and on the server. They need to share and use the same password

Understood. I did not set a password in the Monitoring Wizard or on the NSClient++ program or it's nsc.ini file.

lmiltchev wrote:When you run your check from the command line, do you use the same password as the one listed in the nsc.ini file? You can play around with this - changing and/or temporarily removing the password altogether.

There is no password set for this machine as it is internal.

in your nsc.ini, in the [modules] section, make sure you have NSClientListener.dll not ;NSClientListener.dll The NSClientListener.dll is what will listen on port 12489. If you make this change, restart the NSClient++ service and try again. Done. Still not listening... One thing that is striking me ...

Can you telnet to port 12489 from your Nagios server? # telnet <target_machine_IP_address> 12489 I cannot "connection refused" Also, on your windows machine you can open a Command Prompt (Run->cmd.exe->Enter) and run: # netstat -an |find /i "listening" > c:openports.txt You can ...

Did you add both IP addresses to the nsc.ini file (on this line)? allowed_hosts= Note: After any change in the nsc.ini file, you must restart the nsclient++ service, so that the changes can take effect. I would suggest testing it from the command line first. Run something simple from the command li...

I've got my Nagios server configured with two NICs. One is a 192.168.1.xx and the other is my public IP xx.xx.xx.xx My remote servers that are not in my local network have no problem connecting and talking to Nagios using the public IP address. However the Windows machines in my local network get a ...