I meant in the form of a hb_report which contains the necessary logs
and status information necessary to diagnose your issue.
On Mon, Apr 4, 2011 at 12:11 PM, Muhammad Sharfuddin
wrote:
>
> On Mon, 2011-04-04 at 10:42 +0200, Andrew Beekhof wrote:
>> On Thu, Mar 24, 2011 at 7:42 PM, Muhammad Sharf
On Mon, 2011-04-04 at 10:42 +0200, Andrew Beekhof wrote:
> On Thu, Mar 24, 2011 at 7:42 PM, Muhammad Sharfuddin
> wrote:
> > we have two resources A and B
> > Cluster starts A on node1, and B on node2, while failover node for A is
> > node2 and failover node for B is node1
> >
> > B cant start wi
On Thu, Mar 24, 2011 at 7:42 PM, Muhammad Sharfuddin
wrote:
> we have two resources A and B
> Cluster starts A on node1, and B on node2, while failover node for A is
> node2 and failover node for B is node1
>
> B cant start without A, so I have following location rules:
>
> order first_A_
we have two resources A and B
Cluster starts A on node1, and B on node2, while failover node for A is
node2 and failover node for B is node1
B cant start without A, so I have following location rules:
order first_A_then_B : A B
Problem/Question
now if B fails due to n
