Master Configuration File not reloading

202 views
Skip to first unread message

Jordon Carpenter

unread,
Jul 20, 2017, 9:44:10 PM7/20/17
to Salt-users
I made changes to the salt master configuration file, and then restarted the service but it doesn't appear to be using the new revision. Any idea on how I can reload the /etc/salt/master config file?

Thomas Phipps

unread,
Jul 20, 2017, 10:07:23 PM7/20/17
to salt-...@googlegroups.com
restarting salt-master should reload the config if your changes are not happening then something else must be wrong. check the log file for more info. or turn up the logging.


On Thu, Jul 20, 2017 at 6:44 PM Jordon Carpenter <jordon.c...@rooksecurity.com> wrote:
I made changes to the salt master configuration file, and then restarted the service but it doesn't appear to be using the new revision. Any idea on how I can reload the /etc/salt/master config file?

--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/salt-users/499f6ae0-084d-4919-910e-c545c92b875f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jordon Carpenter

unread,
Jul 21, 2017, 8:22:53 AM7/21/17
to salt-...@googlegroups.com, Thomas Phipps
The only thing I’m seeing in the logs is this:

2017-07-21 12:20:46,951 [salt.loaded.int.grains.core                           ][WARNING ][9973] Unable to find IPv6 record for “<removed>" causing a 0:00:10.012273 second timeout when rendering grains. Set the dns or /etc/hosts for IPv6 to clear this.

But my master configuration is defiantly not loading new revision. 

Thanks,
Jordon Carpenter

Rook Security
Anticipate, Manage, & Eliminate Threats

O: 888.712.9531 x734
E: jordon.carpenter@rooksecurity.com

rookteam    rooksecurity    Rook LinkedIn


This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.
You received this message because you are subscribed to a topic in the Google Groups "Salt-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/salt-users/rSMnY2f3-uM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to salt-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/salt-users/CAPaX09jQDEMD-0740DF0%3D_g_DUxuWH6ojEvrOQz%2BFUvqt%3Druug%40mail.gmail.com.

Jordon Carpenter

unread,
Jul 21, 2017, 8:30:10 AM7/21/17
to salt-...@googlegroups.com, Thomas Phipps
Here is some more information.

[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: <removed>
[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 0.0.0.0: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

Thanks,
Jordon Carpenter

Rook Security
Anticipate, Manage, & Eliminate Threats

O: 888.712.9531 x734
E: jordon.carpenter@rooksecurity.com

rookteam    rooksecurity    Rook LinkedIn


This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.

C. R. Oldham

unread,
Jul 21, 2017, 8:56:41 AM7/21/17
to salt-...@googlegroups.com
Here's a clue:

On Jul 21, 2017, at 06:30, Jordon Carpenter <jordon.c...@rooksecurity.com> wrote:
[...]
[WARNING ] Unable to bind socket 0.0.0.0:4505, error: [Errno 98] Address already in use; Is there another salt-master running?

Do you have a zombie salt-master process hanging around?

-- 
C. R. Oldham, Engineer, SaltStack

:

Jordon Carpenter

unread,
Jul 21, 2017, 9:01:24 AM7/21/17
to salt-...@googlegroups.com, C. R. Oldham
Yes, I killed the processes and it seemed to have loaded the master configuration. Although it appears I lost communication with some of my minions in the process of doing that. 

Thanks,
Jordon Carpenter

Rook Security
Anticipate, Manage, & Eliminate Threats

O: 888.712.9531 x734
E: jordon.carpenter@rooksecurity.com

rookteam    rooksecurity    Rook LinkedIn


This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.

Reply all
Reply to author
Forward
0 new messages