Hi Marco! Unfortunately this didn't fix the problem. The ping resource works correctly as far as I can see. Because otherwise ms_drbd_ora wouldn't start at all. After I plug out the network cable ping recognizes it and Pacemaker tries to failover (it stops the resources) but it doesn't start them on node2. When I plug in the network cable again the resources correctly start at node1.
If you need more information please tell me! Regards Benjamin Benz -----Ursprüngliche Nachricht----- Von: Marco van Putten [mailto:[email protected]] Gesendet: Do 08.04.2010 15:46 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] Resources don't start on second node after pingfails Hi Benjamin, > rule $id="ms_drbd_ora_on_connected_node-rule" -inf: not_defined pingval > or pingval lte 0 You could give this a try instead: rule $id="ms_drbd_ora_on_connected_node-rule" -inf: not_defined pingval or pingval number:lte 0 Good luck, Marco. _______________________________________________ Pacemaker mailing list [email protected] http://oss.clusterlabs.org/mailman/listinfo/pacemaker
<<winmail.dat>>
_______________________________________________ Pacemaker mailing list [email protected] http://oss.clusterlabs.org/mailman/listinfo/pacemaker
