check_puppet - plugin to check Puppet daemon availability
[1mSYNOPSIS[0m
[1mcheck_puppet [22m[[4m-h[24m [4m|[24m [4m-v[24m] [[4mOPTIONS[24m]
[1mDESCRIPTION[0m
check_puppet observes for Puppet daemon activity by checking the pid
file against the process running on the system for both Puppet master
daemon and Puppet client. In the client mode local configuration
freshness is also being checked.
[1mOPTIONS[0m
[1m-h [22mPrint this help and then exit immediately.
[1m-v [22mPrint version and exit.
[1m-c [22mEnable puppet client checking mode. (default)
[1m-C [22mDo not check puppetd.
[1m-m [22mEnable puppet master daemon checking mode.
[1m-M [22mDo not check puppet master daemon. (default)
[1m-p [22mpath-to-pid
Running puppet client pid file. You should ensure that user run‐
ning this plugin have sufficient permissions to access this
file. Default is /var/run/puppet/agent.pid
[1m-P [22mpath-to-pid
Puppet master daemon pid file. Default pid file path is
/var/run/puppet/master.pid
[1m-s [22mpath-to-yaml
Puppet client local configuration YAML. By default puppet stores
it's state in /var/puppet/state/state.yaml
[1m-e [22mConfiguration expiration warning delay.
[1m-E [22mConfiguration expiration critical delay.
[1mENVIRONMENT[0m
Although it is possible to set almost all options with command line
arguments there are some environment variables can be set to change
some script parameters. Note that command line options have higher pri‐
ority before environment variables.
[1mPUPPETD_PIDFILE [22mand [1mPUPPET_MASTERD_PIDFILE [22menvironment variables speci‐
fies your Puppet installation pid files for client and master pro‐
cesses.
[1mPUPPETD_STATE [22mvariable allow to alternate the path to local client YAML
configuration from the default value.
status.
[1mEXAMPLES[0m
You can use SNMP plugin from [4mnet-mgmt/nagios-plugins[24m FreeBSD port to
monitor Puppet daemon activity on remote host.
First, you need to setup a working installation of SNMP-client on the
host. For the details consult the offical Net-SNMP project site at
http://net-snmp.sourceforge.net/
Configure yet another probe in [1msnmpd.conf[22m(5) to execute [1mcheck_puppet[0m
agent with any available command line options:
exec check_puppet /usr/local/bin/check_puppet
restart [1msnmpd [22mdaemon, then query SNMP-client:
$ snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.8
You should see the output from [1msnmpd [22mdaemon showing the result of
[1mcheck_puppet [22magent execution both the output status string and exit
code.
Now configure Nagios service check command. Be sure you have working
[1mcheck_snmp [22mcommand definition in your Nagios configuration. You need to
pass [4mboth[24m OIDs to [1mcheck_snmp [22mcommand with [1m-o [22moption - one OID for
string and another OID for exit status code in order to get correct
status information and status code retrieving by Nagios poller. Spec‐
ify warning and critical ranges with [1m-w [22mand [1m-c [22moptions as `,0' and `,1'
values accordingly. Check in more options for [1mcheck_snmp [22mcommand by
typing
$ /usr/local/libexec/nagios/check_snmp -h
Consult any questions about Nagion configuration at
http://www.nagios.org/docs/
[1mAVAILABILITY[0m
The latest version of this distribution is available on-line from:
http://www.renatasystems.org/freebsd/check_puppet.html
[1mAUTHOR[0m
Written by Alexey V. Degtyarev
[1mREPORTING BUGS[0m
Report bugs to <alexey@renatasystems.org>
[1mSEE ALSO[0m
[1msnmpd.conf[22m(5) [1msnmpd[22m(8)
Man(1) output converted with man2html