Fedora Salt Master - New installation
-
firewall-cmd --list-ports 4505/tcp 4506/tcp [root@localhost ~]# systemctl stop salt-master [root@localhost ~]# systemctl stop salt-master.service [root@localhost ~]# systemctl start salt-master.service [root@localhost ~]# systemctl status salt-master.service ● salt-master.service - The Salt Master Server Loaded: loaded (/usr/lib/systemd/system/salt-master.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2019-05-08 16:31:42 EDT; 5s ago Docs: man:salt-master(1) file:///usr/share/doc/salt/html/contents.html https://docs.saltstack.com/en/latest/contents.html Main PID: 3121 (salt-master) Tasks: 27 (limit: 2350) Memory: 387.5M CGroup: /system.slice/salt-master.service ├─3121 /usr/bin/python2.7 /usr/bin/salt-master ├─3128 /usr/bin/python2.7 /usr/bin/salt-master ├─3130 /usr/bin/python2.7 /usr/bin/salt-master ├─3131 /usr/bin/python2.7 /usr/bin/salt-master ├─3134 /usr/bin/python2.7 /usr/bin/salt-master ├─3135 /usr/bin/python2.7 /usr/bin/salt-master ├─3136 /usr/bin/python2.7 /usr/bin/salt-master ├─3137 /usr/bin/python2.7 /usr/bin/salt-master ├─3139 /usr/bin/python2.7 /usr/bin/salt-master ├─3145 /usr/bin/python2.7 /usr/bin/salt-master ├─3146 /usr/bin/python2.7 /usr/bin/salt-master ├─3147 /usr/bin/python2.7 /usr/bin/salt-master ├─3150 /usr/bin/python2.7 /usr/bin/salt-master ├─3333 /usr/bin/python2.7 /usr/bin/salt-master ├─3334 /usr/bin/python2.7 /usr/bin/salt-master ├─3335 /usr/bin/python2.7 /usr/bin/salt-master ├─3336 /usr/bin/python2.7 /usr/bin/salt-master └─3339 /usr/bin/python2.7 /usr/bin/salt-master May 08 16:31:41 localhost.localdomain systemd[1]: Starting The Salt Master Server... May 08 16:31:41 localhost.localdomain salt-master[3121]: /usr/lib/python2.7/site-packages/salt/scripts.py:102: DeprecationWarning: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 > May 08 16:31:42 localhost.localdomain systemd[1]: Started The Salt Master Server. [root@localhost ~]# salt-master --log-level=debug /usr/lib/python2.7/site-packages/salt/scripts.py:102: DeprecationWarning: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. Salt will drop support for Python 2.7 in the Sodium release or later. [DEBUG ] Reading configuration from /etc/salt/master [DEBUG ] Configuration file path: /etc/salt/master [WARNING ] Insecure logging configuration detected! Sensitive data may be logged. [INFO ] Setting up the Salt Master [WARNING ] Unable to bind socket master-ip:4505, error: [Errno 98] Address already in use; Is there another salt-master running? [INFO ] The Salt Master is shut down [DEBUG ] Stopping the multiprocessing logging queue listener [DEBUG ] closing multiprocessing queue [DEBUG ] joining multiprocessing queue thread [DEBUG ] Stopped the multiprocessing logging queue listener The salt master is shutdown. The ports are not available to bind -
firewall-cmd --list-all FedoraServer (active) target: default icmp-block-inversion: no interfaces: enp0s3 sources: services: cockpit dhcpv6-client ssh ports: 4505/tcp 4506/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: -
Do a netstat -tulpn again. Anytime you see that those ports are in use, that means that Salt-Master is running. Not sure what is starting it, but there is no question that it is being started somewhere. Only one copy can bind to the ports.
-
@scottalanmiller said in Fedora Salt Master - New installation:
Do a netstat -tulpn again.
netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 803/sshd tcp 0 0 master-ip:4505 0.0.0.0:* LISTEN 1019/python2.7 tcp 0 0 master-ip:4506 0.0.0.0:* LISTEN 1025/python2.7 tcp6 0 0 :::22 :::* LISTEN 803/sshd tcp6 0 0 :::9090 :::* LISTEN 1/systemd udp 0 0 127.0.0.1:323 0.0.0.0:* 749/chronyd udp 0 0 0.0.0.0:68 0.0.0.0:* 916/dhclient udp6 0 0 ::1:323 :::* 749/chronyd -
Finally!
salt-key -A The following keys are going to be accepted: Unaccepted Keys: admins-MacBook-Air.local -
@DustinB3403 said in Fedora Salt Master - New installation:
[root@localhost ~]# salt-master --log-level=debug
Doesn't this mean that you are starting the salt-master via the CLI and setting the log-level to debug? Stop the salt-master service with systemctl and rerun this command. I bet the output will be different.
-
@coliver said in Fedora Salt Master - New installation:
@DustinB3403 said in Fedora Salt Master - New installation:
[root@localhost ~]# salt-master --log-level=debug
Doesn't this mean that you are starting the salt-master via the CLI and setting the log-level to debug? Stop the salt-master service with systemctl and rerun this command. I be the output will be different.
Correct. He is trying to start a second instance.
-
@JaredBusch said in Fedora Salt Master - New installation:
Correct. He is trying to start a second instance.
Technically just following the official documentation. If it starts a second instance shame on them for not clarifying that point.
As the documentation reads, it's just to pull detailed logs.
-
@coliver said in Fedora Salt Master - New installation:
Doesn't this mean that you are starting the salt-master via the CLI
That's what I kept saying
-
@DustinB3403 said in Fedora Salt Master - New installation:
@JaredBusch said in Fedora Salt Master - New installation:
Correct. He is trying to start a second instance.
Technically just following the official documentation. If it starts a second instance shame on them for not clarifying that point.
As the documentation reads, it's just to pull detailed logs.
I read the doc, I don't see it ever saying to do that. Where did you get that command from?
-
@scottalanmiller said in Fedora Salt Master - New installation:
Where did you get that command from?
https://docs.saltstack.com/en/2015.8/ref/configuration/index.html
-
Literally says:
It's pretty clear.
-
@coliver said in Fedora Salt Master - New installation:
Literally says:
It's pretty clear.
Ah, not part of the installation docs. That's why I didn't see it. Going through the installation, it is all set by the end of it, not sure where this configuration page pops in, but that's causing the problem. It was all installed and configured previously by following the installation guide.
-
@scottalanmiller said in Fedora Salt Master - New installation:
Do a netstat -tulpn again. Anytime you see that those ports are in use, that means that Salt-Master is running. Not sure what is starting it, but there is no question that it is being started somewhere. Only one copy can bind to the ports.
I was wondering if this was the issue - that Dustin is trying to start a second copy.
-
@Dashrender said in Fedora Salt Master - New installation:
@scottalanmiller said in Fedora Salt Master - New installation:
Do a netstat -tulpn again. Anytime you see that those ports are in use, that means that Salt-Master is running. Not sure what is starting it, but there is no question that it is being started somewhere. Only one copy can bind to the ports.
I was wondering if this was the issue - that Dustin is trying to start a second copy.
So this issue here is that there is an installation guide that gets you fully up and running. There there is a full reference for doing everything by hand. The first part was set up using the installation guide. Then that command to start the process manually was buried deep in the commands reference, disconnected from the installation guide. The first bit is a one page installer than is conclusive, a couple commands and you are done.
The configuration guide is for people doing everything by hand, such as writing your own start up scripts instead of using the ones from the installer. So the first part assumes a standard installation. The second part assumes you are constructing the system manually and haven't used the first part.
-
This is the installation page. You can see how short it is.
https://docs.saltstack.com/en/2015.8/topics/installation/fedora.html
-
Here is the problem, I think...
https://docs.saltstack.com/en/2015.8/topics/troubleshooting/master.html
So if you go through their massive manual, they have a troubleshooting section. And they tell you to run Master in the foreground for troubleshooting. They are assuming that you will stop it in the background first, but they never mention it. It's not part of the installation, but it probably should have a note about stopping any background processes first as easily a lot of people won't realize you can have both.
-
Oh, Dustin just showed me where there is a link to the "Configuring" page as an instruction on the installation page. That's BS. It's unneeded (generally) and telling you to start it again there is totally wrong given where you are coming from.
-
And based on the "Configuring Salt" link, it goes to "post install tasks" and that is where the step comes from.
I'll admit I completely skipped firewalld, but once I did and had it sorted was I mostly there.
Their documentation is weird, as click "next" takes you to the next OS install process, so the "Configure salt" link is the logical step in the guide.
-
And really, all I'm looking for is a convenient way setup my user workstations, and update them without the Apple overhead, including with brew commands.
