Thanks for the info and this is the explanation, When you add KVM host into management server, it creates network bridge that affects CloudStack management to identify itself (we use MAC address to derive management server ID). This is a limitation of running KVM host and management server in one machine.
The message may be annoying, but it should not affect CloudStack from normal functioning Kelven From: Maurice Lawler <maurice.law...@me.com<mailto:maurice.law...@me.com>> Date: Friday, April 26, 2013 1:17 PM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Cc: Kelven Yang <kelven.y...@citrix.com<mailto:kelven.y...@citrix.com>> Subject: Re: Cluster Heartbeat Hello Kelven, I am using KVM | CentOS 6.3 | CS 4.0.1 All under ONE server. However, I was as mentioned told to remove the 'Down' instances from mshost; restart and the error continues. - Maurice On Apr 26, 2013, at 01:13 PM, Kelven Yang <kelven.y...@citrix.com<mailto:kelven.y...@citrix.com>> wrote: What is your management server cluster setup look like? If it is a one-node setup, how many network interfaces do you have in the management server node? Kelven From: Maurice Lawler <maurice.law...@me.com<mailto:maurice.law...@me.com><mailto:maurice.law...@me.com<mailto:maurice.law...@me.com>>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>> Date: Thursday, April 25, 2013 8:53 PM To: Cloud Dev <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>>, "us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org><mailto:us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>>" <us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org><mailto:us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>>>, "us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org><mailto:us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>>" <us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org><mailto:us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>>> Cc: "cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org><mailto:cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org>>" <cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org><mailto:cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org>>>, "cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org><mailto:cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org>>" <cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org><mailto:cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org>>> Subject: Cluster Heartbeat Greetings, Within my log of /var/log/cloud/management/management-cloud.log I am seeing the following: 2013-04-25 22:50:11,081 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:MYIPADDRESS 2013-04-25 22:50:11,081 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESS 2013-04-25 22:50:11,081 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp but is pingable 2013-04-25 22:50:12,581 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:MYIPADDRESS 2013-04-25 22:50:12,582 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESS 2013-04-25 22:50:12,582 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp but is pingable 2013-04-25 22:50:14,080 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:MYIPADDRESS 2013-04-25 22:50:14,080 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESS 2013-04-25 22:50:14,080 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp but is pingable 2013-04-25 22:50:15,579 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:MYIPADDRESS 2013-04-25 22:50:15,580 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESS 2013-04-25 22:50:15,580 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp but is pingable 2013-04-25 22:50:17,080 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:MYIPADDRESS 2013-04-25 22:50:17,081 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESS 2013-04-25 22:50:17,081 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp but is pingable 2013-04-25 22:50:18,581 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:MYIPADDRESS 2013-04-25 22:50:18,581 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESS 2013-04-25 22:50:18,581 INFO [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp but is pingable It was preivously told to me to remove the "down" enttries within the table mshost; however, when I do that the error is no longer, but rebooting cloud-management if I were to make a change seems to revert whatever was done via table and the error reappears. Anyone able to help me resolve this once and for all? - Maurice
