Hi Benjamin, Tait,
Thanks for the advice,
setting up heartbeat to look for an IP was easy, monitoring looks a bit
more complex so i'll have to dive into that.
at least now i know the right direction to look for,
Thanks,
Wessel
On 05/28/2012 09:01 PM, Tait Clarridge wrote:
>> Thanks Mark, that does make it more clear,
>> i've made a setup and heartbeat does that by default,
>> when heartbeat shuts down it's stops slapd as well and assignes the ip
>> to machine2 and starts slapd there ,
>> what i want is that it already has slapd running on the failover but
>> still checks that service for availability. that way i won't have an
>> outdated database on the failover ldap server.
>> would you know if there is a way of making heartbeat not sending the
>> stop command to a particular resource or do i need write a script to
>> (not) do this? i wouldn't mind a script but if that function is already
>> there i'd rather use that one.
>>
>> Thanks, Wessel
>
> Wessel,
>
> Just pass heartbeat an IP, not a service.
> If you use IPaddr2 it will also send a gratuitous ARP that will cut down
> the failover time.
>
> eg.
>
> primarynode.mycompany.com IPaddr2::10.10.10.50/24/eth0
>
> All the services will stay running, if you want to do service checks to
> watch slapd to see if it breaks you can use the "mon" project to kickoff
> a heartbeat failover.
>
> -Tait
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
