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 <lam...@wfu.edu <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 view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Pcexq3Ked8UJ.
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.

Reply via email to