[Pacemaker] unexpected Error in Log files

Hi I configured a cluster which consists of four nodes, started Heartbeat/pacemaker on four nodes. after some point of time 4th nodes gone down unexpectedly and find the following error messages while debugging all the log files like ha-debug and messages.log file . can you please help me

Re: [Pacemaker] Upgrading from 1.0 to 1.1

On 07/19/2011 03:22 AM, Andrew Beekhof wrote: On Fri, Jul 15, 2011 at 10:33 PM, Proskurin Kirill k.prosku...@corp.mail.ru wrote: Hello all. I found what I using corosync with pacemaker ver:0 with installed pacemaker 1.1.5 - eg without start a pacemakerd. Sounds wrong. :-) So I try to

Re: [Pacemaker] crm_cluster_connect: Triggered fatal assert at cluster.c:65 : hb_conn != NULL - SOLVED!

Am Dienstag 19 Juli 2011 02:08:03 schrieb Andrew Beekhof: On Tue, Jul 19, 2011 at 9:58 AM, Andrew Beekhof and...@beekhof.net wrote: On Tue, Jul 19, 2011 at 1:17 AM, Nikita Michalko michalko.sys...@a-i-p.com wrote: Hi all! I have succesfully configured and running 2-nodes-cluster. By

[Pacemaker] Configuration for FS over DRBD over LVM

Hi, I am trying to configure an FS running on top of DRBD on top of LVM or:      FS      |     DRBD      |     LVM I am using Pacemaker 1.0.8, Ubuntu 10.04 and DRBD 8.3.7. Reviewing all the manuals (Pacemaker Explained 1.0, DRBD 8.4 User Guide, etc) I came up with this Pacemaker