This discussion is archived
3 Replies Latest reply: Jan 8, 2013 7:28 AM by user157995 RSS

o2hbmonitor issues?

user157995 Explorer
Currently Being Moderated
We have a 2 node OVM 3.0.3 cluster running server pool fs on a standard NFS (linux nfs) server and periodically, we get an increasing amount of o2hbmonitor alerts, while almost always end up in a fencing activity.:

Jan 2 14:58:33 botwavh01 o2hbmonitor: Last ping 38520 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 2 14:58:35 botwavh01 o2hbmonitor: Last ping 40524 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 2 14:58:37 botwavh01 o2hbmonitor: Last ping 42528 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 2 14:58:39 botwavh01 o2hbmonitor: Last ping 44528 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 2 14:58:41 botwavh01 o2hbmonitor: Last ping 46532 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 2 14:58:43 botwavh01 o2hbmonitor: Last ping 48536 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 2 14:58:45 botwavh01 o2hbmonitor: Last ping 50540 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 2 14:59:17 botwavh01 o2hbmonitor: Last ping 30852 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 2 14:59:19 botwavh01 o2hbmonitor: Last ping 32856 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:57:12 botwavh01 o2hbmonitor: Last ping 30256 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:57:14 botwavh01 o2hbmonitor: Last ping 32260 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:57:16 botwavh01 o2hbmonitor: Last ping 34264 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:57:18 botwavh01 o2hbmonitor: Last ping 36268 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:57:20 botwavh01 o2hbmonitor: Last ping 38272 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:58:22 botwavh01 o2hbmonitor: Last ping 33444 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:58:24 botwavh01 o2hbmonitor: Last ping 35448 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:58:56 botwavh01 o2hbmonitor: Last ping 30116 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:58:58 botwavh01 o2hbmonitor: Last ping 32120 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:00 botwavh01 o2hbmonitor: Last ping 34124 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:02 botwavh01 o2hbmonitor: Last ping 36128 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:04 botwavh01 o2hbmonitor: Last ping 38132 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:06 botwavh01 o2hbmonitor: Last ping 40136 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:08 botwavh01 o2hbmonitor: Last ping 42140 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:10 botwavh01 o2hbmonitor: Last ping 44144 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:12 botwavh01 o2hbmonitor: Last ping 46148 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:14 botwavh01 o2hbmonitor: Last ping 48152 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:16 botwavh01 o2hbmonitor: Last ping 50156 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:18 botwavh01 o2hbmonitor: Last ping 52160 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:20 botwavh01 o2hbmonitor: Last ping 54164 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:22 botwavh01 o2hbmonitor: Last ping 56168 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1
Jan 7 14:59:24 botwavh01 o2hbmonitor: Last ping 58172 msecs ago on /dev/dm-3, 0004FB00000500008898AEE351A0A3D1


any suggestions? The other node in the cluster sees similar messages during the same time but never resulted in a fence

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points