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
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 <[email protected]> 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 <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Date: Thursday, April 25, 2013 8:53 PM
To: Cloud Dev <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
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
