SureI've attached a crm_report to the bug at
http://bugs.clusterlabs.org/show_bug.cgi?id=5007
Thanks!
On Sun, Nov 13, 2011 at 6:00 PM, Andrew Beekhof wrote:
> On Sun, Oct 16, 2011 at 5:43 AM, Chris Redekop wrote:
> > Andrew: It's not that the slave IP doesn't move back...it's that the
> sl
On Sun, Oct 16, 2011 at 5:43 AM, Chris Redekop wrote:
> Andrew: It's not that the slave IP doesn't move back...it's that the slave
> IP simply doesn't run *anywhere*even when both nodes are up, the slave
> ip will not run anywhere. I'm fairly convinced this is a bug
Fair enough, could yo
Andrew: It's not that the slave IP doesn't move back...it's that the slave
IP simply doesn't run *anywhere*even when both nodes are up, the slave
ip will not run anywhere. I'm fairly convinced this is a bug
On Thu, Sep 29, 2011 at 1:21 AM, Andrew Beekhof wrote:
> On Sat, Aug 27, 2011 a
On Sat, Aug 27, 2011 at 9:07 AM, Chris Redekop wrote:
> I'm attempting to set up a master/slave database cluster where the master is
> R/W and the slave is R/O. The master failure scenario works fine (slave
> becomes master, master vip moves over)however when the slave resource
> goes down I
Hi,
On Fri, Aug 26, 2011 at 05:07:13PM -0600, Chris Redekop wrote:
> I'm attempting to set up a master/slave database cluster where the master is
> R/W and the slave is R/O. The master failure scenario works fine (slave
> becomes master, master vip moves over)however when the slave resource
>
It seems to me like this would be a fairly common scenario, but the fact
that there are no replies makes me think I'm trying to set this whole thing
up incorrectly. Am I not doing this the "normal" way? or is it just not as
common as I would expect?or is this whole thing just a stupid newbie
q
