-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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-run produces many errors and warnings #39323
Comments
How have you installed salt? We provide packages for redhat systems, but it look like you are managing salt in opt? https://repo.saltstack.com/#rhel With our packages, I am unable to replicate this issue.
Thanks, |
@gtmanfred Because of our non-homogenous environment, there's a central build script that compiles everything from source so that everything is consistent across the board regardless of OS/platform. It's encouraging to hear that the problem is local to me. I'll kickoff a fresh compile and see if I can replicate the problem and go from there. |
@d101nelson The above two PR's will fix the stack traces caused by the Windows specific salt utils. |
@gtmanfred This seems to have been something with corruption in our local PyPI repo. Got that reset and rebuilt salt-2016.11.2 and all seems good. @twangboy Thanks for the heads-up on those PRs. I'll keep those in mind if I run into them. |
I spoke to soon. Not realizing it, I inadvertently reinstalled 2016.3.3 and tested against that. So, I've installed 2011.11.2 and the problem persists. I manually applied the PRs from @twangboy and that fixed the Windows related errors but the "Exception raised when processing ...", I'm now backtracking through salt releases and 2016.3.5 runners work as expected; unfortunately, I need 2016.11.x to address some beacon issues I ran into with 2016.3.x. I'm also looking at the 2016.11.2 RPM's for any clues, too. |
@gtmanfred Found it. In my /etc/salt/master I have defined:
If I comment this out, then 'salt-run test.arg foo' runs as expected. How should I have 'runner_dirs' configured as I have custom runners. |
If you put the runners in the _runners directory in your salt file server,
you can run ’salt-run saltutil.sync_runners’ and have them synced to the
master extmods
That is how I manage them.
Daniel
…On Mon, Feb 13, 2017 at 4:52 PM d101nelson ***@***.***> wrote:
@gtmanfred <https://github.com/gtmanfred> Found it. In my
/etc/salt/master I have defined:
runner_dirs:
- /srv/runners
If I comment this out, then 'salt-run test.arg foo' runs as expected. How
should I have 'runner_dirs' configured as I have custom runners.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39323 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAssoZeFlQ7uDfx6RIpCJgYkGYQiylyYks5rcN6-gaJpZM4L91zt>
.
|
@gtmanfred I did what you suggested and it worked - but only once. Subsequent I've reordered the code in the runner so that A simple example runner demonstrates the problem.
|
Description of Issue/Question
Using 'salt-run' under salt-2016.11.2 produces many errors and warnings then just dies.
Setup
A functional master/minion setup.
Steps to Reproduce Issue
I've tried a number Salt supplied runners namely 'survey.hash', 'test.arg', and 'jobs.active'. They all produce the same errors.
On the salt-master:
Versions Report
The text was updated successfully, but these errors were encountered: