Hey Maurice, You should check logs prior to this error, that will show the real problem causing CS to put the host in avoid set.
-Prachi From: Maurice Lawler [mailto:maurice.law...@me.com] Sent: Thursday, June 27, 2013 12:40 PM To: Cloud Dev Subject: Console Proxy VM failed to start Hello, I have finally got both system VM's 'Stopped', however, the secondary storage is running without issue. Whereas, the console proxy will not start, this is from the logs. 2013-06-27 14:36:52,192 DEBUG [allocator.impl.FirstFitAllocator] (consoleproxy-1:FirstFitRoutingAllocator) Host name: lunder.daoenix.com, hostId: 9 is in avoid set, skipping this and trying other available hosts 2013-06-27 14:36:52,192 DEBUG [allocator.impl.FirstFitAllocator] (consoleproxy-1:FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts 2013-06-27 14:36:52,193 DEBUG [cloud.deploy.FirstFitPlanner] (consoleproxy-1:null) No suitable hosts found 2013-06-27 14:36:52,193 DEBUG [cloud.deploy.FirstFitPlanner] (consoleproxy-1:null) No suitable hosts found under this Cluster: 1 2013-06-27 14:36:52,193 DEBUG [cloud.deploy.FirstFitPlanner] (consoleproxy-1:null) Could not find suitable Deployment Destination for this VM under any clusters, returning. 2013-06-27 14:36:52,196 DEBUG [cloud.capacity.CapacityManagerImpl] (consoleproxy-1:null) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: 9 2013-06-27 14:36:52,199 DEBUG [cloud.capacity.CapacityManagerImpl] (consoleproxy-1:null) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 36256 2013-06-27 14:36:52,199 DEBUG [cloud.capacity.CapacityManagerImpl] (consoleproxy-1:null) release cpu from host: 9, old used: 1000,reserved: 0, actual total: 36256, total with overprovisioning: 36256; new used: 500,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-06-27 14:36:52,199 DEBUG [cloud.capacity.CapacityManagerImpl] (consoleproxy-1:null) release mem from host: 9, old used: 1342177280,reserved: 0, total: 25186906112; new used: 268435456,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-06-27 14:36:52,201 WARN [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Exception while trying to start console proxy com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[ConsoleProxy|v-40-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:728) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:464) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:632) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:1166) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1989) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:175) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) I am not well with reading the logs, what is this trying to tell me?
