On 23 Apr 2014, at 4:15 am, Tom Parker wrote:
> Good morning
>
> I am trying to restart resources on one of my clusters and I am getting
> the message
>
> pengine[13397]: notice: LogActions: Start domtcot1-qa(qaxen1
> - blocked)
>
> How can I find out why this resource is blocked.
I have attached the config files to this e-mail. The sbd dump is below
[LIVE] qaxen1:~ # sbd -d /dev/mapper/qa-xen-sbd dump
==Dumping header on disk /dev/mapper/qa-xen-sbd
Header version : 2.1
UUID : ae835596-3d26-4681-ba40-206b4d51149b
Number of slots: 255
Sector size
you are missingo cluster configuration and sbd configuration and multipath
config
2014-04-22 20:21 GMT+02:00 Tom Parker :
> Has anyone seen this? Do you know what might be causing the flapping?
>
> Apr 21 22:03:03 qaxen6 sbd: [12962]: info: Watchdog enabled.
> Apr 21 22:03:03 qaxen6 sbd: [12973
Has anyone seen this? Do you know what might be causing the flapping?
Apr 21 22:03:03 qaxen6 sbd: [12962]: info: Watchdog enabled.
Apr 21 22:03:03 qaxen6 sbd: [12973]: info: Servant starting for device
/dev/mapper/qa-xen-sbd
Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Monitoring Pacemaker health
A
Good morning
I am trying to restart resources on one of my clusters and I am getting
the message
pengine[13397]: notice: LogActions: Start domtcot1-qa(qaxen1
- blocked)
How can I find out why this resource is blocked.
Thanks
___
Linux-HA m
>>> Googlemail schrieb am 20.04.2014 um 19:08 in
Nachricht <5353ff24.1030...@googlemail.com>:
[...]
> Hi,
>
> should it be not best practice to not use a the hardware clock in any
> virtualized environment. I would strongly suggest to use an external
> time source.
Hi!
>From some experience I
