Puppet users - Oct 2007 - error message: undefined method `parentof?''

Hi Puppet users, I occasionally see this error message in my logfiles,
and was wondering what it could possibly mean.  I found no mention
of it in the wiki or list archives, and so I turn to you.

Could not run Puppet::Network::Client::Master: undefined method
`parentof?'' for nil:NilClass

It appears in the log files at the end of a configuration run, like this:

Oct 17 20:13:30 domU-12-31-33-00-03-66 puppetd[2022]: Finished configuration run
in 84.61 seconds
Oct 17 20:13:30 domU-12-31-33-00-03-66 puppetd[2022]: Could not run
Puppet::Network::Client::Master: undefined method `parentof?'' for
nil:NilClass
Oct 17 20:14:03 domU-12-31-33-00-03-66 puppetd[2022]: Starting configuration run

During testing I am running the configuration every 30 seconds, and on two
occasions that I''ve observed this recently it was in a configuration
run that
took longer than that.  However, this may be coincidence, because a long
configuration run is not sufficient to create the message.

Any ideas about what this means?  If it might be a problem in my configuration,
any suggestions about what to look for?

Thanks, Alex

On Oct 18, 2007, at 6:56 PM, Alexander Taler wrote:
> Hi Puppet users, I occasionally see this error message in my logfiles,
> and was wondering what it could possibly mean.  I found no mention
> of it in the wiki or list archives, and so I turn to you.
>
> Could not run Puppet::Network::Client::Master: undefined method  
> `parentof?'' for nil:NilClass
>
> It appears in the log files at the end of a configuration run, like  
> this:
>
> Oct 17 20:13:30 domU-12-31-33-00-03-66 puppetd[2022]: Finished  
> configuration run in 84.61 seconds
> Oct 17 20:13:30 domU-12-31-33-00-03-66 puppetd[2022]: Could not run  
> Puppet::Network::Client::Master: undefined method `parentof?'' for
> nil:NilClass
> Oct 17 20:14:03 domU-12-31-33-00-03-66 puppetd[2022]: Starting  
> configuration run
>
> During testing I am running the configuration every 30 seconds, and  
> on two
> occasions that I''ve observed this recently it was in a  
> configuration run that
> took longer than that.  However, this may be coincidence, because a  
> long
> configuration run is not sufficient to create the message.
>
> Any ideas about what this means?  If it might be a problem in my  
> configuration,
> any suggestions about what to look for?
It''s an internal error.  It shouldn''t ever happen in real
life, but
it''s not something Puppet can recover from.  It usually has to do  
with objects being persistent when they shouldn''t be.

I''ve redesigned the system to avoid that entirely, but it''s
not
released yet.

If you''re actually running every 30 seconds... Um, I would expect  
you''d get errors saying it''ll refuse to run, for runs longer
than 30
seconds.

  --
  A great many people think they are thinking when they are merely
  rearranging their prejudices.  -- William James
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

On Thu, Oct 18, 2007 at 08:12:07PM -0500, Luke Kanies
wrote:
> On Oct 18, 2007, at 6:56 PM, Alexander Taler wrote:
> 
> >Hi Puppet users, I occasionally see this error message in my logfiles,
> >and was wondering what it could possibly mean.  I found no mention
> >of it in the wiki or list archives, and so I turn to you.
> >
> >Could not run Puppet::Network::Client::Master: undefined method  
> >`parentof?'' for nil:NilClass
> >
> >Any ideas about what this means?  If it might be a problem in my  
> >configuration, any suggestions about what to look for?
> 
> It''s an internal error.  It shouldn''t ever happen in real
life, but
> it''s not something Puppet can recover from.  It usually has to do
> with objects being persistent when they shouldn''t be.
So if I understand correctly, Puppet will exit when it encounters
that problem, but it''s not something to worry about?

Thanks, Alex

On Oct 19, 2007, at 2:56 AM, Alexander Taler wrote:
> So if I understand correctly, Puppet will exit when it encounters
> that problem, but it''s not something to worry about?
Hmm, it shouldn''t actually exit, I don''t think; at worst, it
might
fail to run that time.  That is, puppetd shouldn''t exit; puppet might.

  --
  Seize opportunity by the beard, for it is bald behind.  --  
Bulgarian Proverb
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

On Fri, Oct 19, 2007 at 01:14:44PM -0500, Luke Kanies
wrote:
> On Oct 19, 2007, at 2:56 AM, Alexander Taler wrote:
> 
> > So if I understand correctly, Puppet will exit when it encounters
> > that problem, but it''s not something to worry about?
> 
> Hmm, it shouldn''t actually exit, I don''t think; at worst,
it might
> fail to run that time.  That is, puppetd shouldn''t exit; puppet
might.
Ah yes, of course.  Thanks for the info Luke.

Alex