Hi Guys!
I'm having a strange problem with pacemaker-heartbeat cluster when I put it
in a maintenance-mode.
First of all, let me show my configuration:
[ Pacemaker ]
node $id="23ade9ce-d274-4e56-aa91-9e95a8c08cf7" test-lb02 \
attributes standby="off"
node $id="52ac429f-2b78-4630-bbd8-f
On Tue, Mar 27, 2012 at 9:36 PM, Hugo Deprez wrote:
> Hello,
>
> I do have no-quorum-policy="ignore"
What about fencing?
> Any idea how to reproduce this ?
> Regards,
>
> On 23 February 2012 23:43, Andrew Beekhof wrote:
>>
>> On Thu, Feb 23, 2012 at 9:17 PM, Hugo Deprez
>> wrote:
>> > I don't
Hello,
I do have no-quorum-policy="ignore"
Any idea how to reproduce this ?
Regards,
On 23 February 2012 23:43, Andrew Beekhof wrote:
> On Thu, Feb 23, 2012 at 9:17 PM, Hugo Deprez
> wrote:
> > I don't think so has, I do have over similar cluster on the same network
> and
> > didn't have any
On Thu, Feb 23, 2012 at 9:17 PM, Hugo Deprez wrote:
> I don't think so has, I do have over similar cluster on the same network and
> didn't have any issues.
> The only thing I can detect was that the virtual machine was like
> unresponsive.
> But I think the VM crash was not like a power shutdown
I don't think so has, I do have over similar cluster on the same network
and didn't have any issues.
The only thing I can detect was that the virtual machine was like
unresponsive.
But I think the VM crash was not like a power shutdown more like very slow
then totaly crash.
Even if the drbd-nagios
On Mon, Feb 13, 2012 at 9:57 PM, Hugo Deprez wrote:
> Hello,
>
> does anyone have an idea ?
Well I see:
Feb 8 12:59:05 server01 crmd: [19470]: ERROR: process_lrm_event: LRM
operation drbd-nagios:1_monitor_15000 (90) Timed Out (timeout=2ms)
Feb 8 13:00:05 server01 crmd: [19470]: WARN: cib_r
Hello,
No one has issue like this ?
Regards,
On 13 February 2012 11:57, Hugo Deprez wrote:
> Hello,
>
> does anyone have an idea ?
>
> it seems that at 13:06:38 resources et started on slave member.
> But then there is something wrong on server01 :
>
> Feb 8 13:06:39 server01 pengine: [1946
Hello,
does anyone have an idea ?
it seems that at 13:06:38 resources et started on slave member.
But then there is something wrong on server01 :
Feb 8 13:06:39 server01 pengine: [19469]: info: determine_online_status:
Node server01 is online
Feb 8 13:06:39 server01 pengine: [19469]: notice: u
On Wed, Feb 8, 2012 at 2:29 PM, Hugo Deprez wrote:
> Dear community,
>
> I am currently running different corosync / drbd cluster using VM running on
> vmware esxi host.
> Guest Os are Debian Squeeze.
>
> the active member of the cluster just freeze the VM was unreachable.
> But the resources didn
Dear community,
I am currently running different corosync / drbd cluster using VM running
on vmware esxi host.
Guest Os are Debian Squeeze.
the active member of the cluster just freeze the VM was unreachable.
But the resources didn't achieved to move to the other node.
My cluster has the followi
10 matches
Mail list logo
