-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Sysctl type fails on some systems when run from a backgrounded puppet agent #47
Comments
It looks like a different provider is being used ("ProviderParsed") but with the sysctl type from augeasproviders, perhaps check for any other conflicting modules that supply a sysctl provider. You could try setting the provider explicitly to "augeas" too. |
I suspect your right and some part of the provider from duritong/puppet-sysctl, which I was previously using, is hanging around but I'm at a total loss to find it.
|
Looking at the pids in the initial logs, it appears you have one long running process (daemonised?) and perhaps a puppet agent -t run too. Have you restarted the daemon since switching providers? It's likely it still has the old code loaded. Other thoughts: if the agent is on the puppetmaster, check the module directories are clear of the old provider, since it could be loading the provider from here. Also check other environments, since there's no separation of plugins between environments. You could also try adding --trace to the command line, which might point out the file it's loading from. |
Closing, hopefully that fixed it. |
I'm baffled as to why I'm seeing failures with the sysctl type on some el6.x systems in prod. I assume it has something to do the system setup, and not the provider, but I'm scratching my head as to the root cause. When the agent is run as puppet agent --test, even from ssh without a pty, it works, so I've been unable to reproduce the failure to debug it. I'm hoping someone has seen this error before or has a suggestion as to how to debug it.
The text was updated successfully, but these errors were encountered: