I missed the original on this but I had something interesting happen yesterday. I installed a new node, introduced it into the cluster and immediately, all of the other nodes died with a kernel panic. Not sure why yet. Mike On Thu, 26 Oct 2006 08:38:04 +0100, Patrick Caulfield wrote: > jason@xxxxxxxxxxxxxx wrote: > >> ok, I was just logging into the 2 nodes of my cluster, tf1 and tf2, I >> noticed that tf1 was NOT >> available via ssh, but tf2 was. tf1 was pingable, but that was it. I >> looked on tft2 and >> noticed that he had taken over the cluster virtual ip address >> >> 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 >> link/ether 00:11:43:d7:c9:c6 brd ff:ff:ff:ff:ff:ff >> inet 192.168.1.6/24 brd 192.168.1.255 scope global eth0 >> inet 192.168.1.7/32 scope global eth0 >> inet6 fe80::211:43ff:fed7:c9c6/64 scope link >> valid_lft forever preferred_lft forever >> >> and in the syslog on tf2, I saw >> Oct 25 20:26:00 tf2 kernel: CMAN: removing node tf1 from the cluster : >> Missed too many >> heartbeats >> > That's the important message in all this, all the rest is just consequence. > > The node has been kicked out of the cluster for not sending heartbeats in a > timely manner. Ether the network is fearfully busy or > the one of nodes is. -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
