[Puppet Users] Re: Error: can''t instantiate uninitialized class

jcbollinger
Thu, 06 Dec 2012 14:22:04 -0000

On Thursday, December 6, 2012 5:14:51 AM UTC-6, Luca Gioppo
wrote:
>
> OK I''m getting mad.
>
> All of a sudden after a few mods I received this error from the
> puppet_master.
>
> I reverted all the changes done up to a last working set but no prize
> still this error and I cannot understand what is happening it seems that it
> manages to finish the catalog but than it stops.
>
> Here is a chunk of the output any idea on ohw to raise the level of debug
> and getting something more useful?
> Puppet version 3.0.0
> Thanks
> Luca
>
> Compiled catalog for jbossm.cortile.cloudlabcsi.local in environment
> production in 1.53 seconds
> Info: Caching catalog for jbossm.cortile.cloudlabcsi.local
> Debug: Searched for resources in 0.01 seconds
> Error: can''t instantiate uninitialized class
> Debug: Finishing transaction 69873076055740
>


That error message is being emitted by the agent, not the master.  Run the
agent with the --debug flag to get the most detailed information available,
but it looks like you may already be doing that.

That doesn''t look like a Puppet error message, however.  Puppet
doesn''t
have a sense of "initializing" classes, nor really of
"instantiating"
them.  The latter, especially, is an OO concept, and Puppet''s
"classes" are
not classes in the OO sense.

I would guess, therefore, that the error is being emitted at a lower level
of the software stack, probably in Ruby itself.  If it''s there then it
could arise from a Puppet bug, a Ruby bug, or an incompatibility between
Puppet and your Ruby implementation.  Which Ruby is that, by the way?


John

--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit