Is this a bug?
Hi, untagged public network doesn't work with Cloudstack 4.4. The virtual router doesn't start. In the log is a Java exception 690 ERROR [c.c.h.h.r.HypervDirectConnectResource] (DirectAgent-70:ctx-318fa261) Unexpected exception: java.lang.NumberFormatException: For input string: "untagged" will shortcut rest of IPAssoc commands Greetings, Björn
Re: System VM not starting
Hi, Is your secondary storage doing OK? Unable to acquire lock on VMTemplateStoragePool: 97 It wants to copy the systemvm template from secondary storage to primary storage in order to start the system vms. Please check both storages can be mounted on your hypervisors. Regards, Remi On 23/09/15 13:30, "Naveen V" wrote: >Hi All, > >I have a cloudstack management server 4.5 as Centos VM , and Host as xen >server 6.2... > >System VM's not starting... below is the error logs > > >com.cloud.exception.AgentUnavailableException: Resource [Host:1] is >unreachable: Host 1: Unable to start instance due to Unable to acquire lock >on VMTemplateStoragePool: 97 > >at >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1109) > >at >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4481) > >at sun.reflect.GeneratedMethodAccessor216.invoke(Unknown Source) > >at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > >at java.lang.reflect.Method.invoke(Method.java:606) > >at >com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) > >at >com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4637) > >at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:103) > >at >org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537) > >at >org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > >at >org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > >at >org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > >at >org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > >at >org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > >at >org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:494) > >at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > >at java.util.concurrent.FutureTask.run(FutureTask.java:262) > >at >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > >at >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > >at java.lang.Thread.run(Thread.java:744) > >Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to >acquire lock on VMTemplateStoragePool: 97 > >at >org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:488) > >at >org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:745) > >at >org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1252) > >at >org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1322) > >at >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:988) > >... 19 more > > > > > > >Exception while trying to start console proxy > >com.cloud.exception.InsufficientServerCapacityException: Unable to create a >deployment for VM[ConsoleProxy|v-39-VM]Scope=interface >com.cloud.dc.DataCenter; id=2 > >at >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:947) > >at >com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4481) > >at sun.reflect.GeneratedMethodAccessor216.invoke(Unknown Source) > >at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > >at java.lang.reflect.Method.invoke(Method.java:606) > >at >com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) > >at >com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4637) > >at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:103) > >at >org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537) > >at >org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > >at >org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > >at >org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > >at >org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > >at >org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > >at >org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:494) > >at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > >at java.util.concurrent.FutureTask.run(FutureTask.java:262) > >at
Re: Expunge
Luis, Do you use shared mount point with your KVM hypervisor or local NFS server? I have tested "Expunge" at my CS 4.5.3 and when I delete VM with "expunge" option -- Cloudstack deletes it from the storage immediately. Can you do the same test and look into management log file ? It would be nice to see trace from what is going on. Or do you have problem only with delayed "expunge" ? Vadim. On 2015-09-24 21:04, Luis wrote: Hi Thank you for your answer. I am using CL 4.5.2 with KVM in Raid 5, after a month the space was not freed up, previously i changes the expunge to 100 - FROM: Vadim Kimlaychuk TO: Luis CC: users@cloudstack.apache.org SENT: Thursday, September 24, 2015 1:33 PM SUBJECT: Re: Expunge Hello Luis, If I remember correctly - you don't get it freed immediately. There is some background process that cleans up. You can probably get better response if write down what version of CS, hypervisor and storage type are you using. Regards, Vadim On 2015-09-24 14:25, Luis wrote: Hi I notice that when I Expunge VM the hard disk space is not returned, I still have the same use, I had to deleted manually from the raid, is this a bug or I am missing a comfiguration?
