Puppet users - Sep 2007 - "warning: Could not get config; using cached copy" error with latest puppet release

I''m receiving a "warning: Could not get config; using cached
copy" when
running "puppetd --test" with the latest puppet and puppet-server RPMs
from dlutter''s site.

Has anyone else seen this problem or can give me an idea of where to
start looking for the problem?

James

*********************************************************************************
Important Note
This email (including any attachments) contains information which is 
confidential and may be subject to legal privilege.  If you are not 
the intended recipient you must not use, distribute or copy this 
email.  If you have received this email in error please notify the 
sender immediately and delete this email. Any views expressed in this 
email are not necessarily the views of AXA-Tech Australia.   Thank you.
**********************************************************************************

> I''m receiving a "warning: Could not get config; using cached
copy"
when
> running "puppetd --test" with the latest puppet and puppet-server
RPMs
> from dlutter''s site.
> 
> Has anyone else seen this problem or can give me an idea of where to
> start looking for the problem?
Just to add, other than failing to read any new configuration, the
puppetd run works as expected.  i.e. If any files managed by the
original configuration have changed, they will be updated, but any
changes to my sites.pp are ignored.

James


*********************************************************************************
Important Note
This email (including any attachments) contains information which is 
confidential and may be subject to legal privilege.  If you are not 
the intended recipient you must not use, distribute or copy this 
email.  If you have received this email in error please notify the 
sender immediately and delete this email. Any views expressed in this 
email are not necessarily the views of AXA-Tech Australia.   Thank you.
**********************************************************************************

On Sep 26, 2007, at 12:54 AM, HARRIS Jimmy ((AXA-Tech-AU)) wrote:
> I''m receiving a "warning: Could not get config; using cached
copy"
> when
> running "puppetd --test" with the latest puppet and puppet-server
RPMs
> from dlutter''s site.
>
> Has anyone else seen this problem or can give me an idea of where to
> start looking for the problem?
You should get an additional error explaining what the problem is,  
although I suppose there''s a chance the error might only be on the  
server (shouldn''t be, but who knows?).

  --
  This space intentionally has nothing but text explaining why this  
space
  has nothing but text explaining that this space would otherwise have
  been left blank, and would otherwise have been left blank.
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

> > I''m receiving a "warning: Could not get config; using
cached copy"
when
> > running "puppetd --test" with the latest puppet and
puppet-server
RPMs
> > from dlutter''s site.
> >
> > Has anyone else seen this problem or can give me an idea of where to
> > start looking for the problem?
> 
> You should get an additional error explaining what the problem is,
> although I suppose there''s a chance the error might only be on the
> server (shouldn''t be, but who knows?).
There was no additional error but I ran "puppetmasterd --debug" and
found out that it was failing to parse one of my classes due to a typo I
had made.  It was only coincidence (perhaps due to the restart of
puppetmasterd) that it happened at the same time as the puppet and
puppet-server upgrades.

James

*********************************************************************************
Important Note
This email (including any attachments) contains information which is 
confidential and may be subject to legal privilege.  If you are not 
the intended recipient you must not use, distribute or copy this 
email.  If you have received this email in error please notify the 
sender immediately and delete this email. Any views expressed in this 
email are not necessarily the views of AXA-Tech Australia.   Thank you.
**********************************************************************************