With one host but end up with multiple node records in CloudStack DB can happen in following cases,
1) Network adapter has been replaced (we use MAC address on the NIC to inherit an unique identifier for the management server node) 2) management server setup is a VM clone? 3) re-installation of management sever but using the same database? If you indeed just have one management server node, to correct the situation, you may login to the database, looking for table "mshost", identify the dead node (in your case, node 2) and delete it from the table. Kelven On 4/10/13 11:54 PM, "Maurice Lawler" <maurice.law...@me.com> wrote: >Considering this is one host utilizing KVM. Not sure how that would be >possible. :/ > >Kelven Yang <kelven.y...@citrix.com> wrote: > >>If it is not 0.0.0.0 IP address issue. You may need to check if you have >>a orphan/stuck MS server running at node 2, your MS on node 2 may be >>shown as running but for some reason it is stuck and stopped to tick the >>database heartbeat >> >>Kelven >> >>From: Maurice Lawler >><maurice.law...@me.com<mailto:maurice.law...@me.com>> >>Reply-To: >>"users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>" >><users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>> >>Date: Tuesday, April 9, 2013 4:27 PM >>To: "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>" >><users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>>, >>"users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>" >><users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>> >>Cc: Cloud Dev >><d...@cloudstack.apache.org<mailto:d...@cloudstack.apache.org>> >>Subject: Cluster-Heartbeat Error >> >>The errors below are flooding my >>/var/log/cloud/management/management-cloud-log. >> >>Please advise. >> >>- Maurice >> >> >> >> >>2013-04-09 17:22:12,183 DEBUG [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Detected management node left, id:2, >>nodeIP:0.0.0.0 >>2013-04-09 17:22:12,183 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0 >>2013-04-09 17:22:12,184 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Management node 2 is detected inactive by >>timestamp but is pingable >>2013-04-09 17:22:13,682 DEBUG [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Detected management node left, id:2, >>nodeIP0.0.0.0 >>2013-04-09 17:22:13,682 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0 >>2013-04-09 17:22:13,683 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Management node 2 is detected inactive by >>timestamp but is pingable >>2013-04-09 17:22:15,184 DEBUG [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Detected management node left, id:2, >>nodeIP0.0.0.0 >>2013-04-09 17:22:15,184 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Trying to connect to0.0.0.0 >>2013-04-09 17:22:15,184 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Management node 2 is detected inactive by >>timestamp but is pingable >>2013-04-09 17:22:16,684 DEBUG [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Detected management node left, id:2, >>nodeIP:0.0.0.0 >>2013-04-09 17:22:16,684 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0 >>2013-04-09 17:22:16,684 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Management node 2 is detected inactive by >>timestamp but is pingable >>2013-04-09 17:22:18,183 DEBUG [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Detected management node left, id:2, >>nodeIP0.0.0.0 >>2013-04-09 17:22:18,183 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Trying to connect to0.0.0.0 >>2013-04-09 17:22:18,183 INFO [cloud.cluster.ClusterManagerImpl] >>(Cluster-Heartbeat-1:null) Management node 2 is detected inactive by >>timestamp but is pingable >>
