On Sat, Oct 20, 2012 at 03:21:34PM +0200, Hilton Gibson wrote: > Can you cc the list your monit configurations?
Here's what I have so far. There is much more I'd like to
investigate, but I'm going slowly and feeling my way.
savage monit.d # cat check-tomcat-7.rc
check process tomcat-7 with pidfile /var/run/tomcat-7.pid
start program = "/etc/init.d/tomcat-7 restart"
stop program = "/etc/init.d/tomcat-7 stop"
# below from
http://fak3r.com/2010/10/07/howto-monitor-tomcat-with-monit-and-munin-in-debian/
if cpu > 60% for 2 cycles then alert
# if cpu > 80% for 5 cycles then restart
# if totalmem > 1500.0 MB for 5 cycles then restart
# if failed host 127.0.0.1 port 113 then alert
# if failed host 127.0.0.1 port 8180 then alert
# if 5 restarts within 5 cycles then timeout
savage monit.d # cat notify.rc
# notify.rc
# monit alert recipients
set alert [email protected]
set alert [email protected]
set alert [email protected]
savage monit.d #
I found that, on Gentoo Linux, you really need to use "restart" rather
than "start", because OpenRC will have Tomcat in "crashed" state and
"start" won't work.
I have no idea why the commented-out parts above want to monitor the
Ident port (113).
Just the default process monitoring has caught several crashes in the
last few weeks, and restarted Tomcat automatically each time.
--
Mark H. Wood, Lead System Programmer [email protected]
Asking whether markets are efficient is like asking whether people are smart.
pgpAKcT4jWYqx.pgp
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
