From f2f92b39bc5084d1b67cec8c51bebc94c9190d84 Mon Sep 17 00:00:00 2001 From: Stephen Gran Date: Mon, 13 Apr 2009 13:58:15 +0100 Subject: [PATCH 1/1] Add monit module and deploy to aargento as a test for now Signed-off-by: Stephen Gran --- manifests/site.pp | 5 + modules/monit/files/debianorg | 2 + modules/monit/files/default | 11 ++ modules/monit/files/monitrc | 215 +++++++++++++++++++++++++++++++++ modules/monit/files/puppet | 7 ++ modules/monit/manifest/init.pp | 54 +++++++++ 6 files changed, 294 insertions(+) create mode 100644 modules/monit/files/debianorg create mode 100644 modules/monit/files/default create mode 100644 modules/monit/files/monitrc create mode 100644 modules/monit/files/puppet create mode 100644 modules/monit/manifest/init.pp diff --git a/manifests/site.pp b/manifests/site.pp index 2593be0ba..08e09561f 100644 --- a/manifests/site.pp +++ b/manifests/site.pp @@ -54,6 +54,11 @@ node default { { include geodns } default: {} } + case $hostname { + argento: + { include monit } + default: {} + } } diff --git a/modules/monit/files/debianorg b/modules/monit/files/debianorg new file mode 100644 index 000000000..97dada5c6 --- /dev/null +++ b/modules/monit/files/debianorg @@ -0,0 +1,2 @@ +set alert samhain-reports@debian.org +set mail-format { from: monit@debian.org } diff --git a/modules/monit/files/default b/modules/monit/files/default new file mode 100644 index 000000000..bf72a5a7d --- /dev/null +++ b/modules/monit/files/default @@ -0,0 +1,11 @@ +# Defaults for monit initscript +# sourced by /etc/init.d/monit +# installed at /etc/default/monit by maintainer scripts +# Fredrik Steen + +# You must set this variable to for monit to start +startup=1 + +# To change the intervals which monit should run uncomment +# and change this variable. +CHECK_INTERVALS=300 diff --git a/modules/monit/files/monitrc b/modules/monit/files/monitrc new file mode 100644 index 000000000..f0f97a5ba --- /dev/null +++ b/modules/monit/files/monitrc @@ -0,0 +1,215 @@ +############################################################################### +## Monit control file +############################################################################### +## +## Comments begin with a '#' and extend through the end of the line. Keywords +## are case insensitive. All path's MUST BE FULLY QUALIFIED, starting with '/'. +## +## Below you will find examples of some frequently used statements. For +## information about the control file, a complete list of statements and +## options please have a look in the monit manual. +## +## +############################################################################### +## Global section +############################################################################### +## +## Start monit in the background (run as a daemon) and check services at +## 2-minute intervals. +# +# set daemon 120 +# +# +## Set syslog logging with the 'daemon' facility. If the FACILITY option is +## omitted, monit will use 'user' facility by default. If you want to log to +## a stand alone log file instead, specify the path to a log file +# +# set logfile syslog facility log_daemon +# +# +## Set the list of mail servers for alert delivery. Multiple servers may be +## specified using comma separator. By default monit uses port 25 - this +## is possible to override with the PORT option. +# +# set mailserver mail.bar.baz, # primary mailserver +# backup.bar.baz port 10025, # backup mailserver on port 10025 +# localhost # fallback relay +# +# +## By default monit will drop alert events if no mail servers are available. +## If you want to keep the alerts for a later delivery retry, you can use the +## EVENTQUEUE statement. The base directory where undelivered alerts will be +## stored is specified by the BASEDIR option. You can limit the maximal queue +## size using the SLOTS option (if omitted, the queue is limited by space +## available in the back end filesystem). +# +# set eventqueue +# basedir /var/monit # set the base directory where events will be stored +# slots 100 # optionaly limit the queue size +# +# +## Monit by default uses the following alert mail format: +## +## --8<-- +## From: monit@$HOST # sender +## Subject: monit alert -- $EVENT $SERVICE # subject +## +## $EVENT Service $SERVICE # +## # +## Date: $DATE # +## Action: $ACTION # +## Host: $HOST # body +## Description: $DESCRIPTION # +## # +## Your faithful employee, # +## monit # +## --8<-- +## +## You can override this message format or parts of it, such as subject +## or sender using the MAIL-FORMAT statement. Macros such as $DATE, etc. +## are expanded at runtime. For example, to override the sender: +# +# set mail-format { from: monit@foo.bar } +# +# +## You can set alert recipients here whom will receive alerts if/when a +## service defined in this file has errors. Alerts may be restricted on +## events by using a filter as in the second example below. +# +# set alert sysadm@foo.bar # receive all alerts +# set alert manager@foo.bar only on { timeout } # receive just service- +# # timeout alert +# +# +## Monit has an embedded web server which can be used to view status of +## services monitored, the current configuration, actual services parameters +## and manage services from a web interface. +# +# set httpd port 2812 and +# use address localhost # only accept connection from localhost +# allow localhost # allow localhost to connect to the server and +# allow admin:monit # require user 'admin' with password 'monit' +# +# +############################################################################### +## Services +############################################################################### +## +## Check general system resources such as load average, cpu and memory +## usage. Each test specifies a resource, conditions and the action to be +## performed should a test fail. +# +# check system myhost.mydomain.tld +# if loadavg (1min) > 4 then alert +# if loadavg (5min) > 2 then alert +# if memory usage > 75% then alert +# if cpu usage (user) > 70% then alert +# if cpu usage (system) > 30% then alert +# if cpu usage (wait) > 20% then alert +# +# +## Check a file for existence, checksum, permissions, uid and gid. In addition +## to alert recipients in the global section, customized alert will be sent to +## additional recipients by specifying a local alert handler. The service may +## be grouped using the GROUP option. +# +# check file apache_bin with path /usr/local/apache/bin/httpd +# if failed checksum and +# expect the sum 8f7f419955cefa0b33a2ba316cba3659 then unmonitor +# if failed permission 755 then unmonitor +# if failed uid root then unmonitor +# if failed gid root then unmonitor +# alert security@foo.bar on { +# checksum, permission, uid, gid, unmonitor +# } with the mail-format { subject: Alarm! } +# group server +# +# +## Check that a process is running, in this case Apache, and that it respond +## to HTTP and HTTPS requests. Check its resource usage such as cpu and memory, +## and number of children. If the process is not running, monit will restart +## it by default. In case the service was restarted very often and the +## problem remains, it is possible to disable monitoring using the TIMEOUT +## statement. This service depends on another service (apache_bin) which +## is defined above. +# +# check process apache with pidfile /usr/local/apache/logs/httpd.pid +# start program = "/etc/init.d/httpd start" +# stop program = "/etc/init.d/httpd stop" +# if cpu > 60% for 2 cycles then alert +# if cpu > 80% for 5 cycles then restart +# if totalmem > 200.0 MB for 5 cycles then restart +# if children > 250 then restart +# if loadavg(5min) greater than 10 for 8 cycles then stop +# if failed host www.tildeslash.com port 80 protocol http +# and request "/monit/doc/next.php" +# then restart +# if failed port 443 type tcpssl protocol http +# with timeout 15 seconds +# then restart +# if 3 restarts within 5 cycles then timeout +# depends on apache_bin +# group server +# +# +## Check device permissions, uid, gid, space and inode usage. Other services, +## such as databases, may depend on this resource and an automatically graceful +## stop may be cascaded to them before the filesystem will become full and data +## lost. +# +# check device datafs with path /dev/sdb1 +# start program = "/bin/mount /data" +# stop program = "/bin/umount /data" +# if failed permission 660 then unmonitor +# if failed uid root then unmonitor +# if failed gid disk then unmonitor +# if space usage > 80% for 5 times within 15 cycles then alert +# if space usage > 99% then stop +# if inode usage > 30000 then alert +# if inode usage > 99% then stop +# group server +# +# +## Check a file's timestamp. In this example, we test if a file is older +## than 15 minutes and assume something is wrong if its not updated. Also, +## if the file size exceed a given limit, execute a script +# +# check file database with path /data/mydatabase.db +# if failed permission 700 then alert +# if failed uid data then alert +# if failed gid data then alert +# if timestamp > 15 minutes then alert +# if size > 100 MB then exec "/my/cleanup/script" +# +# +## Check directory permission, uid and gid. An event is triggered if the +## directory does not belong to the user with uid 0 and gid 0. In addition, +## the permissions have to match the octal description of 755 (see chmod(1)). +# +# check directory bin with path /bin +# if failed permission 755 then unmonitor +# if failed uid 0 then unmonitor +# if failed gid 0 then unmonitor +# +# +## Check a remote host network services availability using a ping test and +## check response content from a web server. Up to three pings are sent and +## connection to a port and a application level network check is performed. +# +# check host myserver with address 192.168.1.1 +# if failed icmp type echo count 3 with timeout 3 seconds then alert +# if failed port 3306 protocol mysql with timeout 15 seconds then alert +# if failed url +# http://user:password@www.foo.bar:8080/?querystring +# and content == 'action="j_security_check"' +# then alert +# +# +############################################################################### +## Includes +############################################################################### +## +## It is possible to include additional configuration parts from other files or +## directories. +# +include /etc/monit.d/* diff --git a/modules/monit/files/puppet b/modules/monit/files/puppet new file mode 100644 index 000000000..5d3e21c27 --- /dev/null +++ b/modules/monit/files/puppet @@ -0,0 +1,7 @@ +check process puppetd with pidfile /var/run/puppet/puppetd.pid + start program = "/etc/init.d/puppet start" + stop program = "/etc/init.d/puppet stop" + if cpu is greater than 80% for 3 cycles then alert + if cpu > 60% for 5 cycles then restart + if 5 restarts within 5 cycles then timeout + diff --git a/modules/monit/manifest/init.pp b/modules/monit/manifest/init.pp new file mode 100644 index 000000000..894be00ac --- /dev/null +++ b/modules/monit/manifest/init.pp @@ -0,0 +1,54 @@ +class clamav { + package { "monit": ensure => installed; + } + + file { + "/etc/monit/monitrc": + source => "puppet:///monit/monitrc", + require => Package["monit"], + notify => Exec["monit restart"] + mode => 440, + ; + } + + file { + "/etc/monit/monit.d": + ensure => directory, + owner => root, + group => root, + mode => 750, + purge => true + ; + } + + file { + "/etc/monit/monit.d/01puppet": + source => "puppet:///monit/puppet", + require => Package["monit"], + notify => Exec["monit restart"] + mode => 440, + ; + } + + file { + "/etc/monit/monit.d/00debian.org": + source => "puppet:///monit/debianorg", + require => Package["monit"], + notify => Exec["monit restart"] + mode => 440, + ; + } + + file { + "/etc/default/monit": + source => "puppet:///monit/default", + require => Package["monit"], + notify => Exec["monit restart"] + ; + } + exec { "monit restart": + path => "/etc/init.d:/usr/bin:/usr/sbin:/bin:/sbin", + refreshonly => true, + } +} + -- 2.20.1