cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maurice Lawler <maurice.law...@me.com>
Subject Cluster Heartbeat
Date Fri, 26 Apr 2013 03:53:35 GMT
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´╗┐

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
    • Unnamed multipart/related (inline, None, 0 bytes)
View raw message