cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Angus <>
Subject RE: Troubleshooting the Exception "Unable to start VM instance"
Date Mon, 29 Apr 2019 13:19:30 GMT
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 as you can't
add attachments on the mailing lists.

Amadeus House, Floral Street, London  WC2E 9DPUK

-----Original Message-----
From: <> 
Sent: 29 April 2019 14:00
Subject: AW: Troubleshooting the Exception "Unable to start VM instance"

Hi, Rakesh,


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

kind regards

Von: Rakesh Venkatesh []
Gesendet: Montag, 29. April 2019 13:17
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 <> 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?
> Unable to start VM 
> instance
>         at
>         at sun.reflect.GeneratedMethodAccessor433.invoke(Unknown Source)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
>         at java.lang.reflect.Method.invoke(
>         at
>         at
>         at
>         at
>         at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$
>         at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$
>         at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(
>         at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(
>         at
>         at
>         at
> java.util.concurrent.Executors$
>         at
>         at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at
> java.util.concurrent.ThreadPoolExecutor$
>         at
> kind regards
> Peter

Thanks and regards
Rakesh venkatesh
View raw message