NCPA on 5666 instead of 5693

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
devopsguru1
Posts: 7
Joined: Fri Nov 22, 2019 10:11 am

NCPA on 5666 instead of 5693

Post by devopsguru1 »

hi All,

My company wants to use 5666 port for NCPA instead of default port 5693, we have changed the configuration file, commented the port 5693 and opened the port 5666 in .cfg file, Can anybody help whether this procedure is right ? When I am trying to configure the NCPA wizard on last or 3rd page when I click the finish button it is throwing a message "Waiting for configuration verification..............................................." nothing i s happening even after 1 hour, Can any body suggest me how can I solve this problem!
User avatar
lmiltchev
Former Nagios Staff
Posts: 13587
Joined: Mon May 23, 2011 12:15 pm

Re: NCPA on 5666 instead of 5693

Post by lmiltchev »

What is the operating system of the client (remote system), e.g. Windows, Linux, etc.? Are you sure that nothing else is listening on port 5666? This port is usually reserved for NRPE... Is NRPE running on this system? Have you modified the firewall rules to open the port? Is the ncpa_listener service actually running on the remote box?

Run the following commands from the command line on the Nagios XI server, and show the output:

Code: Select all

nmap <client ip> -p 5666
curl -k "https://<client ip>:5666/testconnect/?token=<token>"
where you substitute <client ip> and <token> with actual values.

Also, when you ran the NCPA wizard in Nagios XI, did you change the "default" port from 5693 to 5666 in Step 1 of the wizard?

What is the version of NCPA agent and check_ncpa.py plugin that you are currently using?
Be sure to check out our Knowledgebase for helpful articles and solutions!
devopsguru1
Posts: 7
Joined: Fri Nov 22, 2019 10:11 am

Re: NCPA on 5666 instead of 5693

Post by devopsguru1 »

hi Thanks for quick response

the remote system is Windows server 2016, we dont use NRPE, i have modified the fire wall rules(inbound and outbound), though the listener was running, I have restarted the service after the changes

Yes when configuring the wizard on Nagios XI , i modified the port to 5666 instead of 5693

ONCE i go to office I can be able to run the below curl command, Thanks once again really appreciate your quick response
User avatar
lmiltchev
Former Nagios Staff
Posts: 13587
Joined: Mon May 23, 2011 12:15 pm

Re: NCPA on 5666 instead of 5693

Post by lmiltchev »

Sure, show us the output of the curl and the nmap commands whenever you get a chance. We will keep the topic open.
Be sure to check out our Knowledgebase for helpful articles and solutions!
devopsguru1
Posts: 7
Joined: Fri Nov 22, 2019 10:11 am

Re: NCPA on 5666 instead of 5693

Post by devopsguru1 »

i am struggling to login to the Nagios terminal, How do I login to the Nagios xi terminal?
User avatar
lmiltchev
Former Nagios Staff
Posts: 13587
Joined: Mon May 23, 2011 12:15 pm

Re: NCPA on 5666 instead of 5693

Post by lmiltchev »

If you are trying to do this in the GUI (using the SSH Terminal in XI), you would need to open the terminal in a new window (the first time), and add an exception. See the KB article below:

https://support.nagios.com/kb/article/n ... l-207.html

If you had a "putty" installed on your workstation, you could just open a new ssh session to your Nagios XI server, and log in as root. The "default" root password is "nagiosxi", unless you changed it. Hope this helps.
Be sure to check out our Knowledgebase for helpful articles and solutions!
adminwlt
Posts: 7
Joined: Fri Dec 06, 2019 7:28 am

Re: NCPA on 5666 instead of 5693

Post by adminwlt »

Thank you so much once again for your excellent help!

I have ran the following commands in my Nagios xi server with my terminal as per your suggestion, what should I do NOW?

[root@gxxxxxxxxxxxx2 kxxxxa]# nmap 172.xx.xx.xxx -p 5666
Starting Nmap 6.47 ( http://nmap.org ) at 2019-12-10 14:21 GMT
Nmap scan report for Gxxxxxxxxxxx2.gxxxxl.xxx.com (xxxx.xx.96.xxx)
Host is up (0.0012s latency).
PORT STATE SERVICE
5666/tcp open nrpe
---------------------------------------------------------------------------------------
[root@gxxxxxxxxxxxxx2 kxxxxa]# curl -k "https://172.xx.xx.xxx 5666/testconnect/?token=<t0ken>"
curl: (7) Failed connect to 172.xx.xx.xxx 5666:443; Connection refused
User avatar
lmiltchev
Former Nagios Staff
Posts: 13587
Joined: Mon May 23, 2011 12:15 pm

Re: NCPA on 5666 instead of 5693

Post by lmiltchev »

I asked you:
Are you sure that nothing else is listening on port 5666? This port is usually reserved for NRPE...
as I've seen this before... You cannot use the same port for NRPE and NCPA...
[root@gxxxxxxxxxxxx2 kxxxxa]# nmap 172.xx.xx.xxx -p 5666
Starting Nmap 6.47 ( http://nmap.org ) at 2019-12-10 14:21 GMT
Nmap scan report for Gxxxxxxxxxxx2.gxxxxl.xxx.com (xxxx.xx.96.xxx)
Host is up (0.0012s latency).
PORT STATE SERVICE
5666/tcp open nrpe
If you wanted to use port 5666 with NCPA, you would need to remove NRPE (or use NRPE with a different port).
Be sure to check out our Knowledgebase for helpful articles and solutions!
adminwlt
Posts: 7
Joined: Fri Dec 06, 2019 7:28 am

Re: NCPA on 5666 instead of 5693

Post by adminwlt »

HI Thanks for the response once again

How do I remove the NRPE ? i could NOT understand, can you please explain whether it is very important to remove NRPE, i have not used any NRPE Agents so how can I remove?

and 2nd query had some mistake and now I ran it succeeded

[root@gbrtwlvpdnga02 kvunna]# curl -k "https://172.xx.xx.xxx:5666/testconnect/?token=t0ken"
{
"value": "Success."
}[root@gbrtwlvpdnga02 kvunna]#

one more query is also I executed from Nagios server and its working fine but pointing to NRPE Service, please suggest how to avoid..
[root@gbrtwlvpdnga02 kvunna]# netstat -tnpal |grep :5666
tcp6 0 0 :::5666 :::* LISTEN 1263/xinetd
adminwlt
Posts: 7
Joined: Fri Dec 06, 2019 7:28 am

Re: NCPA on 5666 instead of 5693

Post by adminwlt »

I have to change the same way as I have changed the port for NCPA in my .cfg file, Am I right?
Locked