com.xerox.amazonws.ec2.EC2Exception: Client error : The requested instance type's architecture (x86_64) does not match the architecture in the manifest for ami-5926cb30 (i386)

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Atlassian JIRA by Diane Yu, 1 year ago
Client error : The requested instance type's architecture (x86_64) does not match the architecture in the manifest for ami-5926cb30 (i386)
via Atlassian JIRA by Diane Yu, 1 year ago
Client error : The requested instance type's architecture (x86_64) does not match the architecture in the manifest for ami-5926cb30 (i386)
via atlassian.com by Unknown author, 1 year ago
Client error : The requested Availability Zone is currently constrained and we are no longer accepting new customer reque sts for t1/m1/c1/m2 instance types. Please retry your request by not specifying an Availability Zone or choosing us-east-1b, us-east-1d, us-east-1e.
via Google Groups by SANDER SMITH, 1 year ago
Client error : The parameter LaunchSpecification is not recognized
via Atlassian JIRA by Krystian Nowak, 1 year ago
Client error : The volume 'vol-b48c62dd' is not 'attached'.
via Atlassian JIRA by Krystian Nowak, 1 year ago
Client error : The volume 'vol-b48c62dd' is not 'attached'.
com.xerox.amazonws.ec2.EC2Exception: Client error : The requested instance type's architecture (x86_64) does not match the architecture in the manifest for ami-5926cb30 (i386)
at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:1680)
at com.xerox.amazonws.ec2.Jec2.runInstances(Jec2.java:563)
at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:365)
at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:25)
at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:117)
at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:98)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:172)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.