Re: Cloudstack Old env messed up!

2015-07-30 Thread Daan Hoogland
On Thu, Jul 30, 2015 at 8:58 AM, gagan chhabra wrote: > '6001f2ac-0ea9-43ae-b097-3ac2738eb5f2' exists already something else happened, not that the pool is unreachable. -- Daan

Re: Cloudstack Old env messed up!

2015-07-30 Thread gagan chhabra
I am using CS v-4.3.0 with KVM. You can see the logs below. There is Exception that the storage pool is unreachable. 2015-07-30 12:01:43,472 DEBUG [c.c.a.ApiServlet] (catalina-exec-1:ctx-d97b1e9d) ===START=== 10.129.28.236 -- GET command=deployVirtualMachine&response=json&sessionkey=e8WA8mYwZyXd

Re: Cloudstack Old env messed up!

2015-07-29 Thread Carlos Reátegui
Hi Gagan, I have found that the “insufficient capacity” error can be misleading. What version of CloudStack are you using and what hypervisor are your hosts? With CS 4.5.1 + XenServer 6.5, I just saw “insufficient capacity” when trying to start a stopped instance but the problem was actually a

Re: Cloudstack Old env messed up!

2015-07-29 Thread gagan chhabra
I am just trying to get the Env up and running and its just private to my Institute. There are 4 instances which are being used. There are other stopped VMs which need not be affected during resolving the issues. So cannot wipe everything clean and do a fresh installation. I had been looking into

Re: Cloudstack Old env messed up!

2015-07-28 Thread Daan Hoogland
yeah, what Dag said but not as diplomatic ;) On Tue, Jul 28, 2015 at 4:01 PM, Dag Sonstebo wrote: > Hi Gagan, > > Sounds like you might have a number of problems in your environment. > Before starting to dig too deep can you clarify what you are actually > trying to recover? I.e. are you just try

Re: Cloudstack Old env messed up!

2015-07-28 Thread Dag Sonstebo
Hi Gagan, Sounds like you might have a number of problems in your environment. Before starting to dig too deep can you clarify what you are actually trying to recover? I.e. are you just trying to get the CloudStack environment up and running again or do you have production VM instances running whi

Re: Cloudstack Old env messed up!

2015-07-28 Thread Daan Hoogland
if this setup does not contain any production data promote plan-B to A-status. As this is a very small env I would otherwise safe the data and continue with the previous step. Let us know if there is any reason this should not be convenient. On Tue, Jul 28, 2015 at 3:54 PM, gagan chhabra wrote: >

Cloudstack Old env messed up!

2015-07-28 Thread gagan chhabra
I have been given an already set-up Cloud stack environment with 6 hosts (2 clusters with 3 hosts each) ,1 management server and one NFS storage as primary storage. So in total there are 8 physical machines (6 hosts + 1 cloudstack-mgmt-server + 1 NFS:13TBytes). Management server's storage space is