On Sat, Feb 18, 2012 at 12:49 PM, Khoury Brazil <khoury.bra...@gmail.com> wrote: > Since that's out of the way, how can I control catalog expiration on > specific puppet agents? I'm getting these errors if a client has been > offline for a few days: > > Not using expired catalog for <hostname> from cache; expired at <date> > > Since these clients are laptops they can go for a week or two (and in > rare cases longer) without connecting back to the network that the > puppet master is on. > > Would altering catalog expiration affect online agents as well? > > Thanks again, > Khoury
Changing the date on the 'expiration' portion of the client's catalog yaml file resulted in puppet using the cached catalog. I've done some digging and can't seem to find any configuration parameters that control that. Some googling indicates that changing the runinterval might affect it, but I want to continue applying puppet every 30-60 minutes on my agents. I need offline clients to apply a catalog while offline, regardless of the age of the catalog, but I really want to avoid a kludged together solution. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
