On Sep 8, 2011, at 8:52 AM, Craig White wrote:
> Silly me disabled caching on catalogs throughout my testing and now that
I''m in production mode, I have had some issues with my
puppetmaster/foreman ENC server VM sometimes getting into swap and the dreadful
performance has caused some failures because the catalog could not be compiled.
>
> While I have to solve the underlying problem (and I think I''m
getting there), I think it would be useful to have the clients cache the catalog
for those times that it can''t get a compiled catalog from the
puppetmaster.
>
> the clients have this in puppet.conf [agent] section:
> ignorecache = false
> use_cached_catalog = false
>
> the puppetmaster doesn''t have any specific settings but when I run
''puppet master --genconf'', I can see...
>
> localconfig = /var/lib/puppet/state/localconfig
>
> but there is no cached catalog in any of the clients.
>
> What am I missing?
----
perhaps I wasn''t clear. I''m looking for a way to implement
using a cached_catalog if the catalog can''t be retrieved to prevent
these...
(from Foreman e-mail so the appearance may be unusual but the message is a
puppet message)
Puppet Output
Level Resource message
err Puppet Could not retrieve catalog from remote server: execution expired
notice Puppet Using cached catalog
err Puppet Could not retrieve catalog; skipping run
As far as I can tell, no catalog is ever cached on the puppet master or any
puppet clients and if my VM server is in a temporary swap funk, it sends an
e-mail like the above. It seems it would be useful in those instances to just
use a cached catalog as opposed to a failure.
Possible?
Craig
--
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.