It should modify the firewall to allow all of the ports Networker uses and can use. We noticed that while the error would claim an authentication failure, you could see the authentication succeed in the debug logs, but would fail later to connect to set up the save.
CentOS went to using firewalld instead of iptables, so changes made to the iptables can't be static between reboots and I simply wasn't smart enough to figure out how make the changes using the firewalld commands/configuration. The other option as noted above is just turn off the fire wall.
Faced the same error. Upgraded java to the latest version. Rerun the authc configuration script e/opt/nsr/authc-server/scripts/authc_configure.sh . Then restarted the Networker services on the host. After restarting services, I run the nmc configuration, and it completed successfully.
Was trying to setup this in lab environment and run into the error. Stopped the firewall service on both the hosts (nmc and networker) and it was able to proceed.
NMarc1
18 Posts
0
November 15th, 2016 21:00
Login to server as root
Using following command see port 9090 used by another program
netstat -tulpn or netstat -tulpn | grep 9090
Princeaijazbhat
41 Posts
0
December 31st, 2017 05:00
Update hostfile in Oder for nmc to reach networker server which is authentication host .
Kleinenbroich
86 Posts
0
January 2nd, 2018 06:00
Check the /etc/hosts file: Did localhost.localdomain point to 127.0.0.1
pantelimon_alex
1 Rookie
•
10 Posts
0
January 4th, 2018 08:00
On the AUTHC Server "May it be the backup server" run this opt/nsr/authc-server/scripts/ authc_configure.sh and fallow steps
After is completed on NMC Server go an run "/opt/lgtonmc/bin/gstauthcfg -ct -h AUTH_Server "may it be backup server" -p 9090 "
Restart all services and go on
Davidtgnome
1 Rookie
•
66 Posts
0
January 17th, 2018 06:00
On our CentOS servers after every reboot we have to log in and run the following command.
iptables -I INPUT 11 -p tcp -m tcp --dport 7937:9936 -j ACCEPT
It should modify the firewall to allow all of the ports Networker uses and can use. We noticed that while the error would claim an authentication failure, you could see the authentication succeed in the debug logs, but would fail later to connect to set up the save.
CentOS went to using firewalld instead of iptables, so changes made to the iptables can't be static between reboots and I simply wasn't smart enough to figure out how make the changes using the firewalld commands/configuration. The other option as noted above is just turn off the fire wall.
Princeaijazbhat
41 Posts
0
January 17th, 2018 23:00
#sudo firewall-cmd --state
#sudo systemctl status firewalld
To stop and disable it:
sudo systemctl stop firewalld
sudo systemctl disable firewalld
Davidtgnome
1 Rookie
•
66 Posts
0
January 18th, 2018 04:00
Yes but that disables it entirely. Which is not what I want. I want the bloody ports to remain open after a reboot.
mr_robot
1 Rookie
•
30 Posts
0
December 7th, 2020 18:00
Faced the same error. Upgraded java to the latest version. Rerun the authc configuration script e/opt/nsr/authc-server/scripts/authc_configure.sh . Then restarted the Networker services on the host. After restarting services, I run the nmc configuration, and it completed successfully.
mr_robot
1 Rookie
•
30 Posts
0
January 8th, 2021 06:00
Was trying to setup this in lab environment and run into the error. Stopped the firewall service on both the hosts (nmc and networker) and it was able to proceed.