----- Original Message -----
> 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.
6) use the last run summary
# cat /var/lib/puppet/state/last_run_summary.yaml
---
time:
group: 0.000852
last_run: 1306343446
class: 0.002389
yumrepo: 0.037513
service: 2.300486
schedule: 0.002291
cron: 0.001797
config_retrieval: 18.9993901252747
total: 37.9802451252747
package: 0.371819
filebucket: 0.00032
file: 15.664177
exec: 0.593368
user: 0.005843
resources:
total: 384
events:
total: 0
changes:
--
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.
