Better yet, did you open your iptables for port 8135 and 9090? That's usually when see those errors.
Thank you, Matt On Apr 9, 2013, at 7:54 PM, "Ahmad Emneina" <[email protected]> wrote: > did you change your host parameter in the global config to 0.0.0.0? it > should be set to the actual ip of the host, hosting the cloustack > management service. > > 0.0.0.0, bad! > > > On Tue, Apr 9, 2013 at 4:27 PM, Maurice Lawler <[email protected]>wrote: > >> 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 >> >>
