Sysctl type fails on some systems when run from a backgrounded puppet agent about puppet-augeasproviders HOT 4 CLOSED

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.

from puppet-augeasproviders.

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.

# locate Sysctl.rb sysctl.rb
/var/lib/puppet/lib/puppet/type/sysctl.rb

# grep -Ril sysctl /var/lib/puppet/lib
/var/lib/puppet/lib/puppet/type/sysctl.rb
/var/lib/puppet/lib/puppet/provider/sysctl/augeas.rb

# head /var/lib/puppet/lib/puppet/type/sysctl.rb
# Manages entries in /etc/sysctl.conf
#
# Copyright (c) 2012 Dominic Cleal
# Licensed under the Apache License, Version 2.0

Puppet::Type.newtype(:sysctl) do
  @doc = "Manages entries in /etc/sysctl.conf."

  ensurable

from puppet-augeasproviders.

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.

from puppet-augeasproviders.

Closing, hopefully that fixed it.

from puppet-augeasproviders.