Unsolved Salt Minion Problems
-
@WrCombs I suggest you to change the hostnamw via hostnamectl.
What is the output of systemctl status salt-minion?
-
So after a full server reboot the salt-minion finally started but it is not properly registering its key to the master correct @WrCombs .
-
@Romo said in Salt Minion Problems:
So after a full server reboot the salt-minion finally started but it is not properly registering its key to the master correct @WrCombs .
Maybe this happen when you clone an already registered instance.
-
@Francesco-Provino the minion does have a long hostname but it is unique, also the master is properly named as salt and discoverable via dns.
-
Heres the new problem, the master doesn't have a key to accept.
-
-
My vms are all set, I'll run the installation to better help you troubleshoot this. Meanwhile lets try restarting the service
sudo service salt-minion restart -
And try checking the master again.
-
@Romo stil' nothing
-
Is the minion looking to the right master?
-
Is the master's firewall ports open for Salt to be listening?
-
@scottalanmiller said in Salt Minion Problems:
Is the minion looking to the right master?
how do I check these? I KNOW none of these commands and cant find one on the website
-
@WrCombs by default a salt minion will try communicate with a master named salt.
-
@WrCombs from your minion first try to ping your salt master by hostname so:
ping salt -
yes,
I read that part. -
-
@WrCombs said in Salt Minion Problems:
@scottalanmiller said in Salt Minion Problems:
Is the minion looking to the right master?
how do I check these? I KNOW none of these commands and cant find one on the website
Well the instructions for what to open are here:
-
-
Here is how to see the firewall rules for the public zone...
sudo firewall-cmd --zone=public --list-all -
@WrCombs said in Salt Minion Problems:
That looks wrong
That's going after the public master, not your own.
