I am also seeing this bug on one of my nodes (worryingly, the puppet master itself!) The relevant output of puppet agent -t --debug --trace --verbose matches what Fabrice and Lee have also reported:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:65:in `deserialize' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:121:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:191:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:243:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:348:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:347:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:242:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:67:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:107:in `prepare_and_retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:159:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:119:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:42:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:84:in `run_in_fork' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:175:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:175:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:339:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:312:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:438:in `plugin_hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:500:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:87:in `execute' /usr/bin/puppet:4 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I am also using a MySQL DB as my storeconfig. On Tuesday, November 27, 2012 1:45:15 PM UTC-5, Jeff McCune wrote: > > On Tue, Nov 27, 2012 at 9:06 AM, Lee Boynton <l...@lboynton.com<javascript:>> > 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/_g4_Ggww240J. 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.
