Thanks Andreas, Still no luck unfortunately. I’m thinking that perhaps pacemaker is not really the tool for the job here as I explicitly don’t want to control my directory servers but just healthcheck and fail over on detection of functional failure.
Regards, Bernie From: Andreas Kurz [mailto:[email protected]] Sent: 20 February 2016 19:31 To: Cluster Labs - All topics related to open-source clustering welcomed Subject: Re: [ClusterLabs] Pacemaker for 389 directory server with multi-master replication Hello, On Sat, Feb 20, 2016 at 4:11 PM, Bernie Jones <[email protected]> wrote: Hi Andreas, Many thanks for your suggestion. Actually, this is the last configuration that I tried, but it still didn’t seem to do the job: pcs property set stonith-enabled=false Stonith is your friend! pcs property set no-quorum-policy=ignore pcs resource defaults resource-stickiness=100 pcs resource create LDAP_Cluster_IP ocf:heartbeat:IPaddr2 ip=192.168.26.100 cidr_netmask=32 op monitor interval=5s pcs resource create dirsrv lsb:dirsrv op monitor interval="6s" role="Master" timeout="2s" There is no master role for simple clones. pcs resource clone dirsrv pcs constraint order LDAP_Cluster_IP then dirsrv-clone I would first start the application if it does not need to bind to a specific IP. pcs constraint colocation add dirsrv-clone with LDAP_Cluster_IP INFINITY You want it the other way round ... IP must follow application. Regards, Andreas --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_______________________________________________ Users mailing list: [email protected] http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
