When I use crm_standby -U node2 -v false to bring a secondary node out
of standby my esources are stopped for a few seconds on the active node
and then restarted (still on the active node).
Also, when running the hb_report program I got the following. (I am
running Ubuntu 7.10 but I have relin
Hi,
On Thu, Feb 07, 2008 at 04:57:49PM +0100, Lars Marowsky-Bree wrote:
> On 2008-02-07T16:33:48, Dejan Muhamedagic <[EMAIL PROTECTED]> wrote:
>
> > This is very strange. Are you sure that you're running bash and
> > not dash? It's such a mishmash with all those xxshes. I'm off to
> > check that
On 2008-02-07T16:33:48, Dejan Muhamedagic <[EMAIL PROTECTED]> wrote:
> This is very strange. Are you sure that you're running bash and
> not dash? It's such a mishmash with all those xxshes. I'm off to
> check that dash thing.
Why not simply specify #!/bin/bash explicitly?
Other scripts require
Hi,
On Thu, Feb 07, 2008 at 01:13:12PM +, Paul Court wrote:
> When I use crm_standby -U node2 -v false to bring a secondary node out of
> standby my esources are stopped for a few seconds on the active node and
> then restarted (still on the active node).
>
> Also, when running the hb_report
On Feb 7, 2008, at 2:13 PM, Paul Court wrote:
When I use crm_standby -U node2 -v false to bring a secondary node
out of standby my esources are stopped for a few seconds on the
active node and then restarted (still on the active node).
Hi,
The short answer is that the drbd0 most wants to
Quick FYI... this bug has now been fixed and will be in the next
pacemaker release (due in 2 or 3 weeks)
On Mon, Feb 11, 2008 at 2:41 PM, Andrew Beekhof <[EMAIL PROTECTED]> wrote:
>
> On Feb 7, 2008, at 2:13 PM, Paul Court wrote:
>
> > When I use crm_standby -U node2 -v false to bring a secondar
