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: "us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>" <us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>> Date: Tuesday, April 9, 2013 4:27 PM To: "us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>" <us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>>, "us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>" <us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>> Cc: Cloud Dev <dev@cloudstack.apache.org<mailto:dev@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
