Check_nrpe socket time out after 10 seconds for windows host

[rohithroki]

i am using the plugin check_nrpe and the commands are check_nrpe_mem and check_nrpe_swap for monitoring the physical and swap memory

[rkennedy]

Can you show us the full check_command that these services are running, as well as the plugins they're utilizing?

We need this information to understand further. This could be specific to the plugins and how they're being executed.

If checks are timing out regardless, try appending -t 60 to them, which will add a 60 second timeout. Let us know the full input / output from the CLI.

[rohithroki]

i am trying with the below command from my nagios server

/usr/local/nagios/libex/check_nrpe -H ipadressof client -t 120

even thaugh i give 120 also i am getting the same error

socket timed out after 120 seconds

[rkennedy]

On the client machine, do you see anything populate in /var/log/messages? What happens if you try with the -n flag? Can you show us a screenshot as well?

[rohithroki]

client isa windows host with Windows 2008R2 OS installed

[rkennedy]

Please post your NSClient++ log file for us to look at, and also on the windows machine run netstat -an | findstr 5666. We'll need to see the output for this command.

[rohithroki]

please find the details attached

[Box293]

This looks interesting:

2016-05-26 12:44:01: error:include\Socket.h:691: bind failed: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.
2016-05-26 12:44:01: error:include\Socket.h:722: Socket did not start properly, we will now do nothing...

Can you check that you only have one instance of NSClient++ installed and running (look in services.msc)

http://forums.nsclient.org/t/socket-h-7 ... start/3077

[rohithroki]

yes i have only one nsclient instance running on the server. Attaching the SS

[rkennedy]

If you stop that service from running using net stop nscp, and then run netstat -an | findstr 5666 what is the output?

On my system, it shows the port as listening for example -

Code: Select all

C:\Users\rkennedy>netstat -an | findstr 5666
  TCP    0.0.0.0:5666           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5666           0.0.0.0:0              LISTENING
  TCP    [::]:5666              [::]:0                 LISTENING

Are your other service checks working for that server, or are they using check_nt? I just copied over your NSClient++ configuration to my system and 5666 isn't listening.

Code: Select all

C:\Windows\system32>netstat -an | findstr 5666
  TCP    0.0.0.0:5666           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5666           0.0.0.0:0              LISTENING
  TCP    [::]:5666              [::]:0                 LISTENING

C:\Windows\system32>net stop nscp
The NSClient++ (x64) service is stopping.
The NSClient++ (x64) service was stopped successfully.


C:\Windows\system32>net start nscp

The NSClient++ (x64) service was started successfully.


C:\Windows\system32>netstat -an | findstr 5666

Is upgrading to 0.4.3 of NSClient++ an option for you? I helped a few customers get this version going this week, and it worked without issues. https://assets.nagios.com/downloads/nag ... .3-x64.msi (depending on the browser you download with, you may need to rename the .man to .msi)