FWIW, I use /var/lib/puppet/state/state.yaml for monitoring wether the agent is working successfully, and from experience, it will reflect even the case of "works but uses cached catalogs" as a problem.
HTH, Felix On 06/03/2014 09:27 PM, Steve Kilduff wrote: > Hi, Yes you got it. With puppet agent -t it seems no cached catalog is > applied, and it seems that the way in which I purposefully "broke > puppet" by removing a manifest on the puppet master causes puppet agent > to use a cached catalogue which is the default behavior. I > set usecacheonfailure = false in puppet.conf, and now it fails as > expected on the agent runs, and the monitor also catches it. This is > pretty interesting. If I broke puppet, and it continues to successfully > run with cached catalog everything looks fine although isn't. Or I > disable cached catalog, and have maybe heavier load on the server. Maybe > I just need change the monitor tests I am doing. > > Will think about this for a bit longer :) > > Thanks for the help! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/538F0836.2080103%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
