Puppet users - Sep 2009 - How long does the server's node cache stick around?

In my testing, puppet has never caught on to a new config or recipe to
distribute unless I manually delete the node entry from the yaml/nodes
directory.  I couldn''t find any documentation on how to clear the
cache properly (I stumbled on that method) and I couldn''t find any
documentation on how long the cache is kept before it recompiles.  All
I saw were references to "stale timestamps" but no real details. 
I''ve
waited as long as two days and it just doesn''t see the change.

If one day I decide I need to deploy a new required Gnome key to all
of my Linux desktops, what''s the poper method of making sure that the
server realizes all the nodes need to be recompiled?

I''m using LDAP for storing my node entries, if this makes a
difference.  All of my LDAP servers are doing live replication.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

I don''t know the answer to how long the cache hangs around or how to
modify
how long it will use the cache but I know that if you run puppet with the
--test option it forces puppet to ignore the cache which is a lot less
annoying then editing the yaml file.  I suppose in the puppet.conf for your
clients you could put ignorecache = true and it will always compile the
manifest for you.
Chris

On Sun, Sep 27, 2009 at 12:50 PM, Tony Maro <tonymaro@gmail.com> wrote:
>
> In my testing, puppet has never caught on to a new config or recipe to
> distribute unless I manually delete the node entry from the yaml/nodes
> directory.  I couldn''t find any documentation on how to clear the
> cache properly (I stumbled on that method) and I couldn''t find any
> documentation on how long the cache is kept before it recompiles.  All
> I saw were references to "stale timestamps" but no real details. 
I''ve
> waited as long as two days and it just doesn''t see the change.
>
> If one day I decide I need to deploy a new required Gnome key to all
> of my Linux desktops, what''s the poper method of making sure that
the
> server realizes all the nodes need to be recompiled?
>
> I''m using LDAP for storing my node entries, if this makes a
> difference.  All of my LDAP servers are doing live replication.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

I tried the ignorecache=true on the clients to no avail... the server
would still send the cached node entry.  I could watch the output and
it even reported "using cached node blah blah" instead of
"Compiling
node blah blah".

I''m beginning to wonder if it''s an LDAP issue... From what I
gather of
old user list postings, the server should detect config file changes
and automatically recompile.

On Sep 28, 12:56 am, Chris Blumentritt <cblum...@gmail.com>
wrote:
> I don''t know the answer to how long the cache hangs around or how
to modify
> how long it will use the cache but I know that if you run puppet with the
> --test option it forces puppet to ignore the cache which is a lot less
> annoying then editing the yaml file.  I suppose in the puppet.conf for your
> clients you could put ignorecache = true and it will always compile the
> manifest for you.
> Chris
>
> On Sun, Sep 27, 2009 at 12:50 PM, Tony Maro <tonym...@gmail.com>
wrote:
>
> > In my testing, puppet has never caught on to a new config or recipe to
> > distribute unless I manually delete the node entry from the yaml/nodes
> > directory.  I couldn''t find any documentation on how to clear
the
> > cache properly (I stumbled on that method) and I couldn''t
find any
> > documentation on how long the cache is kept before it recompiles.  All
> > I saw were references to "stale timestamps" but no real
details.  I''ve
> > waited as long as two days and it just doesn''t see the
change.
>
> > If one day I decide I need to deploy a new required Gnome key to all
> > of my Linux desktops, what''s the poper method of making sure
that the
> > server realizes all the nodes need to be recompiled?
>
> > I''m using LDAP for storing my node entries, if this makes a
> > difference.  All of my LDAP servers are doing live replication.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Mon, Sep 28, 2009 at 7:14 AM, Tony Maro <tonymaro@gmail.com>
wrote:
>
> I tried the ignorecache=true on the clients to no avail... the server
> would still send the cached node entry.  I could watch the output and
> it even reported "using cached node blah blah" instead of
"Compiling
> node blah blah".
>
> I''m beginning to wonder if it''s an LDAP issue... From
what I gather of
> old user list postings, the server should detect config file changes
> and automatically recompile.
ignorecache should only apply to the client-side cache, not the server.

I don''t use LDAP nodes, and I never have this issue btw.
>
> On Sep 28, 12:56 am, Chris Blumentritt <cblum...@gmail.com> wrote:
>> I don''t know the answer to how long the cache hangs around or
how to modify
>> how long it will use the cache but I know that if you run puppet with
the
>> --test option it forces puppet to ignore the cache which is a lot less
>> annoying then editing the yaml file.  I suppose in the puppet.conf for
your
>> clients you could put ignorecache = true and it will always compile the
>> manifest for you.
>> Chris
>>
>> On Sun, Sep 27, 2009 at 12:50 PM, Tony Maro <tonym...@gmail.com>
wrote:
>>
>> > In my testing, puppet has never caught on to a new config or
recipe to
>> > distribute unless I manually delete the node entry from the
yaml/nodes
>> > directory.  I couldn''t find any documentation on how to
clear the
>> > cache properly (I stumbled on that method) and I couldn''t
find any
>> > documentation on how long the cache is kept before it recompiles.
 All
>> > I saw were references to "stale timestamps" but no real
details.  I''ve
>> > waited as long as two days and it just doesn''t see the
change.
>>
>> > If one day I decide I need to deploy a new required Gnome key to
all
>> > of my Linux desktops, what''s the poper method of making
sure that the
>> > server realizes all the nodes need to be recompiled?
>>
>> > I''m using LDAP for storing my node entries, if this makes
a
>> > difference.  All of my LDAP servers are doing live replication.
> >
>


-- 
nigel

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

I do have this issue.  Any time I add a new node, I have to restart
the puppet master.

On Mon, Sep 28, 2009 at 10:21 AM, Nigel Kersten <nigelk@google.com>
wrote:
>
> On Mon, Sep 28, 2009 at 7:14 AM, Tony Maro <tonymaro@gmail.com>
wrote:
>>
>> I tried the ignorecache=true on the clients to no avail... the server
>> would still send the cached node entry.  I could watch the output and
>> it even reported "using cached node blah blah" instead of
"Compiling
>> node blah blah".
>>
>> I''m beginning to wonder if it''s an LDAP issue... From
what I gather of
>> old user list postings, the server should detect config file changes
>> and automatically recompile.
>
> ignorecache should only apply to the client-side cache, not the server.
>
> I don''t use LDAP nodes, and I never have this issue btw.
>
>>
>> On Sep 28, 12:56 am, Chris Blumentritt <cblum...@gmail.com>
wrote:
>>> I don''t know the answer to how long the cache hangs around
or how to modify
>>> how long it will use the cache but I know that if you run puppet
with the
>>> --test option it forces puppet to ignore the cache which is a lot
less
>>> annoying then editing the yaml file.  I suppose in the puppet.conf
for your
>>> clients you could put ignorecache = true and it will always compile
the
>>> manifest for you.
>>> Chris
>>>
>>> On Sun, Sep 27, 2009 at 12:50 PM, Tony Maro
<tonym...@gmail.com> wrote:
>>>
>>> > In my testing, puppet has never caught on to a new config or
recipe to
>>> > distribute unless I manually delete the node entry from the
yaml/nodes
>>> > directory.  I couldn''t find any documentation on how
to clear the
>>> > cache properly (I stumbled on that method) and I
couldn''t find any
>>> > documentation on how long the cache is kept before it
recompiles.  All
>>> > I saw were references to "stale timestamps" but no
real details.  I''ve
>>> > waited as long as two days and it just doesn''t see
the change.
>>>
>>> > If one day I decide I need to deploy a new required Gnome key
to all
>>> > of my Linux desktops, what''s the poper method of
making sure that the
>>> > server realizes all the nodes need to be recompiled?
>>>
>>> > I''m using LDAP for storing my node entries, if this
makes a
>>> > difference.  All of my LDAP servers are doing live
replication.
>> >
>>
>
>
>
> --
> nigel
>
> >
>


-- 
Chad M. Huneycutt

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---