New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Salt master cache handling drains cpu resources and fails communication with minion #17193
Comments
So, seeing the salt-master process using 100% in "top" we ran strace to see what was going on with the process. We noticed that the master seemed to be stuck in a loop tryng to create a directory in the salt master cache. We received about 15MB of strace logs for this behavious in a couple of seconds.
We solved it by stopping the service, moving the |
Duplicate of #15719 |
I have an issue where the master fails with a timeout when trying to apply a state to a minion using 2014.1.13 on both master and minion. Both are running Ubuntu 14.04.
The master fails with the message: "Failed to authenticate, is this user permitted to execute commands?"
This is a new problem that I did not have before upgrading to 2014.1.13. I ran 2014.1.10 (or 11) before upgrading. I have had problems earlier with salt not printing any result data although exit code is 0. However, trying again and restarting services has usually solved the problem. This time, I just can't get the state to apply. As you can see in the logs, the ping works some times.
Checking "top" after salt prints the error message shows salt-master at 100% cpu. The salt-master is running as root.
Here are two links to master and minion debugging where the issue should become more clear:
https://www.refheap.com/92763
https://www.refheap.com/92765
This issue seems related: #15719
The text was updated successfully, but these errors were encountered: