Thank you for the replies. The problem was really one server which shouldn’t
have been in the cluster at all. It was kind of a leftover, but it continued to
heartbeat in the new cluster.
After completely disconnecting the server from the cluster the issue was gone.
Thanks once again.
--
Danije
If ps aux|grep o2hb does not return anything, means you are using local
heartbeat.
That means you have mismatching ocfs2.conf file. And I suspect the node
where this is failing is the one that has the bad ocfs2.conf file. Compare
the config files from all the nodes and ensure it is the same. Or yo
No, nothing there:
$ ps aux | grep o2hb
root 5724 0.0 0.0 8320 888 pts/0 S+ 22:30 0:00 grep --color
o2hb
Still the same error if i try to mount the iSCSI disk:
o2hb_check_own_slot:590 ERROR: Heartbeat generation mismatch on device (sdb):
expected(2:0x2f32486d4c54730a, 0x54d926d
On node 2, do:
ps aux | grep o2hb
I suspect you have multiple o2hb threads running. If so, restart the o2cb
cluster on that node.
On Mon, Feb 9, 2015 at 10:08 AM, Danijel Krmar <
danijel.kr...@activecollab.com> wrote:
> As said in the title, when I want to mount a iSCSI target on one machine I
>
As said in the title, when I want to mount a iSCSI target on one machine I get
the following error:
(o2hb-3F92114867,7826,3):o2hb_check_own_slot:590 ERROR: Heartbeat generation
mismatch on device (sdb): expected(2:0xa0cf28215b4b1ed3, 0x54d8a036),
ondisk(2:0xb016e6a72676a791, 0x54d8a037)
The sam