[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Restarting monit when if it fails and Inittab

From: Martin Pala
Subject: Re: Restarting monit when if it fails and Inittab
Date: Mon, 15 Jul 2002 23:49:12 +0200


i've extended documentation on CVS for monit's init support, text bellow is
taken from new FAQ:

   Q: I want to run monit from init to be respawned in the case of
      monit's crash.

   A: You must have either 'set init' statement in monit configuration
      file or specify -I option on monit command line in the init
      configuration file. Sample /etc/inittab entry for monit:

       # Run monit in standard runlevels
       mo:2345:respawn:/usr/local/sbin/monit -Ic /etc/monitrc

      After you modified init configuration file, you can run following
      command to re-examine runlevel and start monit:

       telinit q

I think that have monit to start from init is the simplest way to watch
monit. Hope it will help,



----- Original Message -----
From: "Nick Hall" <address@hidden>
To: <address@hidden>
Sent: Monday, July 15, 2002 6:04 PM
Subject: Restarting monit when if it fails and Inittab

> I recently installed monit since I've heard it works well for
> monitoring processes (mainly I wanted it for Apache). This is
> probably a novice mistake but I put monit as a respawn
> process in /etc/inittab since I thought that in the case that
> monit could crash (which may be very unlikely), I wanted a
> way for it to be restarted automatically, or at the very least,
> I be notified. Every couple days I would get a bunch of alerts
> that Apache was restarted at the same time and often when I
> looked Apache wasn't even running after all that. What was
> happening was that as time passed more and more monit processes
> were being spawned and I had 10 separate ones trying to restart
> Apache at the same time. I see monit has a "-I" option to run
> from Init but I can't find any documentation about what that
> specifically does. Does anyone know if this would be something
> I should run to fix the problem of multiple monit processes
> being spawned? Or even better, what is the better way of trying
> to insure that monit stays running? I thought about creating
> another monit config to just make the sure first copy of monit
> is running. Are people doing it this way or just not worrying
> about monit crashing? Thanks for the help,
> Nick
> --
> To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]