Trouble connecting to RH 6 server using NCPA

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
ronafisher2
Posts: 11
Joined: Mon Feb 08, 2021 4:46 pm

Trouble connecting to RH 6 server using NCPA

Post by ronafisher2 »

Greetings,

Running a Nagios 4.4.6 core server and using NCPA active checks on a group of hosts. All Windows hosts and a RHEL 8 server working fine.

Got a Redhat 6 server with the NCPA 2.2.2 linux 64bit client installed and listener is up. Firewall opened for default tcp 5693 on the client. Set token and IP = 0.0.0.0 in ncpa.cfg file. Doing a manual API check

[nagios@server nagios]$ /usr/local/nagios/libexec/check_ncpa.py -H remoteserver -t token -P 5693 -M 'processes' -v
Connecting to: https://remoteserver:5693/api/processes ... jS&check=1
An error occurred:
UNKNOWN: An error occured connecting to API. (Connection error: '[Errno 113] No route to host')


On the remote server ran tcpdump and it shows the nagios server hitting it

[root@remoteserver tmp]# tcpdump -i eth0 port 5693
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
16:29:22.471737 IP server.36388 > remoteserver.5693: Flags , seq 4117186990, win 29200, options [mss 1460,sackOK,TS val 2024861410 ecr 0,nop,wscale 7], length 0
^C
1 packets captured
2 packets received by filter
0 packets dropped by kernel


Any ideas?

Ron
ronafisher2
Posts: 11
Joined: Mon Feb 08, 2021 4:46 pm

Re: Trouble connecting to RH 6 server using NCPA

Post by ronafisher2 »

This was an iptables issue needing to add ACCEPT rules before REJECT rules on the client.
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: Trouble connecting to RH 6 server using NCPA

Post by benjaminsmith »

This was an iptables issue needing to add ACCEPT rules before REJECT rules on the client.
Cool. Glad you got it sorted out. We'll mark this as resolved.

Cheers,
Benjamin
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked