I'd make a backup of the db, and delete the entries where the MS is down. Hopefully that'll clear up your logs.
Ahmad On Apr 18, 2013, at 7:59 PM, Maurice Lawler <maurice.law...@me.com> wrote: > I'm 100% sure it's user error! As always *grin* Of course I removed my IP > address / hostname. > > - Maurice > > The output is: > > mysql> SELECT * FROM mshost\G; > *************************** 1. row *************************** > id: 1 > msid: 219948120943996 > runid: 1366256187370 > name: myhostname.domain.com > state: Down > version: 4.0.1.20130201075054 > service_ip: myipaddress > service_port: 9090 > last_update: 2013-04-19 01:49:19 > removed: NULL > alert_count: 0 > *************************** 2. row *************************** > id: 2 > msid: 279278805451357 > runid: 1366250623758 > name: myhostname.domain.com > state: Down > version: 4.0.1.20130201075054 > service_ip: myipaddress > service_port: 9090 > last_update: 2013-04-18 03:32:29 > removed: NULL > alert_count: 0 > *************************** 3. row *************************** > id: 3 > msid: 279278805450862 > runid: 1366337908232 > name: myhostname.domain.com > state: Up > version: 4.0.1.20130201075054 > service_ip: myipaddress > service_port: 9090 > last_update: 2013-04-19 02:57:12 > removed: NULL > alert_count: 0 > 3 rows in set (0.00 sec) > > > > On Apr 18, 2013, at 02:11 PM, Chiradeep Vittal <chiradeep.vit...@citrix.com> > wrote: > >> Maurice, it appears to be something specific to the sequence of actions >> you took or your environment. >> >> Developers and QA kill and restart their management servers dozens of >> times a day and have (AFAIK) never seen this issue. >> >> What are the entries in the mshost table? >> >> >> On 4/17/13 11:20 PM, "Maurice Lawler" <maurice.law...@me.com> wrote: >> >> >Thank you. How would I correct this and why would the table state >> >something other then what I have setup, what would have caused that? >> > >> > >> >On Apr 18, 2013, at 12:27 AM, Chiradeep Vittal >> ><chiradeep.vit...@citrix.com> wrote: >> > >> >> That's probably not what the mshost table thinks? >> >> >> >> On 4/17/13 11:00 AM, "Maurice Lawler" <maurice.law...@me.com> wrote: >> >> >> >>> No. I have ONE server running. >> >>> >> >>> One MS - One Install of CS - One of everything. All on the same IP >> >>> address. >> >>> >> >>> >> >>> On Apr 17, 2013, at 12:05 PM, Chiradeep Vittal >> >>> <chiradeep.vit...@citrix.com> wrote: >> >>> >> >>>> You probably have another MS connecting to the same database? >> >>>> >> >>>> On 4/17/13 9:49 AM, "Maurice Lawler" <maurice.law...@me.com> wrote: >> >>>> >> >>>>> No the management IP hasn't changed. My question is why when >> >>>>>restarting >> >>>>> Cloud Management the issue is cleared up. Then almost an hour later, >> >>>>>it >> >>>>> starts in again; how do I correct this issue? >> >>>>> >> >>>>> >> >>>>> On Apr 17, 2013, at 12:23 AM, Chiradeep Vittal >> >>>>> <chiradeep.vit...@citrix.com> wrote: >> >>>>> >> >>>>>> Did the management server ip change? It somehow thinks there's 2 >> >>>>>> management servers. >> >>>>>> >> >>>>>> On 4/16/13 7:00 PM, "Maurice Lawler" <maurice.law...@me.com> wrote: >> >>>>>> >> >>>>>>> Greetings, >> >>>>>>> >> >>>>>>> I am having this FLOOD my log. I will have you know, this is ONE >> >>>>>>> server >> >>>>>>> ONE HOST. KVM | CentOS 6.3 | Cloudstack 4.0.1 >> >>>>>>> >> >>>>>>> I have found restarting cloud management solves the issue for >> >>>>>>>awhile, >> >>>>>>> then it starts again. >> >>>>>>> >> >>>>>>> Please advise. >> >>>>>>> >> >>>>>>> - Maurice >> >>>>>>> >> >>>>>>> ==== Eror Log ==== >> >>>>>>> >> >>>>>>> 2013-04-16 20:58:38,993 DEBUG >> >>>>>>> [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) >> >>>>>>> Zone 1 >> >>>>>>> is ready to launch console proxy >> >>>>>>> 2013-04-16 20:58:39,137 DEBUG [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Detected management node left, id:1, >> >>>>>>> nodeIP:MYIPADDRESSHERE >> >>>>>>> 2013-04-16 20:58:39,137 INFO [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESSHERE >> >>>>>>> 2013-04-16 20:58:39,138 INFO [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Management node 1 is detected inactive >> >>>>>>>by >> >>>>>>> timestamp but is pingable >> >>>>>>> 2013-04-16 20:58:39,264 DEBUG >> >>>>>>> [network.router.VirtualNetworkApplianceManagerImpl] >> >>>>>>> (RouterStatusMonitor-1:null) Found 0 routers. >> >>>>>>> 2013-04-16 20:58:40,637 DEBUG [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Detected management node left, id:1, >> >>>>>>> nodeIP:MYIPADDRESSHERE >> >>>>>>> 2013-04-16 20:58:40,637 INFO [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESSHERE >> >>>>>>> 2013-04-16 20:58:40,637 INFO [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Management node 1 is detected inactive >> >>>>>>>by >> >>>>>>> timestamp but is pingable >> >>>>>>> 2013-04-16 20:58:42,062 DEBUG [agent.manager.AgentManagerImpl] >> >>>>>>> (AgentManager-Handler-13:null) Ping from 3 >> >>>>>>> 2013-04-16 20:58:42,063 DEBUG [agent.manager.AgentManagerImpl] >> >>>>>>> (AgentManager-Handler-14:null) Ping from 4 >> >>>>>>> 2013-04-16 20:58:42,138 DEBUG [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Detected management node left, id:1, >> >>>>>>> nodeIP:MYIPADDRESSHERE >> >>>>>>> 2013-04-16 20:58:42,138 INFO [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESSHERE >> >>>>>>> 2013-04-16 20:58:42,138 INFO [cloud.cluster.ClusterManagerImpl] >> >>>>>>> (Cluster-Heartbeat-1:null) Management node 1 is detected inactive >> >>>>>>>by >> >>>>>>> timestamp but is pingable >> >>>>>>> >> >>>>>>> =========================== >> >>>>>> >> >>>>> >> >>>> >> >>> >> >> >> > >>
