Salt Stack communication issues
-
I don't see anywhere where you put salt into the /etc/hosts file of the minion, or put it into DNS. Is that maybe the issue?
-
@reid-cooper said in Salt Stack communication issues:
I don't see anywhere where you put salt into the /etc/hosts file of the minion, or put it into DNS. Is that maybe the issue?
I did. I can also ping salt from the minion and get a response from the master.
-
@fuznutz04 said in Salt Stack communication issues:
@reid-cooper said in Salt Stack communication issues:
I don't see anywhere where you put salt into the /etc/hosts file of the minion, or put it into DNS. Is that maybe the issue?
I did. I can also ping salt from the minion and get a response from the master.
Nothing shows up using this command on the master:
salt-key -L
-
Did you open the right ports on the master?
Did you verify that master's process is running?
-
@black3dynamite said in Salt Stack communication issues:
@fuznutz04 said in Salt Stack communication issues:
@reid-cooper said in Salt Stack communication issues:
I don't see anywhere where you put salt into the /etc/hosts file of the minion, or put it into DNS. Is that maybe the issue?
I did. I can also ping salt from the minion and get a response from the master.
Nothing shows up using this command on the master:
salt-key -L
negative. Just this:
[root@salt ~]# salt-key -L Accepted Keys: Denied Keys: Unaccepted Keys: salt Rejected Keys:
The unaccepted key salt of course is the master itself.
-
@scottalanmiller said in Salt Stack communication issues:
Did you open the right ports on the master?
Did you verify that master's process is running?
I opened ports 4505 and 4506/tcp by issuing:
firewall-cmd --permanent --zone=public --add-port=4505-4506/tcp firewall-cmd --reload
-
@scottalanmiller said in Salt Stack communication issues:
Did you verify that master's process is running?
Yes.
[root@salt ~]# systemctl status salt-master ● salt-master.service - The Salt Master Server Loaded: loaded (/usr/lib/systemd/system/salt-master.service; enabled; vendor preset: disabled Active: active (running) since Fri 2017-11-17 10:21:19 EST; 28min ago Main PID: 778 (salt-master) Tasks: 30 (limit: 19660) CGroup: /system.slice/salt-master.service ├─778 /usr/bin/python /usr/bin/salt-master ├─909 /usr/bin/python /usr/bin/salt-master ├─930 /usr/bin/python /usr/bin/salt-master ├─931 /usr/bin/python /usr/bin/salt-master ├─932 /usr/bin/python /usr/bin/salt-master ├─933 /usr/bin/python /usr/bin/salt-master ├─934 /usr/bin/python /usr/bin/salt-master ├─935 /usr/bin/python /usr/bin/salt-master ├─936 /usr/bin/python /usr/bin/salt-master ├─937 /usr/bin/python /usr/bin/salt-master ├─938 /usr/bin/python /usr/bin/salt-master └─939 /usr/bin/python /usr/bin/salt-master Nov 17 10:21:09 salt systemd[1]: Starting The Salt Master Server... Nov 17 10:21:19 salt systemd[1]: Started The Salt Master Server.
-
@fuznutz04 said in Salt Stack communication issues:
@scottalanmiller said in Salt Stack communication issues:
Did you open the right ports on the master?
Did you verify that master's process is running?
I opened ports 4505 and 4506/tcp by issuing:
firewall-cmd --permanent --zone=public --add-port=4505-4506/tcp firewall-cmd --reload
And public is definitely the right zone?
-
@scottalanmiller said in Salt Stack communication issues:
@fuznutz04 said in Salt Stack communication issues:
@scottalanmiller said in Salt Stack communication issues:
Did you open the right ports on the master?
Did you verify that master's process is running?
I opened ports 4505 and 4506/tcp by issuing:
firewall-cmd --permanent --zone=public --add-port=4505-4506/tcp firewall-cmd --reload
And public is definitely the right zone?
FacePalm. There was only 1 zone listed on the firewall, and it was called FedoraServer. Opening the ports in this zone of course solved the issue.
-
@fuznutz04 said in Salt Stack communication issues:
@scottalanmiller said in Salt Stack communication issues:
@fuznutz04 said in Salt Stack communication issues:
@scottalanmiller said in Salt Stack communication issues:
Did you open the right ports on the master?
Did you verify that master's process is running?
I opened ports 4505 and 4506/tcp by issuing:
firewall-cmd --permanent --zone=public --add-port=4505-4506/tcp firewall-cmd --reload
And public is definitely the right zone?
FacePalm. There was only 1 zone listed on the firewall, and it was called FedoraServer. Opening the ports in this zone of course solved the issue.
I was wondering as FedoraServer is the default.
-
@fuznutz04 You ran into this "problem" because you used the netinstall iso.
With the DVD iso FedoraServer is the default. -
Learn something new every day. I'm so used to CentOS, so I'm not used to the differences with Fedora.
Thanks!