server and client can ping, but services aren't reporting

[travisjburrell]

Our datacenter lost connectivity for ~40mins this afternoon. We were greeted with a mountain of notifications when the firewall came back up, of course, but since connectivity has been restored, each of the instances monitored in AWS via IPSec tunnel have reported all failed services.

• host reports "up" in Nagios
• client can ping server
• server can ping client
• ncpa_listener/_passive are both running on the clients

The only way for us to connect to these instances is via VPN to our datacenter, & then through the IPSec tunnel. The tunnel reports up, and indeed, I can ssh to each of the affected clients without issue.

Code: Select all

[root@nagios libexec]# ./check_ncpa.py -H <clientIP> -t <token> -M 'processes'
UNKNOWN: Execution exceeded timeout threshold of 60s

Any help would be greatly appreciated.

[travisjburrell]

There's also this (to one of the affected clients):

Code: Select all

[root@nagios ~]# nmap 10.253.1.230 -Pn -p 5693

Starting Nmap 6.47 ( http://nmap.org ) at 2022-01-28 09:27 EST
Nmap scan report for 10.253.1.230
Host is up (0.033s latency).
PORT     STATE SERVICE
5693/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds

(I've tried restarting the ncpa services already)

[dchurch]

I see you have an open ticket for this issue in our ticketing system, so I will be closing this thread. In the future, please open only one forum post or ticket per issue so we can best focus our efforts. Thank you!

[pbroste]

Hello @travisjburrell

Thanks for reaching out, appears from the 'nmap' results from port 5693 to that server. Want to run the following to help verify:

Code: Select all

/usr/local/nagios/libexec/check_ncpa.py -H <yourhostaddresshere> -t <yourtokenhere> --list --verbose

You posted that you are able to ssh to the server and wanted to suggest the option to configure ssh service check(s).

Thanks,
Perry