Thanks for the responses,
We wish the server to be a hot standby, so the kamailio service is
running and is ready to take traffic as soon as the virtual IP is
assigned. Kamailio is bound to a fixed IP and DNAT/SNAT is used to
convert the IP of incoming traffic.
Monit is there to make sure that
AFAIK the current "Linux approach" (RedHat, Suse) it to use
pacemaker+corosync and OCF resource scripts.
Pacemaker is the cluster resource manager: control all resources and
monitors services by usage of the OCF scripts
Corosync provides the cluster communication: communication between the
v
An option is to use in the UCARP VIP up/down scripts the commands:
monit start kamailio
monit stop kamailio
Then monit will stop kamailio and no longer do options ping when the
server is standby.
Cheers,
Daniel
On 2/17/11 2:05 PM, Klaus Feichtinger wrote:
Hi,
I have built a similar solutio
Hi,
I have built a similar solution with only one difference: I am using
HEARTBEAT instead of ucarp. In heartbeat it is possible moving
"haresources" from one active host to another. So, I activate MONIT (and
mysql + kamailio) only when the resources (e.g. virtual IP address) are
switched from one
Am 16.02.2011 11:48, schrieb Hugh Waite:
> Hello,
> I am setting up a high-availablilty kamailio system using UCARP to
> failover between active and standby instances. To detect failure, we
> intend to use Monit.
> Monit can monitor the kamailio PID and start the process when needed
> (Example on
