Jul 08 10:59:22 v321p601 systemd: rvice start operation timed out. Jul 08 10:58:26 v321p601 salt-master: Setting up the Salt Master Jul 08 10:57:52 v321p601 systemd: Starting The Salt Master Server. Main PID: 5780 (code=killed, signal=TERM) Process: 5780 ExecStart=/usr/bin/salt-master (code=killed, signal=TERM) Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled)ĭrop-In: /etc/systemd/system/Īctive: failed (Result: timeout) since Wed 10:59:22 -03 54min agoįile:///usr/share/doc/salt/html/contents.html In my case, the salt-master failed to start: Then, issue salt '*' service.status and check if the master is running.ĭo a check of the salt-master service systemctl status salt-master Look for errors in the /var/log/salt/minion Why am I seeing this problem and how do I correct it? Version: Red Hat Enterprise Linux Server 6.10 Santiago This is my salt versions report: salt -versions-report I've opened up the salt ports on the firewall.īut the salt server still isn't responding. I have accepted the key for the server on the salt master. If you are confident that you are connecting to a valid Salt Master, then remove the master public key and restart the Salt Minion. The master may need to be updated if it is a version of Salt lower than 2017.7.2, or 11:57:37,990 The Salt Master server's public key did not authenticate!
#MINION MASTERS CODES 2018 VERIFICATION#
Either enable signature verification on the minion or disable signing the public key on the master!
11:57:37,990 The masters sent its public-key signature, but signature verification is not enabled on the minion. 11:57:27,935 Error while bringing up minion for multi-master. I'm getting some errors when I start salt minions: Error while bringing up minion for multi-master.
0 kommentar(er)
