Are you using stored configs? Could you also paste your puppet.conf with passwords redacted?
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. 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. Hope this helps, -Jeff On Mon, Oct 22, 2012 at 8:23 AM, Fabrice Bacchella <fbacche...@spamcop.net>wrote: > Here it is : > [2012-10-22 17:18:50] puppet-master[25373]: allocator undefined for Proc > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/yaml.rb:133:in `transfer' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/yaml.rb:133:in `node_import' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/yaml.rb:133:in `load' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/yaml.rb:133:in `load' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/util/rails/reference_serializer.rb:6:in > `unserialize_value' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/param_value.rb:64:in > `find_all_params_from_host' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/param_value.rb:63:in `each' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/param_value.rb:63:in > `find_all_params_from_host' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb:232:in > `find_resources_parameters' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb:119:in > `find_resources_parameters_tags' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb:101:in `merge_resources' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:23:in > `debug_benchmark' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:13:in `railsmark' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/core_ext/benchmark.rb:8:in > `realtime' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:13:in `railsmark' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:23:in > `debug_benchmark' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb:100:in `merge_resources' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/active_record.rb:25:in > `save' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:13:in `railsmark' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/core_ext/benchmark.rb:8:in > `realtime' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb:13:in `railsmark' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/active_record.rb:24:in > `save' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/indirector/store_configs.rb:24:in `save' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:195:in `find' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:108:in `do_find' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:71:in `send' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:71:in `process' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb:24:in > `service' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:33:in `listen' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:30:in `listen' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in > `initialize' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `new' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `listen' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:26:in > `synchronize' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:26:in `listen' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:92:in `listen' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:104:in `start' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:136:in `start' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:199:in `main' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:148:in > `run_command' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:438:in `plugin_hook' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:500:in `exit_on_fail' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' > [2012-10-22 17:18:50] puppet-master[25373]: > /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:87:in `execute' > [2012-10-22 17:18:50] puppet-master[25373]: /usr/bin/puppet:4 > > > > Le 18 oct. 2012 à 17:26, Jeff McCune a écrit : > > > Could you check the server logs and run the master with --verbose > > --debug --trace? > > > > The information I'm looking for is a backtrace to the file and ljne > > number that raised that exception. > > > > Thanks, > > -Jeff > > > > On Oct 18, 2012, at 5:26 AM, Fabrice Bacchella <fbacche...@spamcop.net> > wrote: > > > >> My puppet setup break just a few hours with this message. > >> > >> I didn't upgrade anything, didn't really changed my module and it just > broke. The node what where working suddenly stop working. > >> > >> I'm using the official Puppet 3.0 on Scientific Linux (aka Redhat) 6.3 > >> > >> Can some one explain me this magic ? > >> > >> -- > >> 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. > >> > > > > -- > > 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. > > > > -- > 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. > > -- 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.
0001-WIP-Instrument-store_configs-serialization-issue.patch
Description: Binary data
