On Tue, Nov 27, 2012 at 9:06 AM, Lee Boynton <l...@lboynton.com> wrote: > Sorry, just looked in the puppet.conf file. It is indeed the storeconfigs > option. I guess I should just go ahead and use PuppetDB.
PuppetDB could be a viable work around, but this is the second time I've heard of someone running into this error with Storedconfigs. We do still support the storedconfigs feature in Puppet 3.0, so these issues concern me. Fabrice mentioned that restarting the puppet master helped with this issue. Could you please bounce the puppet master and see if that helps resolve this issue? Could you also enable the --verbose --debug and --trace options on your Puppet master and paste any stack traces that show up in your logs or on the console. This will help me diagnose this issue further. Thanks, -Jeff -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
