O2CB_HEARTBEAT_THRESHOLD not set

Bug #1715251 reported by Sebastian Müller
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OCFS2 Tools
Fix Released
Unknown
ocfs2-tools (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

After Upgrading to Kernel 4.4.0-93-generic

Sep 5 23:34:11 vmsrv17 kernel: [ 1321.299778] (o2hb-3F82744807,3467,11):o2hb_check_slot:895 ERROR: Node 10 on device sd
b1 has a dead count of 302000 ms, but our count is 62000 ms.
Sep 5 23:34:11 vmsrv17 kernel: [ 1321.299778] Please double check your configuration values for 'O2CB_HEARTBEAT_THRESHO
LD'
Sep 5 23:34:11 vmsrv17 kernel: [ 1321.374058] (o2hb-3F82744807,3467,11):o2hb_check_slot:895 ERROR: Node 11 on device sd
b1 has a dead count of 302000 ms, but our count is 62000 ms.
Sep 5 23:34:11 vmsrv17 kernel: [ 1321.374058] Please double check your configuration values for 'O2CB_HEARTBEAT_THRESHOLD'

From now
/sys/kernel/config/cluster/${CLUSTER}/heartbeat/threshold
is know as
/sys/kernel/config/cluster/${CLUSTER}/heartbeat/dead_threshold

Need to be changed in /etc/init.d/o2cb LINE 210

Revision history for this message
Joshua Powers (powersj) wrote :

It also appears that the upstream maintainers felt this should be fixed in the kernel instead and sure enough it was changed in the kernel recently:

https://lkml.org/lkml/2017/7/3/709

This seems to indicate that the patch from the below Debian bug is no longer necessary:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858623

I don't see the issue in Xenial, but I do see it only in Artful. Can you confirm that this you were running version 1.8.5-2 in Artful?

Changed in ocfs2-tools (Ubuntu):
status: New → Confirmed
Revision history for this message
Joshua Powers (powersj) wrote :

This appears to be fixed in artful and later releases, marking this as fixed released.

Changed in ocfs2-tools (Ubuntu):
status: Confirmed → Fix Released
Changed in ocfs2-tools:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.