Ian, When you delete a VM, it eventually gets expunged (deleted) the time this actually takes is controlled by the global settings ' expunge.delay' and 'expunge internal'
Once the VM has been expunged its state in the DB table vm_instance will be 'expunging' and there will be a date/time in the 'removed' column (there it is again!) Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 [email protected] -----Original Message----- From: Ian Young [mailto:[email protected]] Sent: 20 February 2014 19:37 To: [email protected] Subject: Re: Management node is detected inactive by timestamp but is pingable Restarting cloudstack-agent and cloudstack-management made the inactive management node notice go away but the instance is still stuck in an "expunging" state. How can I get rid of it? On Thu, Feb 20, 2014 at 10:55 AM, Ian Young <[email protected]> wrote: > I noticed that there are 12 records in the cloud.mshost table, all of > which have an "Up" state. I only have one management server. Should > I delete the other 11 records? > > > On Thu, Feb 20, 2014 at 10:20 AM, Ian Young <[email protected]>wrote: > >> Yesterday I tried to start an existing instance but it failed. Since >> it was basically a brand new installation, I just decided to destroy >> it and start over. However, it stayed in an "expunging" state and >> remains so today. I cannot create new instances now. The >> management-server.log shows numerous messages like this: >> >> 2014-02-20 10:04:04,442 DEBUG [cloud.cluster.ClusterManagerImpl] >> (Cluster-Heartbeat-1:null) Detected management node left, id:11, >> nodeIP:192.168.100.6 >> 2014-02-20 10:04:04,442 INFO [cloud.cluster.ClusterManagerImpl] >> (Cluster-Heartbeat-1:null) Trying to connect to 192.168.100.6 >> 2014-02-20 10:04:04,442 INFO [cloud.cluster.ClusterManagerImpl] >> (Cluster-Heartbeat-1:null) Management node 11 is detected inactive by >> timestamp but is pingable >> >> The management server and the hypervisor host are the same machine >> (budgetary constraints necessitated this setup) so, obviously, it >> should be able to connect to itself. What is this timestamp it's >> referring to? Is it simply a matter of updating this so the >> management server is no longer considered inactive? >> > > Need Enterprise Grade Support for Apache CloudStack? Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments. Apache CloudStack Bootcamp training courses **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/> 18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/> 17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/> 24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/> 16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/> 23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
