o2cb configuration options ignored in 16.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
We've been trying to add a 16.04 node (ocfs2-tools 1.6.4-3.1) to our existing OCFS2 filesystem based on Ubuntu 13.04 (ocfs2-tools 1.6.4-2ubuntu1) and , Ubuntu 14.04 (ocfs2-tool 1.6.4-3ubuntu1)
* Node1: Ubuntu 16.04, Slot 1, 10.22.44.21
* Node2: Ubuntu 13.04, Slot 2, 10.22.44.22
* Node3: Ubuntu 14.04, Slot 6, 10.22.44.23
* Node4: Ubuntu 14.04, Slot 7, 10.22.44.24
The exiting system has a O2CB_HEARTBEAT_
Aug 16 15:58:02 node1 kernel: [ 936.294820] (o2hb-37AAEB030
Aug 16 15:58:02 node1 kernel: [ 936.294820] Please double check your configuration values for 'O2CB_HEARTBEAT
Aug 16 15:58:02 node1 kernel: [ 936.294949] (o2hb-37AAEB030
Aug 16 15:58:02 node1 kernel: [ 936.294949] Please double check your configuration values for 'O2CB_HEARTBEAT
Aug 16 15:58:02 node1 kernel: [ 936.295071] (o2hb-37AAEB030
Aug 16 15:58:02 node1 kernel: [ 936.295071] Please double check your configuration values for 'O2CB_HEARTBEAT
Aug 16 15:58:03 node1 kernel: [ 937.123350] o2net: node node3 (num 6) at 10.22.44.23:7777 uses a heartbeat timeout of 120000 ms, but we use 60000 ms locally. Disconnecting.
Aug 16 15:58:03 node1 kernel: [ 937.393608] o2net: node node2 (num 2) at 10.22.44.22:7777 uses a heartbeat timeout of 120000 ms, but we use 60000 ms locally. Disconnecting.
Aug 16 15:58:04 node1 kernel: [ 938.055983] o2net: node node4 (num 7) at 10.22.44.24:7777 uses a heartbeat timeout of 120000 ms, but we use 60000 ms locally. Disconnecting.
Aug 16 15:58:29 node1 kernel: [ 963.213554] o2net: node node3 (num 6) at 10.22.44.23:7777 uses a heartbeat timeout of 120000 ms, but we use 60000 ms locally. Disconnecting.
Aug 16 15:58:30 node1 kernel: [ 964.057995] o2net: node node4 (num 7) at 10.22.44.24:7777 uses a heartbeat timeout of 120000 ms, but we use 60000 ms locally. Disconnecting.
Aug 16 15:58:32 node1 kernel: [ 966.404380] o2net: No connection established with node 2 after 30.0 seconds, check network and cluster configuration.
Aug 16 15:58:32 node1 kernel: [ 966.404390] o2net: No connection established with node 6 after 30.0 seconds, check network and cluster configuration.
Aug 16 15:58:32 node1 kernel: [ 966.404393] o2net: No connection established with node 7 after 30.0 seconds, check network and cluster configuration.
Aug 16 15:58:59 node1 kernel: [ 993.296012] o2net: node node3 (num 6) at 10.22.44.23:7777 uses a heartbeat timeout of 120000 ms, but we use 60000 ms locally. Disconnecting.
Aug 16 15:59:00 node1 kernel: [ 994.060435] o2net: node node4 (num 7) at 10.22.44.24:7777 uses a heartbeat timeout of 120000 ms, but we use 60000 ms locally. Disconnecting.
Aug 16 15:59:02 node1 kernel: [ 996.486396] o2net: No connection established with node 2 after 30.0 seconds, check network and cluster configuration.
Aug 16 15:59:02 node1 kernel: [ 996.486405] o2net: No connection established with node 6 after 30.0 seconds, check network and cluster configuration.
Aug 16 15:59:02 node1 kernel: [ 996.486409] o2net: No connection established with node 7 after 30.0 seconds, check network and cluster configuration.
Aug 16 15:59:05 node1 kernel: [ 999.582560] o2cb: This node could not connect to nodes: 2 6 7.
Aug 16 15:59:05 node1 kernel: [ 999.582607] o2cb: Cluster check failed. Fix errors before retrying.
Aug 16 15:59:05 node1 kernel: [ 999.582647] (mount.
Aug 16 15:59:05 node1 kernel: [ 999.582814] (mount.
Aug 16 15:59:05 node1 kernel: [ 999.582895] ocfs2: Unmounting device (8,32) on (node 0)
Aug 16 15:59:05 node1 kernel: [ 999.582905] (mount.
Changed in ocfs2-tools (Ubuntu): | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.