Ricky Zhou wrote:
> +1, use sudo /usr/sbin/puppetd --disable to disable puppet there.
> Don't forget to reenable it later though.
Where I work we have nagios monitoring puppet (via the state.yaml
files, which Seth mentioned in IRC I see). And as part of that check,
we read the contents /var/lib/puppet/state/puppetdlock, if there are
any, and display them in nagios.
When an admin needs to temporarily disable puppet, they use (a
slightly overengineered) script that drops the reason and their uid
into the lock file. The nagios check then knows it's disabled
intentionally and only warns rather than going critical if puppet
hasn't run in over X hours. It also displays nicely in the web
interface e.g.:
WARN: Puppet is disabled: Testing hosted2 changes (codeblock)
This has been very handy for the various admins to keep track of not
only when puppet is disabled but who did it and why.
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Careful. We don't want to learn from this.
-- Calvin
Attachment:
pgpMzZWZ3Zl48.pgp
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
