Hi Andrew,
> Yes please.
http://developerbugs.linux-foundation.org/show_bug.cgi?id=2161
Best Regards,
Hideo Yamauchi.
--- Andrew Beekhof wrote:
> 2009/7/23 :
> > Hi Andrew,
> >
> >> Can you open a bug for that.
> >> I suspect the lrmd might be doing the wrong thing, but assign it to
> >> pac
2009/7/23 :
> Hi Andrew,
>
>> Can you open a bug for that.
>> I suspect the lrmd might be doing the wrong thing, but assign it to
>> pacemaker until I can prove that :-)
>
> All right.
> Had better I register problem in bugzilla?
Yes please.
___
Pacema
Hi Andrew,
> Can you open a bug for that.
> I suspect the lrmd might be doing the wrong thing, but assign it to
> pacemaker until I can prove that :-)
All right.
Had better I register problem in bugzilla?
#As for me, a problem understands the thing in lrmd.
Best Regards,
Hideo Yamauchi.
--- An
2009/7/22 :
> Hi Andrew,
>
>
>> If the crmd dies, then I (IIRC) the lrmd cancels all existing resource
>> monitoring.
>> However, when the crmd is recovered, it should setup the resource
>> monitoring again.
>>
>> Is the second part not happening?
>
> There are some patterns in a problem.
>
> When
Hi Andrew,
> If the crmd dies, then I (IIRC) the lrmd cancels all existing resource
> monitoring.
> However, when the crmd is recovered, it should setup the resource
> monitoring again.
>
> Is the second part not happening?
There are some patterns in a problem.
When crmd/stonithd restarts in
2009/7/17 :
> Hi Andrew,
>
>> What do you mean by monitor here?
>> Do you mean that pacemaker would no longer detect if those two processes
>> died?
>
> This monitor means the monitor of the resource.
> When these processes fall, the monitor of the resource of lrmd/stonithd stops.
> For example,
Hi Andrew,
> What do you mean by monitor here?
> Do you mean that pacemaker would no longer detect if those two processes died?
This monitor means the monitor of the resource.
When these processes fall, the monitor of the resource of lrmd/stonithd stops.
For example, the monitor of external/ssh a
On Fri, Jul 17, 2009 at 3:34 AM, wrote:
> Hi,
>
> We began shift investigation to the combination of Pacemaker and
> corosync/openais now.
>
> We put Pacemaker and openais(whitetank) together and confirmed movement at
> the time of the process
> trouble.
> (This is the function that a reboot eme
Hi,
We began shift investigation to the combination of Pacemaker and
corosync/openais now.
We put Pacemaker and openais(whitetank) together and confirmed movement at the
time of the process
trouble.
(This is the function that a reboot emergency occurred by a combination with
Heartbeat.)
I let
