monit-general
[Top][All Lists]
Advanced

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

Re: frustrated monit not executing processes


From: Michael Steinfeld
Subject: Re: frustrated monit not executing processes
Date: Mon, 27 Aug 2007 19:42:46 -0400

Okay, something has to be wrong here..

I can use "monit -g mongrel start|stop apache"
I can enable and disable monitoring on mongrels but I can't
start/restart/stop them

if I manually use the same start stop command in monit.conf from the
CLI it works.
I just can't get "monit -g mongrel start/stop/restart all" to work.

What the heck am I missing here? What can I give you guys in my config
to help me troubleshoot. I did paste my configs above in the first
email.

thanks again.

On 8/27/07, Michael Steinfeld <address@hidden> wrote:
> On 8/27/07, Martin Pala <address@hidden> wrote:
> >
> >
> > Michael Steinfeld wrote:
> > > On 8/27/07, Jovan Kostovski <address@hidden> wrote:
> > >> On 8/27/07, Michael Steinfeld <address@hidden> wrote:
> > >>> Am I missing something here?
> > >>>
> > >>> set httpd port 28212 and
> > >>>     #use address   # only accept connection from localhost
> > >>>     allow localhost     # allow localhost to connect to the server and
> > >>>     allow admin:password    # require user 'admin' with password 'monit'
> > >> Try:
> > >> set httpd port 28212
> > >>     allow localhost
> > >>     allow admin:password
> > >
> > > tried that it didn't help. I have no problem getting access to the web
> > > interface of monit. That's all fine. But when I attempt to stop/start
> > > any of my services *nothing*.
> > >
> > >
> > >> don't add "and" after the port number. If this doesn't work
> > >> Check if that port (if it's not a typo, the default port is 2812)
> > >> is not used by some other service or it's blocked on firewall.
> > >>
> > >
> > > I have it on that port and it is not blocked for certain.
> > >
> > > Any other ideas???? Thanks.
> > >
> >
> > Monit CLI is using the monit http to request the action. Is it using the
> > same monitrc (configuration file) as the monit daemon? You can run both
> > - monit daemon and CLI in verbose monde, using -v option and check
> > output and logs.
> >
> > You can use sniffer to check the traffic between monit CLI and daemon
> > (tracing localhost:28212 should be sufficient) and check for reset/rejects.
> >
> > You can also try to connect to localhost:28212 for example using telnet
> > and check if the connection works.
>
> did that, everything looks good. Let me be a little clearer. When I
> try to use http://server:port and click on any service and restart it,
> nothing happens and I get an email that said "Can't execute" when I
> use the CLI and add -v that is how I saw the errors I posted above.
>
>
>
>
>
>
> >
> > Martin
> >
> >
> > --
> > To unsubscribe:
> > http://lists.nongnu.org/mailman/listinfo/monit-general
> >
>
>
> --
> Michael Steinfeld
> Linux Admin/Developer
> AIM: mikesteinfeld
> GTALK: address@hidden
>


-- 
Michael Steinfeld
Linux Admin/Developer
AIM: mikesteinfeld
GTALK: address@hidden




reply via email to

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