You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "angeline shen (JIRA)" <ji...@apache.org> on 2013/02/23 05:20:14 UTC
[jira] [Created] (CLOUDSTACK-1376) Unable to migrate VM due to
internal error process exited while connecting to monitor:
angeline shen created CLOUDSTACK-1376:
-----------------------------------------
Summary: Unable to migrate VM due to internal error process exited while connecting to monitor:
Key: CLOUDSTACK-1376
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1376
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.1.0
Environment: MS rhel6.3 ASF 4.1 latest build 2/21/2013
host rhel6.3 KVM
Reporter: angeline shen
Priority: Critical
Fix For: 4.1.0
MS rhel6.3 ASF 4.1 latest build 2/21/2013
host rhel6.3 KVM
1. advance zone, 1 KVM hosts. Create VMs on host 1.
2. Add host 2
3. Put host 1 in maintenance mode. Host 1 enters ErrorinMaintenance state instead of
PrepareMaintenance mode
VMs fail to migrate to suitable host
2013-02-22 19:53:53,080 WARN [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-0:work-8) Unable to migrate vm from 1
2013-02-22 19:53:53,081 DEBUG [cloud.resource.ResourceManagerImpl] (HA-Worker-0:work-8) No next resource state for host 1 while current state is ErrorInMaintenance with event UnableToMigrate
com.cloud.utils.fsm.NoTransitionException: No next resource state found for current state =ErrorInMaintenance event =UnableToMigrate
at com.cloud.resource.ResourceManagerImpl.resourceStateTransitTo(ResourceManagerImpl.java:1283)
at com.cloud.resource.ResourceManagerImpl.maintenanceFailed(ResourceManagerImpl.java:2533)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
at com.cloud.ha.HighAvailabilityManagerImpl.migrate(HighAvailabilityManagerImpl.java:562)
at com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:815)
2013-02-22 19:53:53,081 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-0:work-8) Completed HAWork[8-Migration-38-Running-Migrating]
2013-02-22 19:53:53,116 DEBUG [agent.transport.Request] (AgentManager-Handler-11:null) Seq 4-507510810: Processing: { Ans: , MgmtId: 6655051826959, via: 4, Ver: v1, Flags: 110, [{"StopAnswer":{"vncPort":0,"result":true,"wai
t":0}}] }
2013-02-22 19:53:53,116 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-11:null) Seq 4-507510810: Unable to find listener.
2013-02-22 19:53:53,117 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-11:null) Seq 4-507510810: No more comma
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira