On Tue, Oct 5, 2010 at 1:50 PM, Dejan Muhamedagic deja...@fastmail.fm wrote:
Hi,
On Tue, Oct 05, 2010 at 11:18:37AM +0200, Andrew Beekhof wrote:
Dejan: looks like something in the lrm library.
Any idea why the message doesn't contain lrm_opstatus?
Becase this monitor operation never run.
On Thu, Oct 7, 2010 at 11:13 AM, Dejan Muhamedagic deja...@fastmail.fm wrote:
On Thu, Oct 07, 2010 at 09:49:05AM +0200, Andrew Beekhof wrote:
On Tue, Oct 5, 2010 at 1:50 PM, Dejan Muhamedagic deja...@fastmail.fm
wrote:
Hi,
On Tue, Oct 05, 2010 at 11:18:37AM +0200, Andrew Beekhof wrote:
On Thu, Oct 7, 2010 at 6:06 PM, Ron Kerry rke...@sgi.com wrote:
On 10/7/2010 8:00 AM, Andrew Beekhof wrote:
On Thu, Oct 7, 2010 at 11:13 AM, Dejan Muhamedagic deja...@fastmail.fm
wrote:
On Thu, Oct 07, 2010 at 09:49:05AM +0200, Andrew Beekhof wrote:
On Tue, Oct 5, 2010 at 1:50 PM, Dejan
Dejan: looks like something in the lrm library.
Any idea why the message doesn't contain lrm_opstatus?
lrm_targetrc also looks strange.
On Thu, Sep 30, 2010 at 9:41 PM, Ron Kerry rke...@sgi.com wrote:
Folks -
I am seeing the following message sequence that results in a bogus
declaration of
Folks -
I am seeing the following message sequence that results in a bogus declaration of monitor failures
for two resources very quickly after a failover completes (from hendrix to genesis) with all
resources coming up. The scenario is the same for both resources.
CXFS resource monitor
