if I understand your requirements correctly, you try to establish the following:
you have n servers, let us call them server1, server2, ...
you have m services, let us call them app1, app2, .... Each app has its own IP-Address, can run on any of the servers, but runs only on one server at any given time.
What I did was the following:
* on each server, I created a config file for the server-relevant things (watch cpu, disk full etc)
* for each app I created a seperate config file (and seperate id and pid-file) which resides on storage available to the app regardless of where it is running. This checks on the app itself and starts the gui for that app. In the start-script for the app I start an additional monit instance in the stop-script I unload this instance)
So on each server you have multiple instances of monit running: one for the server itself and an additional one for each app running on the server.
Altogether you then have n+m httpd running.
This setup does not show you in one gui a server plus all the apps running on it, but on the other hand you can look at the app without having to know on what server it is running at the moment.
>>> Sukumar T R <address@hidden> 20.09.2012 19:00 >>>
Thanks for your reply
Here my requirement is little different. I have grouped components or the processes into two groups. So at any point of time only a single group will be running on the active server which is holding the V.I.P.
I have script which will start the components based on the virtual Ip on the server. So by specifying the group name , the respective components of the group is being started. But the monitor gui is not starting. Hope u understand my requirement and problem. If u 've any suggestions , please share on this.
On Sep 20, 2012 5:07 PM, <address@hidden
Send monit-general mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of monit-general digest..."
1. Re: Monit Graphical Interface is not getting started when
monit is started with the group (Martin Pala)
Date: Thu, 20 Sep 2012 16:41:33 +0200
From: Martin Pala <address@hidden>
To: This is the general mailing list for monit
Subject: Re: Monit Graphical Interface is not getting started when
monit is started with the group
Content-Type: text/plain; charset=iso-8859-1
If you want to start monit, type just "./monit" ... it will start in daemon mode (provided you have "set daemon X" statement in your configuration file).
The command which you execute is correct CLI command for starting the group (but it won't stat monti as daemon if it's not running already).
On Sep 20, 2012, at 1:25 PM, Sukumar T R <address@hidden> wrote:
> Am trying to start the monit a group of components using following
> ./monit -c monitrc-app -g GRP_RP_ACTIVE_STANDBY_COMPONENTS start .
> The grouped components are getting started as expected, but am facing an issue where the graphical interface is not started as part of this.
> I need help as this is very critical. If someone has faced the same issue, please share your feedback. I really appreciate your help.
> Thanks & Regards,
> To unsubscribe:
monit-general mailing list
End of monit-general Digest, Vol 116, Issue 32