hii Tomas,
"missed too ... heartbeat ..." this error is generally network and
comminucation problems. You should tcpdump for the event. you using tcpdump,
find source of this error.
example cman to cman communication,
16:40:13.540514 IP node1.domain.com.6809 > 10.0.0.255.6809: UDP, length 28
16:40:14.037110 IP node2.domain.com.6809 > 10.0.0.255.6809: UDP, length 28
16:40:15.059749 IP node3.domain.com.6809 > 10.0.0.255.6809: UDP, length 28
16:41:28.568924 IP node1.domain.com.6809 > 10.0.0.255.6809: UDP, length 28
16:41:29.016120 IP node2.domain.com.6809 > 10.0.0.255.6809: UDP, length 28
16:41:30.046889 IP node3.domain.com.6809 > 10.0.0.255.6809: UDP, length 28
From: "Tomas Hoger" <tomas.hoger@xxxxxxxxx>
Reply-To: linux clustering <linux-cluster@xxxxxxxxxx>
To: "linux clustering" <linux-cluster@xxxxxxxxxx>
Subject: Re: Cluster rejoin problem - 4U3, two node cluster
Date: Wed, 4 Jul 2007 18:36:46 +0200
On 7/4/07, mehmet celik <bsd_daemon@xxxxxxx> wrote:
when you do restart. which services run on the node1 ???
Cluster only use one service (consisting of IP, filesystems and
applications) and it was running on node1 before it was rebooted.
Logs also show that service was moved to node2 during node1's
shutdown.
when network problem, you get this error.
We haven't noticed any network-related problems.
th.
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
_________________________________________________________________
http://liveearth.msn.com
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
