Le 24 oct. 2012 à 17:49, Jeff McCune <j...@puppetlabs.com> a écrit :
> Are you using stored configs? Could you also paste your puppet.conf with > passwords redacted? Yes I'm using stored config. > > It looks like the YAML library itself is raising the exception. Could you > apply this small patch to one of your puppet masters, then email me the > /tmp/for_jeff.json file? This will help me understand what value might be > causing the exception in the YAML library. > > Also, a viable work-around might be to switch from stored configs to PuppetDB. No it's not. We're using mysql for our database and have no competences in postgress, so installing PuppetDB needs time, reflexion and testing. It might be an intersting solution, but certainly not a work-around for a bug. > > You should be able to apply this patch using: > > cd /usr/lib/ruby/site_ruby/1.8 > patch -p2 < /tmp/0001-WIP-Instrument-store_configs-serialization-issue.patch > > Then you'd need to restart your puppet master and look for /tmp/for_jeff.json > file to be created. This patch does something magic. A broken node (with allocator undefined for Proc) is working when I apply your patch to the puppet master and restart it. I can then remove it and the node will keep working. All of this with up to date puppet in both node and master. Anyway, I'll send you the requested files in a private mail. -- 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.
