On Wed, Jun 14, 2006 at 06:24:35PM +0200, [EMAIL PROTECTED] wrote:
> the sometimes necessary modification of the heartbeat threshold cannot
> be made
> via the script, and, even worse, it is overwritten by write_config(),
> when someone
> calls the script after the modification was made using some
On Wed, Jun 14, 2006 at 06:24:35PM +0200, [EMAIL PROTECTED] wrote:
> maybe this is not the place to file a bug, but
oss.oracle.com/bugzilla is the "correct" place, but all we
really care about is that you bring it to our attention, which you have
done :-)
> the sometimes necessary mod
It's not a sysctl entry. It won't work that way.
Set the required value in /etc/sysconfig/o2cb
and restart the cluster. Do it on all nodes.
[EMAIL PROTECTED] wrote:
> hi,
>
> I'm just thinking about changing the heartbeat threshold of our cluster
> online by issuing
> # echo 31 > /proc/fs/ocfs2_n
hi,
I'm just thinking about changing the heartbeat threshold of our cluster
online by issuing
# echo 31 > /proc/fs/ocfs2_nodemanager/hb_dead_threshold
I thought I read that somewhere ut cannot recall where and I don't find
it
in the FAQ(?).
So is this the way to do it, or is it "stop and restart
I would not recommend that for 1.1.7 to 1.2.1. While neither
the on-disk format nor the messaging has changed since 1.0,
there have been other internal changes which could cause
problems.
The recommendation is documented in the faq... under "Upgrading to 1.2.1".
Marco Friebe wrote:
> Thanks for y
Yes, we are missing that bit. File a bug on http://oss.oracle.com/bugzilla
component ocfs2-tools.
[EMAIL PROTECTED] wrote:
> hi,
>
> maybe this is not the place to file a bug, but
>
> I think there is one in /etc/init.d/o2cb.
>
> the script should be used to create the config file /etc/sysconf
hi,
maybe this is not the place to file a bug, but
I think there is one in /etc/init.d/o2cb.
the script should be used to create the config file /etc/sysconfig/o2cb
by calling
it with "o2cb configure", and the generated config file contains info
not to edit
the file, but to use the script.
hi,
today we had a self fencing node in our cluster and found the lines
below in /var/log/messages.
--snip
Jun 14 13:05:44 bmiam113 kernel: (18,0):o2hb_write_timeout:270 ERROR:
Heartbeat write timeout to device dm-0 after 12000 milliseconds
Jun 14 13:05:44 bmiam113 kernel: Heartbeat thread (18) p
