Monitor Debian servers with monit
Posted by hardik on Mon 10 Oct 2005 at 12:01
Monit is a system monitoring utility which allows an admin to easily monitor files, processes, directories, or devices on your Debian system. It can also be used for automatic maintenance/repairs - by executing particular commands when errors arise. To ease administration monit provide a web based monitoring interface, with SSL support.
To install monit in to your Debian server, Simply use apt-get:
#apt-get install monit
Once installed you'll find the main configuration file located at /etc/monit/monitrc.
Below is my sample configuration file, which will also explain some keywords.
set daemon 120 # poll at 2-minute intervals. Monit will wakeup every two minute to # monitor things. Time must be given in seconds.
set logfile syslog facility log_daemon # Set syslog logging.
# Set a default mail from-address for all alert messages emitted by monit.
# All alert mail will be sent to below mail address.
set mail-format { from: hardik@test.com }
set alert root@test.com
# You can define your mail-notification format. Do man monit
mail-format {
from: hardik@test.com
subject: $SERVICE $EVENT at $DATE
message: Monit $ACTION $SERVICE at $DATE on $HOST,
Yours sincerely,
Hardik Dalwadi.
}
# Make monit start its web-server. So you can acccess it from webrowser.
set httpd port 2812 and
use address test.com
##Monit web-server ACL.
allow localhost # allow localhost to connect to the server and
allow 192.168.1.2 # allow 192.168.1.2 to connect to the server,
# You can give only one per entry
allow admin:monit # user name and password for authentication.
allow hardik:hardik # set multiple user to access through browser.
# Monitoring the apache2 web services. # It will check process apache2 with given pid file. # If process name or pidfile path is wrong then monit will # give the error of failed. tough apache2 is running. check process apache2 with pidfile /var/run/apache2.pid #Below is actions taken by monit when service got stuck. start program = "/etc/init.d/apache2 start" stop program = "/etc/init.d/apache2 stop" # Admin will notify by mail if below of the condition satisfied. if cpu is greater than 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 3 restarts within 5 cycles then timeout group server
#Monitoring slapd process.
check process slapd with pidfile /var/ldap/var/run/slapd.pid
start program = "/etc/init.d/slapd start"
stop program = "/etc/init.d/slapd stop"
if failed port 389 then restart
if 2 restarts within 3 cycles then timeout
group server
# monit will only monit/give alert in this mode.
mode passive
# Check Database file, size,permission etc...
check file slapd-database with path /var/ldap/var/openldap-data/mydata.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 alert
#Check directory for permission.
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 host for which services up/down on particular port.
check host test.com with address 192.168.1.9
if failed icmp type echo with timeout 4 seconds then alert
if failed port 21 then alert
if failed port 22 type tcp 22 with timeout 40 seconds then aler
if failed port 80 protocol http then alert
if failed port 389 type tcp with timeout 15 seconds then alert
You can also include other configuration files via include directives:
include /etc/monit/default.monitrc include /etc/monit/mysql.monitrc
After modifying the configuration file you should check for the syntax to make sure they are correct. To do this run:
# monit -t
Now you can run monit directly:
# monit
Once monit is running you can check for activity with your web-browser.
You can of course use the Debian init script to start the monitoring:
/etc/init.d/monit start
For this to work you must enable the service by changing the file /etc/default/monit:
# 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=180
For more example of monit check the monit homepage.
[ Send Message | View Steve's Scratchpad | View Weblogs ]
After reading this I setup simple monitoring of my host, with a few services:
- Apache
- Bind
- ClamAV
- Exim4
- MySQL
- OpenSSH
You can see the configuration file here.
I figured it is worth posting since the paths all match the Debian system...
Steve
--
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
If you set up the templates correctly, the only noticable time you need to invest in nagios is the initial setup.
i.e. have a "web server" template, a "mail server" template, etc.
[ Parent | Reply to this comment ]
Many thanks for a great article, MOST useful.
--
"It's Not Magic, It's Work"
Adam
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
apt-cache search zabbix returns nothing..
When i was looking for monitoring soft i chose spong.
Spong in unmaintained for 2 years already but works
great and is more KISS than NAGIOS. I could
not get nagious to work, but spong was so simple
i even wrote a few plugins for it myself.
[ Parent | Reply to this comment ]
To use this repository, insert this line to your sources.list:
deb http://www.opf.slu.cz/zabbix stable contrib #(for stable distribution)
deb http://www.opf.slu.cz/zabbix testing contrib #(for testing distribution)
deb http://www.opf.slu.cz/zabbix unstable contrib #(for unstable distribution)
Then install required packages.
* zabbix-server[testing,unstable] (server processess zabbix_suckerd, zabbix_trapperd)
* zabbix-agent[stable,testing,unstable] (staticaly linked agent without dependencies, possible to install everywhere)
* zabbix-doc[stable,testing,unstable]
* zabbix-frontend-php[testing,unstable] (PHP frontend to administration)
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
http://www.linpro.no/projects/munin/
or apt-cache search munin
[ Parent | Reply to this comment ]
'mon' is a good alternative, too.
More feature complete but not more complex to setup.
http://www.kernel.org/pub/software/admin/mon/html/
[ Parent | Reply to this comment ]
I just deployed monit on a few servers last month and I have been very impressed with it. IMO, this and nagios are not in the same category- I use monit for some security checking (md5sums of binaries) and making sure services restart properly on failure.
[ Parent | Reply to this comment ]
And compare to that Monit is very easy.
Cheers,
Hardik Dalwadi.
[ Parent | Reply to this comment ]
but, please move
/etc/monitrc
to
/etc/monit/monitrc
cu icewalker
[ Parent | Reply to this comment ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
Done. Thanks for the notice.
Steve
--
[ Parent | Reply to this comment ]
Currently, we monitor ~100 servers with Nagios for fault reporting and cacti for graphing load averages for memory, cpu, network utilization, etc (tt uses rrdtool internally and produces some nice looking graphs).
[ Parent | Reply to this comment ]
if failed port 22 type tcp 22 with timeout 40 seconds then alert
you need to remove 22 after "tcp" or it will fail
[ Parent | Reply to this comment ]
Ilya Grigorik has written a detailed HOWTO for using Monit to manage Mongrel processes for serving Ruby on Rails applications. It's here:
http://www.igvita.com/blog/2006/11/07/monit-makes-mongrel-play-ni ce/
ED
[ Parent | Reply to this comment ]