Hello I have environment where Node A and Node B have Fedora DS in multimaster replicated setup. I have applications, that connect both nodes (and use LDAP). Then I have application, that can only connect to one IP-address. Applications are what they are, I cannot change how those behave.
I think I need heartbeat setup, where I would have one virtual address C and some kind of magic for heartbeat to (a) poll LDAP (make simple bind or just check that tcp389 is available) (b) when (a) fails, just release virtual IP C (c) if LDAP fails on both nodes, Node A should take over the address C (d) monitoring system (this one I have) deals with LDAP problems and restarts it if needed from init scripts How to achieve this kind of setup? I have no prioir knowledge of heartbeat, I managed to get virtual IP up and running file but don't know how to do the LDAP check? I tried to search mailing list archives, I found some information where heartbeat starts/shuts down LDAP from init scripts, this is not what I need. Any pointers to docs or links? Regards, Kimmo Koivisto _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
