cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ajit Singh <ajitsing...@gmail.com>
Subject Re: InsufficientServerCapacity - system vm's
Date Thu, 23 Jul 2020 09:23:17 GMT
Hi Vivek

Kindly find below the upper part of logs of the error shared before.

2020-07-23 12:54:51,627 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-74:ctx-4483f427 job-37133/job-38762 ctx-2d729b09) VM
state transitted from :Starting to Stopped with event: OperationFailedvm's
original host id: null new host id: null host id before state transition:
null
2020-07-23 12:54:51,629 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-74:ctx-4483f427 job-37133/job-38762 ctx-2d729b09)
Invocation exception, caused by:
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[ConsoleProxy|v-1492-VM]Scope=interface
com.cloud.dc.DataCenter; id=16
2020-07-23 12:54:51,629 INFO  [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-74:ctx-4483f427 job-37133/job-38762 ctx-2d729b09)
Rethrow exception com.cloud.exception.InsufficientServerCapacityException:
Unable to create a deployment for VM[ConsoleProxy|v-1492-VM]Scope=interface
com.cloud.dc.DataCenter; id=16
2020-07-23 12:54:51,629 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-74:ctx-4483f427 job-37133/job-38762) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 1492, job origin: 37133
2020-07-23 12:54:51,629 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-74:ctx-4483f427 job-37133/job-38762) Unable to complete
AsyncJobVO {id:38762, userId: 1, accountId: 1, instanceType: null,
instanceId:null, cmd: com.cloud.vm.VmWorkStart, cmdInfo:
rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oA

BGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0AB

BMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0

d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAAAAAAAAAABAAAAAAAAAAEAAAAAAAAF1HQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcG

 wAAAAAAAAAAHBwcHBwcHBwcHA, cmdVersion: 0, status: IN_PROGRESS,
processStatus: 0, resultCode: 0, result: null, initMsid: 271527376523351,
completeMsid: null, lastUpdated: null, lastPolled: null, created: Thu Jul
23 12:54:50 IST 2020}, job origin:37133

Regards
Ajit

On Thu, Jul 23, 2020 at 2:37 PM Vivek Kumar <vivek.kumar@indiqus.com.invalid>
wrote:

> Hello Ajit,
>
> Can you share the upper part of logs from this error. Just check on what
> steps is it failing. Best way to grep the job-id and follow the job id and
> see where it went wrong. I am assuming that you have already registered
> the  VMware system VM templates in your secondary storage which you added
> for VMWare Zone.
>
>
>
> Vivek Kumar
> Manager - Cloud & DevOps
> IndiQus Technologies
> 24*7  O +91 11 4055 1411  |   M +91 7503460090
> www.indiqus.com <http://indiqus.com/>
>
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain information that is confidential
> and/or privileged. If you are not the intended recipient please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result of
> viruses.
>
> > On 23-Jul-2020, at 1:28 PM, Ajit Singh <ajitsingh78@gmail.com> wrote:
> >
> > Hi
> >
> > I have created a new zone in an existing cloud stack by adding VMware and
> > esxi host and it got successfully created with pod and cluster. but
> system
> > vm's (console proxy and storage vm) are not getting created and they are
> > spawning endlessly. From the logs, it says  InsufficientServerCapacity
> but
> > in my host cpu and ram is under utilized.
> >
> >
> > 2020-07-23 12:54:51,698 WARN  [c.c.c.ConsoleProxyManagerImpl]
> > (consoleproxy-1:ctx-c9872458) Exception whil
> >                               e trying to start console proxy
> > com.cloud.exception.InsufficientServerCapacityException: Unable to
> create a
> > deployment for VM[ConsoleProxy
> >                 |v-1492-VM]Scope=interface com.cloud.dc.DataCenter; id=16
> >        at
> >
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
> >        at
> >
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4768)
> >        at sun.reflect.GeneratedMethodAccessor592.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:4930)
> >        at
> > com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> >        at
> >
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImp
> >                                                             l.java:594)
> >        at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:
> >                                                             49)
> >        at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.j
> >                                                             ava:56)
> >        at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManaged
> >
> > Context.java:103)
> >        at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedC
> >
>  ontext.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:54
> >                                                             1)
> >        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)
> > 2020-07-23 12:54:51,699 INFO  [c.c.c.ConsoleProxyManagerImpl]
> > (consoleproxy-1:ctx-c9872458) Unable to star
> >                               t console proxy vm for standby capacity, vm
> > id : 1492, will recycle it and start a new one
> >
> > Regards
> > Ajit
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message