Dejan Muhamedagic wrote: > Hi, > > On Sun, Jun 21, 2009 at 11:53:52PM +0200, Christoph Lechner wrote: >> Hi all, >> >> I want my active/standby heartbeat setup (Version 2.1.4, CRM enabled) to >> run a specific resource on the standby node only. The resource is a >> Postfix null-client, that is the Postfix mailer is configured to accept >> mail from port 25 over the loopback interface only, so programs running >> on the machine don't see any difference when sending mail. So I can get >> notification when the RAID status changes, etc. >> >> I guess I need a location constraint, but I wasn't able to figure out >> what exactly to do. > > Just make a location constraint with the score of -INFINITY for > the active node. Then it won't ever run there.
OK, so I entered the constraints <!-- for testing only --> <rsc_location id="run-mail-on-s1" rsc="postfix-master"> <rule id="prefered_run-mail-on-s1"> <expression attribute="#uname" operation="eq" value="ab-server1"/> </rule> </rsc_location> and <rsc_colocation id="mail-master-and-nullclient-on-different-hosts" from="postfix-master" to="postfix-nullclient" score="-INFINITY"/> in the CIB. postfix-master and postfix-nullclient run on different hosts, with postfix-master sticking to ab-server1 at the moment. postfix-nullclient is started on the second (=standby) node. But if I shutdown heartbeat on the standby node, postfix-nullclient always wins over postfix-master, which is highly undesireable, because noone can send me mail. How can I make postfix-master win the election if one node is shut down *and* still have the behavior that the null client runs only on the other host than the master. What is missing now is that if there's only one working node, postfix-master is the winning resource. CU - cl _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
