The Problem was solved by changing the OCFS2 timeout values to
O2CB_HEARTBEAT_THRESHOLD=61
O2CB_IDLE_TIMEOUT_MS=6
O2CB_KEEPALIVE_DELAY_MS=4000
O2CB_RECONNECT_DELAY_MS=4000
Hi,
Hi,
On Fri, Jun 05, 2009 at 12:06:11PM +0100, florian.engelm...@bt.com
wrote:
Hi,
On
Hi,
On Thu, Jun 04, 2009 at 03:47:03PM +0100, florian.engelm...@bt.com
wrote:
Hello,
this is a little bit off topic but maybe anybody can help me. The
physical setup of our Debian etch heartbeat cluster looks like this:
Cluster of two nodes connected with bonding to the network,
Hi,
Hi,
On Fri, Jun 05, 2009 at 12:06:11PM +0100, florian.engelm...@bt.com
wrote:
Hi,
On Thu, Jun 04, 2009 at 03:47:03PM +0100, florian.engelm...@bt.com
wrote:
Hello,
this is a little bit off topic but maybe anybody can help me.
The
physical setup of our Debian etch
Hello,
I spent the whole afternoon to search for a good heartbeat v2
documentation, but it looks like this is somehow difficult. Maybe
someone in here can help me?
The only good doc is Andrews Configuration_Explained. See:
I was now reading the great links Michael gave me and I learned a lot.
But I am still a little confused about openAIS / Heartbeat / Pacemaker.
I understood (if I am right) that pacemaker is a part (big) of heartbeat
2. So if you want to use heartbeat 3 you have to use pacemaker.
Pacemaker is also
Hello,
we are testing debian lenny at the moment. We are running debian etch
successfull with heartbeat2 with crm disabled. On debian lenny we want to run
heartbeat2 with crm enabled but we have a lot of problems.The GUI forgets
attributes of resources and is not usable to configure the
