Hi there, Just to report that I still see the same issue:
Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > allocator undefined for Proc > /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:185:in `is_http_200?' > /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:100:in `find' > /usr/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:197:in `find' > /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:243:in `block in > retrieve_new_catalog' > /usr/lib/ruby/vendor_ruby/puppet/util.rb:351:in `block in thinmark' > /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' > /usr/lib/ruby/vendor_ruby/puppet/util.rb:350:in `thinmark' > /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:242:in > `retrieve_new_catalog' > /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:67:in `retrieve_catalog' > /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:107:in > `prepare_and_retrieve_catalog' > /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:159:in `run' > /usr/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `block (5 levels) in run' > /usr/lib/ruby/vendor_ruby/puppet/agent/locker.rb:20:in `lock' > /usr/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `block (4 levels) in run' > /usr/lib/ruby/1.9.1/sync.rb:227:in `sync_synchronize' > /usr/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/puppet/agent.rb:119:in `with_client' > /usr/lib/ruby/vendor_ruby/puppet/agent.rb:42:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/puppet/agent.rb:84:in `run_in_fork' > /usr/lib/ruby/vendor_ruby/puppet/agent.rb:41:in `block in run' > /usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `call' > /usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `controlled_run' > /usr/lib/ruby/vendor_ruby/puppet/agent.rb:39:in `run' > /usr/lib/ruby/vendor_ruby/puppet/application/agent.rb:353:in `onetime' > /usr/lib/ruby/vendor_ruby/puppet/application/agent.rb:327:in `run_command' > /usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `block (2 levels) > in run' > /usr/lib/ruby/vendor_ruby/puppet/application.rb:456:in `plugin_hook' > /usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `block in run' > /usr/lib/ruby/vendor_ruby/puppet/util.rb:504:in `exit_on_fail' > /usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `run' > /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' > /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:86:in `execute' > /usr/bin/puppet:4:in `<main>' > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run > Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson > System info, as requested: root@ip-10-0-3-82:/etc/puppet/modules# lsb_release -irc > Distributor ID: Debian > Release: 6.0.7 > Codename: squeeze > # > root@ip-10-0-3-82:/etc/puppet/modules# ruby -v > ruby 1.8.7 (2010-08-16 patchlevel 302) [x86_64-linux] > # > root@ip-10-0-3-82:/etc/puppet/modules# puppet -V > 3.1.1 > Only workaround, for me, so far is to delete the node from the puppet database. Cheers!! On Thursday, November 29, 2012 2:34:50 PM UTC, John Lamb wrote: > > OS: Red Hat Enterprise Linux Server release 6.3 (Santiago) > Ruby: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] > Puppet: puppet-3.0.1-1.el6.noarch > > I can get the facter output to you later today. > > For what it's worth, I ran into this problem as I was developing a class > within an already-existing service. I referenced one or several resources > that didn't actually exist (via the require metaparameter - I tried to > require Group['git'],) and after fixing this issue I was no longer able to > get my puppet agent runs to work, even after commenting out all the changes > I had made. > > I was able to "fix" this by trying "puppet node clean broken.node.name", > which failed, then I tested puppet node clean against a working node, which > also failed, then on a whim I tried it against the broken node once more, > at which point it worked. Since then puppet has worked as usual. > > The error I got from puppet node clean is: > Error: uninitialized constant ActiveRecord::Base > Error: Try 'puppet help node clean' for usage > > Interestingly, this morning our puppet deprecation report told us: "11 > ActiveRecord-based storeconfigs and inventory are deprecated." We normally > don't have any deprecated storeconfigs. We have a total of 25 machines. I > don't know if this is related to the issue at large. > > On Wednesday, November 28, 2012 8:09:38 PM UTC-5, Jeff McCune wrote: >> >> On Wed, Nov 28, 2012 at 10:55 AM, John Lamb <[email protected]> wrote: >> > 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: >> >> OK, there's definitely a bug somewhere... >> >> I'm going to work on reproducing this issue tomorrow. Before then, >> could anyone affected by this "allocator undefined for Proc" error >> please let me know what exact versions of the operating system, Ruby, >> and Puppet they're running? >> >> If possible, if you could just privately email me the output of facter >> from an affected Puppet master that would be greatly helpful in >> reproducing this issue. >> >> Finally, could you please send me (privately) a copy and paste of all >> exported resources in your manifests? You can probably find them >> easiest with a recursive grep against "@@". This will help me >> populate the storedconfigs database so I can reproduce this issue. >> >> Thanks, >> -Jeff >> > On Thursday, November 29, 2012 1:09:38 AM UTC, Jeff McCune wrote: > > On Wed, Nov 28, 2012 at 10:55 AM, John Lamb <[email protected] <javascript:>> > wrote: > > 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: > > OK, there's definitely a bug somewhere... > > I'm going to work on reproducing this issue tomorrow. Before then, > could anyone affected by this "allocator undefined for Proc" error > please let me know what exact versions of the operating system, Ruby, > and Puppet they're running? > > If possible, if you could just privately email me the output of facter > from an affected Puppet master that would be greatly helpful in > reproducing this issue. > > Finally, could you please send me (privately) a copy and paste of all > exported resources in your manifests? You can probably find them > easiest with a recursive grep against "@@". This will help me > populate the storedconfigs database so I can reproduce this issue. > > Thanks, > -Jeff > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
