Hi Peter, +1 to Paul's comment. We need full logs to get an accurate assessment.
Also, while you are at it could you check if your hosts and agents are up and running in infra tab? Regards, Anurag On Mon, Apr 29, 2019 at 6:58 PM Paul Angus <paul.an...@shapeblue.com> wrote: > Hi Peter, > > We'd be able to help best if you post a whole unedited chunk of the > management log from the time you attempt to start this VM. You need to use > something like pastebin.com as you can't add attachments on the mailing > lists. > > paul.an...@shapeblue.com > www.shapeblue.com > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > > -----Original Message----- > From: peter.murysh...@zv.fraunhofer.de <peter.murysh...@zv.fraunhofer.de> > Sent: 29 April 2019 14:00 > To: users@cloudstack.apache.org > Subject: AW: Troubleshooting the Exception "Unable to start VM instance" > > Hi, Rakesh, > > thanks! > > After further digging the logs so far I can find: > > Destroying vm VM[User|i-291-77209-VM] as it failed to create on Host with > Id:null VM state transitted from :Stopped to Error with event: > OperationFailedToErrorvm's original host id: null new host id: null host id > before state transition: null > > Additionally, via the log ID I've found an error which contains some > base64 encoding but does not decode well i.e. base64 exits with an error > and outputs something lengthy (2972 chars) looking like a Java stack trace > but with random binary characters. > > Error: [o.a.c.f.j.i.AsyncJobManagerImpl] > (Work-Job-Executor-92:ctx-0c7bb167 job-1027206/job-1027210 ctx-74dde55e) > (logid:2477aa66) Complete async job-1027210, jobStatus: FAILED, resultCode: > 0, result: rO0ABXNyAC9jb20u..... > > What is readable in this "base64" output is (special characters replaced > with hyphen or new line): > > com.cloud.utils.exception.CloudRuntimeExceptionVMOI > csErrorCodexr-java.lang.RuntimeException-detailMessaget > Ljava/lang/String;[ > xr-java.lang.Throwable-Lcauset-Ljava/lang/Throwable;L > stackTracet-[Ljava/lang/StackTraceElement; > L-suppressedExceptionst-Ljava/util/Lis > > kind regards > Peter > > > ________________________________________ > Von: Rakesh Venkatesh [www.rakeshv....@gmail.com] > Gesendet: Montag, 29. April 2019 13:17 > An: users@cloudstack.apache.org > Betreff: Re: Troubleshooting the Exception "Unable to start VM instance" > > Hello Peter > > If you dig into logs a little bit more, you can see the actual reason for > the error. The usual errors are insufficient server capacity exception like > not enough cpu, memory, ip address or mismatch between template tag and > host tag or some other mismatch in the tags. These are the common errors I > have seen. > Search for "startVirtualMachine" api and trace its jobid which is usually > like "context-<some number>" and look at the logs > > On Mon, Apr 29, 2019 at 12:58 PM <peter.murysh...@zv.fraunhofer.de> wrote: > > > Hi, all, > > > > sometimes the system can't start a VM instance (a 530 error). > > In the logs there is the following trace - how to troubleshoot it and > > understand which circumstances lead to it? > > > > > > com.cloud.utils.exception.CloudRuntimeException: Unable to start VM > > instance > > at > > > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4889) > > at sun.reflect.GeneratedMethodAccessor433.invoke(Unknown Source) > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:498) > > at > > > com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) > > at > > > com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5047) > > at > > com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) > > at > > > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:615) > > 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:563) > > at > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > > at > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > > at > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > > at java.lang.Thread.run(Thread.java:748) > > > > kind regards > > Peter > > > > > > -- > Thanks and regards > Rakesh venkatesh >
