Basically the ways I know of: 1) Don't run puppet as a daemon, but run it out of cron every X mins. 2) Setup a cronjob that checks if puppet is running and restart it if not. 3) Setup a nagios job that checks to see if puppet is running 4) Presuming you are managing your puppet code in some sort of version control system, you can "publish" the latest timestamp of your latest commit, and also push that out via puppet, and setup a nagios check that compares them and if they ever are behind by more than X mins you can crit on it. You could take this a step further and have nagios automatically restart puppet if they are behind, but if you think it might be a syntax error, I would probably skip that. (As an aside you should do syntax checking before committing. I added the commands to do so below) 5) Foreman (or dashboard) can monitor puppet runs, and flag any broken runs.
Check syntax: puppet --noop --parseonly memcached.pp Check erb syntax: erb -x -T '-' memcached-sessions.erb |ruby -c We use a combination of 2,3,4 and 5. Cheers, Brian On Wed, May 25, 2011 at 1:12 PM, Douglas Garstang <doug.garst...@gmail.com> wrote: > I probably waste quite a bit of time each week restarting the puppet client, > and logging systems, and tailing the messages file, to see if my puppet > changes worked. Is there a better way? How do people normally do this? > Sure, I can use puppetrun or mcollective to cause puppet to do a config run > on the client, but I still need to log in and look at the messages file. The > reports that the clients generate, and which are available on the server > contain, I believe yield enough information to determine if there was any > syntax errors or not. I guess they contain more, but, even though they are > yaml files, they contain ruby objects, which non ruby parsers won't read. > Would have been nice if it was standard yaml. > Anyway.... ideas? > Doug. > > -- > 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. > -- 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.
