NRPE Socket Timeout when running check that loads PSSNapin f
Posted: Tue May 19, 2015 3:33 pm
We have a Nagios Core server that is showing "CHECK_NRPE: Socket timeout after 30 seconds" on checks that require the Exchange pssnapin to load. The scripts run correctly and quick locally on the Exchange server and other NRPE checks run fine on the server like alias_cpu and alias_disk. The checks that fail on the Exchange server succeed on other Exchange servers. I have copied the script (https://exchange.nagios.org/directory/P ... es/details) and the nsclient.ini file from a working server and still have the issue. The nsclient.log on the server that is not working shows this: "e:c:\build\nscp\include\socket/connection.hpp:146: Failed to send data: The file handle supplied is not valid"
One fix that we have done to get some of the servers to work was to not require "Check for publisher's certificate revocation" in internet options.
The command that I am using on the Nagios server command line to test is: ./check_nrpe -H hostname.domain -c check_queue_health -t 30
The nsclient.ini file has this:
; NSClient server - A simple server that listens for incoming NSClient (check_nt) connection and handles them. Although NRPE is the preferred method NSClient is fully supported and can be used for simplicity or for compatibility.
NSClientServer = 1
; Undocumented section
[/settings/external scripts/scripts]
check_queue_health=cmd /c echo Scripts\QueueHealth.ps1 | PowerShell.exe -Command -
; Undocumented section
[/settings/default]
This is happening on Exchange 2007 SP3 UR 16 servers on Windows 2008 R2 SP1 and Exchange 2013 SP1 UR8 on Server 2012 R2
Any ideas on what else to try?
Thanks
One fix that we have done to get some of the servers to work was to not require "Check for publisher's certificate revocation" in internet options.
The command that I am using on the Nagios server command line to test is: ./check_nrpe -H hostname.domain -c check_queue_health -t 30
The nsclient.ini file has this:
; NSClient server - A simple server that listens for incoming NSClient (check_nt) connection and handles them. Although NRPE is the preferred method NSClient is fully supported and can be used for simplicity or for compatibility.
NSClientServer = 1
; Undocumented section
[/settings/external scripts/scripts]
check_queue_health=cmd /c echo Scripts\QueueHealth.ps1 | PowerShell.exe -Command -
; Undocumented section
[/settings/default]
This is happening on Exchange 2007 SP3 UR 16 servers on Windows 2008 R2 SP1 and Exchange 2013 SP1 UR8 on Server 2012 R2
Any ideas on what else to try?
Thanks