You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users-cn@cloudstack.apache.org by 淡看浮华 <36...@qq.com> on 2014/03/19 12:27:11 UTC
执行cloud-setup-agent,报不能启动agent错误，请大家帮忙分析分析，谢谢
我是在vmware workstation8中的一台虚拟机里同时安装了cloudstack4.0.2的管理节点和agent,操作系统为ubuntu12.04
在添加域的过程中,添加主机这一步始终失败,agent.log日志里报错，说不能启动agent
执行cloud-setup-agent,也是报错说不能启动agent
**************************************************************
具体agent.log日志内容如下：
***************************************************************
2014-03-19 04:07:51,649 ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent:
com.cloud.utils.exception.CloudRuntimeException: Cannot recv data: Connection reset by peer
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:654)
at com.cloud.agent.Agent.<init>(Agent.java:163)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:559)
at com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:514)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:431)
at com.cloud.agent.AgentShell.start(AgentShell.java:589)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
2014-03-19 04:08:22,946 INFO [utils.component.ComponentLocator] (main:null) Unable to find components.xml
2014-03-19 04:08:22,949 INFO [utils.component.ComponentLocator] (main:null) Skipping configuration using components.xml
2014-03-19 04:08:22,949 INFO [cloud.agent.AgentShell] (main:null) Implementation Version is 4.0.2.20130501180711
2014-03-19 04:08:22,950 INFO [cloud.agent.AgentShell] (main:null) agent.properties found at /etc/cloud/agent/agent.properties
2014-03-19 04:08:22,952 INFO [cloud.agent.AgentShell] (main:null) Defaulting to using properties file for storage
2014-03-19 04:08:22,958 INFO [cloud.agent.AgentShell] (main:null) Defaulting to the constant time backoff algorithm
2014-03-19 04:08:23,076 INFO [cloud.agent.Agent] (main:null) id is
2014-03-19 04:08:23,164 INFO [resource.virtualnetwork.VirtualRoutingResource] (main:null) VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
*************************************************************************************
setup.log日志内容如下：
*************************************************************************************
DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}'
DEBUG:root:execute:ifconfig cloudbr0
DEBUG:root:Found default network device:cloudbr0
DEBUG:root:execute:uname -r
DEBUG:root:execute:uname -m
DEBUG:root:execute:hostname -f
DEBUG:root:execute:kvm-ok
DEBUG:root:execute:service apparmor status
DEBUG:root:execute:apparmor_status |grep libvirt
DEBUG:root:Failed to execute:
DEBUG:root:execute:sudo /usr/sbin/service network-manager status
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}'
DEBUG:root:execute:ifconfig cloudbr0
DEBUG:root:Found default network device:cloudbr0
DEBUG:root:execute:ifconfig eth0
DEBUG:root:cloudbr0:eth0 already configured
DEBUG:root:execute:sudo /usr/sbin/service network-manager status
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:sudo /usr/sbin/service network-manager stop
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:sudo /usr/sbin/service network-manager status
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:sudo /usr/sbin/service network-manager stop
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:sudo update-rc.d -f network-manager remove
DEBUG:root:execute:ifup cloudbr0
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin stop
DEBUG:root:execute:sudo update-rc.d -f libvirt-bin remove
DEBUG:root:execute:sudo update-rc.d -f libvirt-bin defaults
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin start
DEBUG:root:execute:ufw allow 22
DEBUG:root:execute:ufw allow 1798
DEBUG:root:execute:ufw allow 16509
DEBUG:root:execute:ufw allow proto tcp from any to any port 5900:6100
DEBUG:root:execute:ufw allow proto tcp from any to any port 49152:49216
DEBUG:root:execute:sudo /usr/sbin/service ufw status
DEBUG:root:execute:sudo /usr/sbin/service ufw stop
DEBUG:root:execute:sudo /usr/sbin/service ufw status
DEBUG:root:execute:sudo /usr/sbin/service ufw start
DEBUG:root:execute:sudo /usr/sbin/service cloud-agent status
DEBUG:root:Failed to execute: * could not access PID file for cloud-agent
DEBUG:root:execute:sudo /usr/sbin/service cloud-agent stop
DEBUG:root:execute:sleep 30
DEBUG:root:execute:sudo update-rc.d -f cloud-agent remove
DEBUG:root:execute:sudo update-rc.d -f cloud-agent defaults
DEBUG:root:execute:sudo /usr/sbin/service cloud-agent status
DEBUG:root:Failed to execute: * could not access PID file for cloud-agent
DEBUG:root:execute:sudo /usr/sbin/service cloud-agent start
Re: 答复: 取消维护ISCSI存储提示错误
Posted by ganglin_lan <ga...@tcloudcomputing.com>.
试试 xe pbd-plug uuid=4e2cc197-fdec-5688-131a-746e0fc16262 ?
ganglin_lan
发件人： 许叁征
发送时间： 2014-03-21 19:50
收件人： users-cn@cloudstack.apache.org; 'ganglin_lan'
主题： 答复: 答复: 取消维护ISCSI存储提示错误
是的，存储出问题， 不过存储问题已解决。之前把xenserver 的ISCSI不小心给forget掉了，现在找不到这个磁盘，重新通过XENserver面板添加的ISCSI可以显示name 35510305-6f6f-3ca0-90ae-797b47b29ae3
但是UUID却不能变成原来XENserver“4e2cc197-fdec-5688-131a-746e0fc16262”
尝试以下办法 添加 提示出错，有什么办法 可以恢复cloudstack正常连接xenserver上的iscsi, ？让原来的使用iscsi存储启动起来。
[root@xen122 ~]# xe pbd-create sr-uuid=4e2cc197-fdec-5688-131a-746e0fc16262 host-uuid=ea339c35-2574-4813-b873-35c24f47e5e1 device-config:target=192.168.0.28 device-config:targetIQN=iqn.2014-01.net.xsz:iscsi.disk0-target device-config:SCSIlid=35510305-6f6f-3ca0-90ae-797b47b29ae3
The uuid you supplied was invalid.
type: SR
uuid: 4e2cc197-fdec-5688-131a-746e0fc16262
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3281-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3281-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 ganglin_lan
发送时间: 2014年3月21日星期五 16:46
收件人: users-cn
主题: Re: 答复: 取消维护ISCSI存储提示错误
这应该不是cloudstack的问题，存储出问题了
ganglin_lan
发件人： 许叁征
发送时间： 2014-03-21 16:27
收件人： users-cn@cloudstack.apache.org
主题： 答复: 取消维护ISCSI存储提示错误
贴一下详细的日志，供大家分析下
Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3142)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3254)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Catch Exception: class com.cloud.utils.exception.CloudRuntimeException due to com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to start i-2-64691-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,991 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,010 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,028 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,090 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to cleanup VIF
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VIF.unplug(VIF.java:804)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1100)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,096 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-193:null) The VM is in stopped state, detected problem during startup : i-2-64691-VM
2014-03-21 16:25:13,096 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-193:null) Seq 66-624099358: Response Received:
2014-03-21 16:25:13,097 DEBUG [agent.transport.Request] (DirectAgent-193:null) Seq 66-624099358: Processing: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, [{"StartAnswer":{"vm":{"id":64691,"name":"i-2-64691-VM","bootloader":"PyGrub","type":"User","cpus":1,"speed":2000,"minRam":2147483648,"maxRam":2147483648,"arch":"x86_64","os":"CentOS 5.5 (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"vncPassword":"42972cbfa2e06a4f","params":{},"uuid":"d3c70166-80de-4323-a079-ee0c360616aa","disks":[{"id":64737,"name":"ROOT-64691","mountPoint":"/iqn.2014-03.net.cloudstack130:iscsi.disk0/1","path":"800f525f-e3ee-4afc-a3c0-346794808201","size":21474836480,"type":"ROOT","storagePoolType":"IscsiLUN","storagePoolUuid":"35510305-6f6f-3ca0-90ae-797b47b29ae3","deviceId":0},{"id":64802,"name":"DATA-64691","mountPoint":"/iqn.2014-03.net.cloudstack130:iscsi.disk0/1","path":"c8ebf2d7-8c6e-4224-9ada-d9b08b3ae00e","size":53687091200,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"35510305-6f6f-3ca0-90ae-797b47b29ae3","deviceId":1},{"id":64691,"name":"centos5.81","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"1283c8ee-f3e6-4b68-9d30-62eb47fdf741","ip":"172.16.0.172","netmask":"255.255.255.0","gateway":"172.16.0.254","mac":"06:aa:e6:00:00:29","dns1":"218.85.157.99","dns2":"218.85.157.99","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://untagged","isolationUri":"ec2://untagged","isSecurityGroupEnabled":false}]},"result":false,"details":"Unable to start i-2-64691-VM due to ","wait":0}}] }
2014-03-21 16:25:13,097 DEBUG [agent.manager.AgentAttache] (DirectAgent-193:null) Seq 66-624099358: No more commands found
2014-03-21 16:25:13,097 DEBUG [agent.manager.AgentAttache] (DirectAgent-193:null) Seq 66-624099358: No more commands found
2014-03-21 16:25:13,097 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099358: Received: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, { StartAnswer } }
2014-03-21 16:25:13,157 INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Unable to start VM on Host[-66-Routing] due to Unable to start i-2-64691-VM due to
2014-03-21 16:25:13,224 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Cleaning up resources for the vm VM[User|test6] in Starting state
2014-03-21 16:25:13,225 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Sending { Cmd , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-64691-VM","wait":0}}] }
2014-03-21 16:25:13,226 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Executing: { Cmd , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-64691-VM","wait":0}}] }
2014-03-21 16:25:13,226 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-192:null) Seq 66-624099359: Executing request
2014-03-21 16:25:13,316 INFO [xen.resource.CitrixResourceBase] (DirectAgent-192:null) VM does not exist on XenServerea339c35-2574-4813-b873-35c24f47e5e1
2014-03-21 16:25:13,316 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-192:null) Seq 66-624099359: Response Received:
2014-03-21 16:25:13,316 DEBUG [agent.transport.Request] (DirectAgent-192:null) Seq 66-624099359: Processing: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, [{"StopAnswer":{"vncPort":0,"result":true,"details":"VM does not exist","wait":0}}] }
2014-03-21 16:25:13,316 DEBUG [agent.manager.AgentAttache] (DirectAgent-192:null) Seq 66-624099359: No more commands found
2014-03-21 16:25:13,316 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Received: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, { StopAnswer } }
2014-03-21 16:25:13,397 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-10:job-738) Changing active number of nics for network id=204 on -1
2014-03-21 16:25:13,449 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Successfully released network resources for the vm VM[User|test6]
2014-03-21 16:25:13,449 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Successfully cleanued up resources for the vm VM[User|test6] in Starting state
2014-03-21 16:25:13,452 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Root volume is ready, need to place VM in volume's cluster
2014-03-21 16:25:13,453 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Vol[64737|vm=64691|ROOT] is READY, changing deployment plan to use this pool's dcId: 1 , podId: 1 , and clusterId: 20
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) DeploymentPlanner allocation algorithm: random
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:20, requested cpu: 2000, requested ram: 2147483648
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: Yes
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) This VM has last host_id specified, trying to choose the same host: 66
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) The last host of this VM is in avoid set
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Cannot choose the last host to deploy this VM
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Cluster: 20
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Cluster: 20
2014-03-21 16:25:13,459 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking resources in Cluster: 20 under Pod: 1
2014-03-21 16:25:13,459 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling HostAllocators to find suitable hosts
2014-03-21 16:25:13,459 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:20
2014-03-21 16:25:13,460 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-66-Routing]]
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-66-Routing]]
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=2048
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host name: xenserver-ivehudzt, hostId: 66 is in avoid set, skipping this and trying other available hosts
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable hosts found
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable hosts found under this Cluster: 20
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) DeploymentPlanner allocation algorithm: random
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:null, requested cpu: 2000, requested ram: 2147483648
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: No
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: No
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) This VM has last host_id specified, trying to choose the same host: 66
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) The last host of this VM is in avoid set
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Cannot choose the last host to deploy this VM
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Pod: 1
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Pod: 1
2014-03-21 16:25:13,465 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) CPUOverprovisioningFactor considered: 6.0
2014-03-21 16:25:13,466 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Removing from the clusterId list these clusters from avoid set: [20]
2014-03-21 16:25:13,470 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking resources in Cluster: 1 under Pod: 1
2014-03-21 16:25:13,470 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling HostAllocators to find suitable hosts
2014-03-21 16:25:13,470 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1
2014-03-21 16:25:13,471 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-56-Routing]]
2014-03-21 16:25:13,472 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-56-Routing]]
2014-03-21 16:25:13,472 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=2048
2014-03-21 16:25:13,474 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Checking if host: 56 has enough capacity for requested CPU: 2000 and requested RAM: 2147483648 , cpuOverprovisioningFactor: 6.0
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 217536
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Free CPU: 184536 , Requested CPU: 2000
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Free RAM: 6890548352 , Requested RAM: 2147483648
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host has enough CPU and RAM available
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 56, used: 33000, reserved: 0, actual total: 36256, total with overprovisioning: 217536; requested cpu:2000,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 56, used: 17582522368, reserved: 0, total: 24473070720; requested mem: 2147483648,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-21 16:25:13,476 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found a suitable host, adding to list: 56
2014-03-21 16:25:13,476 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking suitable pools for volume (Id, Type): (64737,ROOT)
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) We need to allocate new storagepool for this volume
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling StoragePoolAllocators to find suitable pools
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling StoragePoolAllocators to find suitable pools
2014-03-21 16:25:13,477 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-738) Looking for pools in dc: 1 pod:1 cluster:1 having tags:[iscsi]
2014-03-21 16:25:13,478 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-738) No storage pools available for shared volume allocation, returning
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable pools found for volume: Vol[64737|vm=64691|ROOT] under cluster: 1
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable pools found
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable storagePools found under this Cluster: 1
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-21 16:25:13,599 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: 66 new host id: null host id before state transition: 66
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 217536
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) release cpu from host: 66, old used: 4000,reserved: 14000, actual total: 36256, total with overprovisioning: 217536; new used: 2000,reserved:14000; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) release mem from host: 66, old used: 4294967296,reserved: 16106127360, total: 24472994112; new used: 2147483648,reserved:16106127360; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,691 WARN [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-738) There was an error starting the user vm id: 64691 on storage pool, cannot complete primary storage maintenance
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|test6]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:597)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2815)
at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,742 ERROR [cloud.api.ApiDispatcher] (Job-Executor-10:job-738) Exception while executing CancelPrimaryStorageMaintenanceCmd:
java.lang.ClassCastException: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2848)
at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:14,546 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-3:null) Async job-738 completed
2014-03-21 16:25:15,133 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-7:null) Async job-731 completed
2014-03-21 16:25:15,995 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2014-03-21 16:25:16,097 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy
2014-03-21 16:25:16,503 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2014-03-21 08:25:16 GMT
^C
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3277-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3277-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 许叁征
发送时间: 2014年3月21日星期五 14:40
收件人: users-cn@cloudstack.apache.org
主题: 答复: 取消维护ISCSI存储提示错误
部署了两个群集，单独的节点，单独的存储，
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 linuxbqj@gmail.com
发送时间: 2014年3月20日星期四 17:36
收件人: users-cn@cloudstack.apache.org
主题: Re: 取消维护ISCSI存储提示错误
你们是部署了几个存储呢？如果是多个存储，并且主机设置了HA 是可以实现迁移的
在 2014年3月20日 下午4:55，hongweinn@gmail.com <ho...@gmail.com> 写道：
>
>
>
>
>
>
> 我也遇见了同样的问题。XENSERVER+FC-SAN模拟FC宕机后怎么恢复。刚开始的时候系统VM启动不了，然后自动创建也失败，最后把FC删了重新添加了一遍。系统VM创建成功。然后两台XENserver中的一台无法创建虚拟机，准备把FC存储再次删除，但是设置成维护模式就变成两个按钮了。一个是启动维护，一个是取消维护。点取消维护就报同样的错误。
> 已经一下午了，仍然没搞定，如果有消息，互通解决方案
>
>
> hongweinn@gmail.com
> ?发件人：?许叁征发送时间：?2014-03-20?15:04收件人：?users-cn@cloudstack.apache.org主题：?取消维护ISCSI存储提示错误?
> HI ALL
> 今天发现ISCSI无法启动虚拟机，在平台上将ISCSI存储设置成维护 状态 ，然后再取
> 消维护，提示以下错误 ，看看这个是怎么问题？一直是这样的，先谢谢了。
> ?
> com.cloud.utils.exception.ExecutionException cannot be cast to
> com.cloud.exception.ResourceUnavailableException
>
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
答复: 答复: 取消维护ISCSI存储提示错误
Posted by 许叁征 <xu...@chinanetcenter.com>.
是的，存储出问题， 不过存储问题已解决。之前把xenserver 的ISCSI不小心给forget掉了，现在找不到这个磁盘，重新通过XENserver面板添加的ISCSI可以显示name 35510305-6f6f-3ca0-90ae-797b47b29ae3
但是UUID却不能变成原来XENserver“4e2cc197-fdec-5688-131a-746e0fc16262”
尝试以下办法 添加 提示出错，有什么办法 可以恢复cloudstack正常连接xenserver上的iscsi, ？让原来的使用iscsi存储启动起来。
[root@xen122 ~]# xe pbd-create sr-uuid=4e2cc197-fdec-5688-131a-746e0fc16262 host-uuid=ea339c35-2574-4813-b873-35c24f47e5e1 device-config:target=192.168.0.28 device-config:targetIQN=iqn.2014-01.net.xsz:iscsi.disk0-target device-config:SCSIlid=35510305-6f6f-3ca0-90ae-797b47b29ae3
The uuid you supplied was invalid.
type: SR
uuid: 4e2cc197-fdec-5688-131a-746e0fc16262
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3281-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3281-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 ganglin_lan
发送时间: 2014年3月21日星期五 16:46
收件人: users-cn
主题: Re: 答复: 取消维护ISCSI存储提示错误
这应该不是cloudstack的问题，存储出问题了
ganglin_lan
发件人： 许叁征
发送时间： 2014-03-21 16:27
收件人： users-cn@cloudstack.apache.org
主题： 答复: 取消维护ISCSI存储提示错误
贴一下详细的日志，供大家分析下
Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3142)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3254)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Catch Exception: class com.cloud.utils.exception.CloudRuntimeException due to com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to start i-2-64691-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,991 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,010 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,028 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,090 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to cleanup VIF
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VIF.unplug(VIF.java:804)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1100)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,096 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-193:null) The VM is in stopped state, detected problem during startup : i-2-64691-VM
2014-03-21 16:25:13,096 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-193:null) Seq 66-624099358: Response Received:
2014-03-21 16:25:13,097 DEBUG [agent.transport.Request] (DirectAgent-193:null) Seq 66-624099358: Processing: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, [{"StartAnswer":{"vm":{"id":64691,"name":"i-2-64691-VM","bootloader":"PyGrub","type":"User","cpus":1,"speed":2000,"minRam":2147483648,"maxRam":2147483648,"arch":"x86_64","os":"CentOS 5.5 (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"vncPassword":"42972cbfa2e06a4f","params":{},"uuid":"d3c70166-80de-4323-a079-ee0c360616aa","disks":[{"id":64737,"name":"ROOT-64691","mountPoint":"/iqn.2014-03.net.cloudstack130:iscsi.disk0/1","path":"800f525f-e3ee-4afc-a3c0-346794808201","size":21474836480,"type":"ROOT","storagePoolType":"IscsiLUN","storagePoolUuid":"35510305-6f6f-3ca0-90ae-797b47b29ae3","deviceId":0},{"id":64802,"name":"DATA-64691","mountPoint":"/iqn.2014-03.net.cloudstack130:iscsi.disk0/1","path":"c8ebf2d7-8c6e-4224-9ada-d9b08b3ae00e","size":53687091200,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"35510305-6f6f-3ca0-90ae-797b47b29ae3","deviceId":1},{"id":64691,"name":"centos5.81","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"1283c8ee-f3e6-4b68-9d30-62eb47fdf741","ip":"172.16.0.172","netmask":"255.255.255.0","gateway":"172.16.0.254","mac":"06:aa:e6:00:00:29","dns1":"218.85.157.99","dns2":"218.85.157.99","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://untagged","isolationUri":"ec2://untagged","isSecurityGroupEnabled":false}]},"result":false,"details":"Unable to start i-2-64691-VM due to ","wait":0}}] }
2014-03-21 16:25:13,097 DEBUG [agent.manager.AgentAttache] (DirectAgent-193:null) Seq 66-624099358: No more commands found
2014-03-21 16:25:13,097 DEBUG [agent.manager.AgentAttache] (DirectAgent-193:null) Seq 66-624099358: No more commands found
2014-03-21 16:25:13,097 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099358: Received: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, { StartAnswer } }
2014-03-21 16:25:13,157 INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Unable to start VM on Host[-66-Routing] due to Unable to start i-2-64691-VM due to
2014-03-21 16:25:13,224 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Cleaning up resources for the vm VM[User|test6] in Starting state
2014-03-21 16:25:13,225 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Sending { Cmd , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-64691-VM","wait":0}}] }
2014-03-21 16:25:13,226 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Executing: { Cmd , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-64691-VM","wait":0}}] }
2014-03-21 16:25:13,226 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-192:null) Seq 66-624099359: Executing request
2014-03-21 16:25:13,316 INFO [xen.resource.CitrixResourceBase] (DirectAgent-192:null) VM does not exist on XenServerea339c35-2574-4813-b873-35c24f47e5e1
2014-03-21 16:25:13,316 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-192:null) Seq 66-624099359: Response Received:
2014-03-21 16:25:13,316 DEBUG [agent.transport.Request] (DirectAgent-192:null) Seq 66-624099359: Processing: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, [{"StopAnswer":{"vncPort":0,"result":true,"details":"VM does not exist","wait":0}}] }
2014-03-21 16:25:13,316 DEBUG [agent.manager.AgentAttache] (DirectAgent-192:null) Seq 66-624099359: No more commands found
2014-03-21 16:25:13,316 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Received: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, { StopAnswer } }
2014-03-21 16:25:13,397 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-10:job-738) Changing active number of nics for network id=204 on -1
2014-03-21 16:25:13,449 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Successfully released network resources for the vm VM[User|test6]
2014-03-21 16:25:13,449 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Successfully cleanued up resources for the vm VM[User|test6] in Starting state
2014-03-21 16:25:13,452 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Root volume is ready, need to place VM in volume's cluster
2014-03-21 16:25:13,453 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Vol[64737|vm=64691|ROOT] is READY, changing deployment plan to use this pool's dcId: 1 , podId: 1 , and clusterId: 20
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) DeploymentPlanner allocation algorithm: random
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:20, requested cpu: 2000, requested ram: 2147483648
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: Yes
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) This VM has last host_id specified, trying to choose the same host: 66
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) The last host of this VM is in avoid set
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Cannot choose the last host to deploy this VM
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Cluster: 20
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Cluster: 20
2014-03-21 16:25:13,459 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking resources in Cluster: 20 under Pod: 1
2014-03-21 16:25:13,459 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling HostAllocators to find suitable hosts
2014-03-21 16:25:13,459 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:20
2014-03-21 16:25:13,460 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-66-Routing]]
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-66-Routing]]
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=2048
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host name: xenserver-ivehudzt, hostId: 66 is in avoid set, skipping this and trying other available hosts
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable hosts found
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable hosts found under this Cluster: 20
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) DeploymentPlanner allocation algorithm: random
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:null, requested cpu: 2000, requested ram: 2147483648
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: No
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: No
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) This VM has last host_id specified, trying to choose the same host: 66
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) The last host of this VM is in avoid set
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Cannot choose the last host to deploy this VM
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Pod: 1
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Pod: 1
2014-03-21 16:25:13,465 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) CPUOverprovisioningFactor considered: 6.0
2014-03-21 16:25:13,466 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Removing from the clusterId list these clusters from avoid set: [20]
2014-03-21 16:25:13,470 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking resources in Cluster: 1 under Pod: 1
2014-03-21 16:25:13,470 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling HostAllocators to find suitable hosts
2014-03-21 16:25:13,470 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1
2014-03-21 16:25:13,471 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-56-Routing]]
2014-03-21 16:25:13,472 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-56-Routing]]
2014-03-21 16:25:13,472 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=2048
2014-03-21 16:25:13,474 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Checking if host: 56 has enough capacity for requested CPU: 2000 and requested RAM: 2147483648 , cpuOverprovisioningFactor: 6.0
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 217536
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Free CPU: 184536 , Requested CPU: 2000
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Free RAM: 6890548352 , Requested RAM: 2147483648
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host has enough CPU and RAM available
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 56, used: 33000, reserved: 0, actual total: 36256, total with overprovisioning: 217536; requested cpu:2000,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 56, used: 17582522368, reserved: 0, total: 24473070720; requested mem: 2147483648,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-21 16:25:13,476 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found a suitable host, adding to list: 56
2014-03-21 16:25:13,476 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking suitable pools for volume (Id, Type): (64737,ROOT)
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) We need to allocate new storagepool for this volume
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling StoragePoolAllocators to find suitable pools
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling StoragePoolAllocators to find suitable pools
2014-03-21 16:25:13,477 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-738) Looking for pools in dc: 1 pod:1 cluster:1 having tags:[iscsi]
2014-03-21 16:25:13,478 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-738) No storage pools available for shared volume allocation, returning
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable pools found for volume: Vol[64737|vm=64691|ROOT] under cluster: 1
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable pools found
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable storagePools found under this Cluster: 1
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-21 16:25:13,599 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: 66 new host id: null host id before state transition: 66
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 217536
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) release cpu from host: 66, old used: 4000,reserved: 14000, actual total: 36256, total with overprovisioning: 217536; new used: 2000,reserved:14000; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) release mem from host: 66, old used: 4294967296,reserved: 16106127360, total: 24472994112; new used: 2147483648,reserved:16106127360; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,691 WARN [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-738) There was an error starting the user vm id: 64691 on storage pool, cannot complete primary storage maintenance
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|test6]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:597)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2815)
at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,742 ERROR [cloud.api.ApiDispatcher] (Job-Executor-10:job-738) Exception while executing CancelPrimaryStorageMaintenanceCmd:
java.lang.ClassCastException: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2848)
at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:14,546 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-3:null) Async job-738 completed
2014-03-21 16:25:15,133 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-7:null) Async job-731 completed
2014-03-21 16:25:15,995 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2014-03-21 16:25:16,097 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy
2014-03-21 16:25:16,503 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2014-03-21 08:25:16 GMT
^C
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3277-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3277-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 许叁征
发送时间: 2014年3月21日星期五 14:40
收件人: users-cn@cloudstack.apache.org
主题: 答复: 取消维护ISCSI存储提示错误
部署了两个群集，单独的节点，单独的存储，
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 linuxbqj@gmail.com
发送时间: 2014年3月20日星期四 17:36
收件人: users-cn@cloudstack.apache.org
主题: Re: 取消维护ISCSI存储提示错误
你们是部署了几个存储呢？如果是多个存储，并且主机设置了HA 是可以实现迁移的
在 2014年3月20日 下午4:55，hongweinn@gmail.com <ho...@gmail.com> 写道：
>
>
>
>
>
>
> 我也遇见了同样的问题。XENSERVER+FC-SAN模拟FC宕机后怎么恢复。刚开始的时候系统VM启动不了，然后自动创建也失败，最后把FC删了重新添加了一遍。系统VM创建成功。然后两台XENserver中的一台无法创建虚拟机，准备把FC存储再次删除，但是设置成维护模式就变成两个按钮了。一个是启动维护，一个是取消维护。点取消维护就报同样的错误。
> 已经一下午了，仍然没搞定，如果有消息，互通解决方案
>
>
> hongweinn@gmail.com
> ?发件人：?许叁征发送时间：?2014-03-20?15:04收件人：?users-cn@cloudstack.apache.org主题：?取消维护ISCSI存储提示错误?
> HI ALL
> 今天发现ISCSI无法启动虚拟机，在平台上将ISCSI存储设置成维护 状态 ，然后再取
> 消维护，提示以下错误 ，看看这个是怎么问题？一直是这样的，先谢谢了。
> ?
> com.cloud.utils.exception.ExecutionException cannot be cast to
> com.cloud.exception.ResourceUnavailableException
>
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
Re: 答复: 取消维护ISCSI存储提示错误
Posted by ganglin_lan <ga...@tcloudcomputing.com>.
这应该不是cloudstack的问题，存储出问题了
ganglin_lan
发件人： 许叁征
发送时间： 2014-03-21 16:27
收件人： users-cn@cloudstack.apache.org
主题： 答复: 取消维护ISCSI存储提示错误
贴一下详细的日志，供大家分析下
Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3142)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3254)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Catch Exception: class com.cloud.utils.exception.CloudRuntimeException due to com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to start i-2-64691-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,991 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,010 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,028 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,090 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to cleanup VIF
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VIF.unplug(VIF.java:804)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1100)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,096 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-193:null) The VM is in stopped state, detected problem during startup : i-2-64691-VM
2014-03-21 16:25:13,096 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-193:null) Seq 66-624099358: Response Received:
2014-03-21 16:25:13,097 DEBUG [agent.transport.Request] (DirectAgent-193:null) Seq 66-624099358: Processing: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, [{"StartAnswer":{"vm":{"id":64691,"name":"i-2-64691-VM","bootloader":"PyGrub","type":"User","cpus":1,"speed":2000,"minRam":2147483648,"maxRam":2147483648,"arch":"x86_64","os":"CentOS 5.5 (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"vncPassword":"42972cbfa2e06a4f","params":{},"uuid":"d3c70166-80de-4323-a079-ee0c360616aa","disks":[{"id":64737,"name":"ROOT-64691","mountPoint":"/iqn.2014-03.net.cloudstack130:iscsi.disk0/1","path":"800f525f-e3ee-4afc-a3c0-346794808201","size":21474836480,"type":"ROOT","storagePoolType":"IscsiLUN","storagePoolUuid":"35510305-6f6f-3ca0-90ae-797b47b29ae3","deviceId":0},{"id":64802,"name":"DATA-64691","mountPoint":"/iqn.2014-03.net.cloudstack130:iscsi.disk0/1","path":"c8ebf2d7-8c6e-4224-9ada-d9b08b3ae00e","size":53687091200,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"35510305-6f6f-3ca0-90ae-797b47b29ae3","deviceId":1},{"id":64691,"name":"centos5.81","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"1283c8ee-f3e6-4b68-9d30-62eb47fdf741","ip":"172.16.0.172","netmask":"255.255.255.0","gateway":"172.16.0.254","mac":"06:aa:e6:00:00:29","dns1":"218.85.157.99","dns2":"218.85.157.99","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://untagged","isolationUri":"ec2://untagged","isSecurityGroupEnabled":false}]},"result":false,"details":"Unable to start i-2-64691-VM due to ","wait":0}}] }
2014-03-21 16:25:13,097 DEBUG [agent.manager.AgentAttache] (DirectAgent-193:null) Seq 66-624099358: No more commands found
2014-03-21 16:25:13,097 DEBUG [agent.manager.AgentAttache] (DirectAgent-193:null) Seq 66-624099358: No more commands found
2014-03-21 16:25:13,097 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099358: Received: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, { StartAnswer } }
2014-03-21 16:25:13,157 INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Unable to start VM on Host[-66-Routing] due to Unable to start i-2-64691-VM due to
2014-03-21 16:25:13,224 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Cleaning up resources for the vm VM[User|test6] in Starting state
2014-03-21 16:25:13,225 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Sending { Cmd , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-64691-VM","wait":0}}] }
2014-03-21 16:25:13,226 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Executing: { Cmd , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-64691-VM","wait":0}}] }
2014-03-21 16:25:13,226 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-192:null) Seq 66-624099359: Executing request
2014-03-21 16:25:13,316 INFO [xen.resource.CitrixResourceBase] (DirectAgent-192:null) VM does not exist on XenServerea339c35-2574-4813-b873-35c24f47e5e1
2014-03-21 16:25:13,316 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-192:null) Seq 66-624099359: Response Received:
2014-03-21 16:25:13,316 DEBUG [agent.transport.Request] (DirectAgent-192:null) Seq 66-624099359: Processing: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, [{"StopAnswer":{"vncPort":0,"result":true,"details":"VM does not exist","wait":0}}] }
2014-03-21 16:25:13,316 DEBUG [agent.manager.AgentAttache] (DirectAgent-192:null) Seq 66-624099359: No more commands found
2014-03-21 16:25:13,316 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Received: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, { StopAnswer } }
2014-03-21 16:25:13,397 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-10:job-738) Changing active number of nics for network id=204 on -1
2014-03-21 16:25:13,449 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Successfully released network resources for the vm VM[User|test6]
2014-03-21 16:25:13,449 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Successfully cleanued up resources for the vm VM[User|test6] in Starting state
2014-03-21 16:25:13,452 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Root volume is ready, need to place VM in volume's cluster
2014-03-21 16:25:13,453 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Vol[64737|vm=64691|ROOT] is READY, changing deployment plan to use this pool's dcId: 1 , podId: 1 , and clusterId: 20
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) DeploymentPlanner allocation algorithm: random
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:20, requested cpu: 2000, requested ram: 2147483648
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: Yes
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) This VM has last host_id specified, trying to choose the same host: 66
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) The last host of this VM is in avoid set
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Cannot choose the last host to deploy this VM
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Cluster: 20
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Cluster: 20
2014-03-21 16:25:13,459 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking resources in Cluster: 20 under Pod: 1
2014-03-21 16:25:13,459 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling HostAllocators to find suitable hosts
2014-03-21 16:25:13,459 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:20
2014-03-21 16:25:13,460 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-66-Routing]]
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-66-Routing]]
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=2048
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host name: xenserver-ivehudzt, hostId: 66 is in avoid set, skipping this and trying other available hosts
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable hosts found
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable hosts found under this Cluster: 20
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) DeploymentPlanner allocation algorithm: random
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:null, requested cpu: 2000, requested ram: 2147483648
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: No
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: No
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) This VM has last host_id specified, trying to choose the same host: 66
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) The last host of this VM is in avoid set
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Cannot choose the last host to deploy this VM
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Pod: 1
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Pod: 1
2014-03-21 16:25:13,465 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) CPUOverprovisioningFactor considered: 6.0
2014-03-21 16:25:13,466 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Removing from the clusterId list these clusters from avoid set: [20]
2014-03-21 16:25:13,470 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking resources in Cluster: 1 under Pod: 1
2014-03-21 16:25:13,470 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling HostAllocators to find suitable hosts
2014-03-21 16:25:13,470 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1
2014-03-21 16:25:13,471 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-56-Routing]]
2014-03-21 16:25:13,472 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-56-Routing]]
2014-03-21 16:25:13,472 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=2048
2014-03-21 16:25:13,474 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Checking if host: 56 has enough capacity for requested CPU: 2000 and requested RAM: 2147483648 , cpuOverprovisioningFactor: 6.0
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 217536
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Free CPU: 184536 , Requested CPU: 2000
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Free RAM: 6890548352 , Requested RAM: 2147483648
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host has enough CPU and RAM available
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 56, used: 33000, reserved: 0, actual total: 36256, total with overprovisioning: 217536; requested cpu:2000,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 56, used: 17582522368, reserved: 0, total: 24473070720; requested mem: 2147483648,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-21 16:25:13,476 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found a suitable host, adding to list: 56
2014-03-21 16:25:13,476 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking suitable pools for volume (Id, Type): (64737,ROOT)
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) We need to allocate new storagepool for this volume
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling StoragePoolAllocators to find suitable pools
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling StoragePoolAllocators to find suitable pools
2014-03-21 16:25:13,477 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-738) Looking for pools in dc: 1 pod:1 cluster:1 having tags:[iscsi]
2014-03-21 16:25:13,478 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-738) No storage pools available for shared volume allocation, returning
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable pools found for volume: Vol[64737|vm=64691|ROOT] under cluster: 1
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable pools found
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable storagePools found under this Cluster: 1
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-21 16:25:13,599 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: 66 new host id: null host id before state transition: 66
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 217536
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) release cpu from host: 66, old used: 4000,reserved: 14000, actual total: 36256, total with overprovisioning: 217536; new used: 2000,reserved:14000; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) release mem from host: 66, old used: 4294967296,reserved: 16106127360, total: 24472994112; new used: 2147483648,reserved:16106127360; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,691 WARN [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-738) There was an error starting the user vm id: 64691 on storage pool, cannot complete primary storage maintenance
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|test6]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:597)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2815)
at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,742 ERROR [cloud.api.ApiDispatcher] (Job-Executor-10:job-738) Exception while executing CancelPrimaryStorageMaintenanceCmd:
java.lang.ClassCastException: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2848)
at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:14,546 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-3:null) Async job-738 completed
2014-03-21 16:25:15,133 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-7:null) Async job-731 completed
2014-03-21 16:25:15,995 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2014-03-21 16:25:16,097 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy
2014-03-21 16:25:16,503 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2014-03-21 08:25:16 GMT
^C
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3277-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3277-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 许叁征
发送时间: 2014年3月21日星期五 14:40
收件人: users-cn@cloudstack.apache.org
主题: 答复: 取消维护ISCSI存储提示错误
部署了两个群集，单独的节点，单独的存储，
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 linuxbqj@gmail.com
发送时间: 2014年3月20日星期四 17:36
收件人: users-cn@cloudstack.apache.org
主题: Re: 取消维护ISCSI存储提示错误
你们是部署了几个存储呢？如果是多个存储，并且主机设置了HA 是可以实现迁移的
在 2014年3月20日 下午4:55，hongweinn@gmail.com <ho...@gmail.com> 写道：
>
>
>
>
>
>
> 我也遇见了同样的问题。XENSERVER+FC-SAN模拟FC宕机后怎么恢复。刚开始的时候系统VM启动不了，然后自动创建也失败，最后把FC删了重新添加了一遍。系统VM创建成功。然后两台XENserver中的一台无法创建虚拟机，准备把FC存储再次删除，但是设置成维护模式就变成两个按钮了。一个是启动维护，一个是取消维护。点取消维护就报同样的错误。
> 已经一下午了，仍然没搞定，如果有消息，互通解决方案
>
>
> hongweinn@gmail.com
> ?发件人：?许叁征发送时间：?2014-03-20?15:04收件人：?users-cn@cloudstack.apache.org主题：?取消维护ISCSI存储提示错误?
> HI ALL
> 今天发现ISCSI无法启动虚拟机，在平台上将ISCSI存储设置成维护 状态 ，然后再取
> 消维护，提示以下错误 ，看看这个是怎么问题？一直是这样的，先谢谢了。
> ?
> com.cloud.utils.exception.ExecutionException cannot be cast to
> com.cloud.exception.ResourceUnavailableException
>
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
答复: 取消维护ISCSI存储提示错误
Posted by 许叁征 <xu...@chinanetcenter.com>.
贴一下详细的日志，供大家分析下
Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3142)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3254)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Catch Exception: class com.cloud.utils.exception.CloudRuntimeException due to com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to start i-2-64691-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: <none/>
result:
errorInfo: [VM_REQUIRES_SR, OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,991 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,010 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,028 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to clean up VBD due to
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VBD.unplug(VBD.java:1054)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1092)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,090 WARN [xen.resource.CitrixResourceBase] (DirectAgent-193:null) Unable to cleanup VIF
You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
at com.xensource.xenapi.Types.checkResponse(Types.java:207)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VIF.unplug(VIF.java:804)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.handleVmStartFailure(CitrixResourceBase.java:1100)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1353)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,096 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-193:null) The VM is in stopped state, detected problem during startup : i-2-64691-VM
2014-03-21 16:25:13,096 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-193:null) Seq 66-624099358: Response Received:
2014-03-21 16:25:13,097 DEBUG [agent.transport.Request] (DirectAgent-193:null) Seq 66-624099358: Processing: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, [{"StartAnswer":{"vm":{"id":64691,"name":"i-2-64691-VM","bootloader":"PyGrub","type":"User","cpus":1,"speed":2000,"minRam":2147483648,"maxRam":2147483648,"arch":"x86_64","os":"CentOS 5.5 (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"vncPassword":"42972cbfa2e06a4f","params":{},"uuid":"d3c70166-80de-4323-a079-ee0c360616aa","disks":[{"id":64737,"name":"ROOT-64691","mountPoint":"/iqn.2014-03.net.cloudstack130:iscsi.disk0/1","path":"800f525f-e3ee-4afc-a3c0-346794808201","size":21474836480,"type":"ROOT","storagePoolType":"IscsiLUN","storagePoolUuid":"35510305-6f6f-3ca0-90ae-797b47b29ae3","deviceId":0},{"id":64802,"name":"DATA-64691","mountPoint":"/iqn.2014-03.net.cloudstack130:iscsi.disk0/1","path":"c8ebf2d7-8c6e-4224-9ada-d9b08b3ae00e","size":53687091200,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"35510305-6f6f-3ca0-90ae-797b47b29ae3","deviceId":1},{"id":64691,"name":"centos5.81","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"1283c8ee-f3e6-4b68-9d30-62eb47fdf741","ip":"172.16.0.172","netmask":"255.255.255.0","gateway":"172.16.0.254","mac":"06:aa:e6:00:00:29","dns1":"218.85.157.99","dns2":"218.85.157.99","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://untagged","isolationUri":"ec2://untagged","isSecurityGroupEnabled":false}]},"result":false,"details":"Unable to start i-2-64691-VM due to ","wait":0}}] }
2014-03-21 16:25:13,097 DEBUG [agent.manager.AgentAttache] (DirectAgent-193:null) Seq 66-624099358: No more commands found
2014-03-21 16:25:13,097 DEBUG [agent.manager.AgentAttache] (DirectAgent-193:null) Seq 66-624099358: No more commands found
2014-03-21 16:25:13,097 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099358: Received: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, { StartAnswer } }
2014-03-21 16:25:13,157 INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Unable to start VM on Host[-66-Routing] due to Unable to start i-2-64691-VM due to
2014-03-21 16:25:13,224 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Cleaning up resources for the vm VM[User|test6] in Starting state
2014-03-21 16:25:13,225 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Sending { Cmd , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-64691-VM","wait":0}}] }
2014-03-21 16:25:13,226 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Executing: { Cmd , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-64691-VM","wait":0}}] }
2014-03-21 16:25:13,226 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-192:null) Seq 66-624099359: Executing request
2014-03-21 16:25:13,316 INFO [xen.resource.CitrixResourceBase] (DirectAgent-192:null) VM does not exist on XenServerea339c35-2574-4813-b873-35c24f47e5e1
2014-03-21 16:25:13,316 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-192:null) Seq 66-624099359: Response Received:
2014-03-21 16:25:13,316 DEBUG [agent.transport.Request] (DirectAgent-192:null) Seq 66-624099359: Processing: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, [{"StopAnswer":{"vncPort":0,"result":true,"details":"VM does not exist","wait":0}}] }
2014-03-21 16:25:13,316 DEBUG [agent.manager.AgentAttache] (DirectAgent-192:null) Seq 66-624099359: No more commands found
2014-03-21 16:25:13,316 DEBUG [agent.transport.Request] (Job-Executor-10:job-738) Seq 66-624099359: Received: { Ans: , MgmtId: 690716573693, via: 66, Ver: v1, Flags: 110, { StopAnswer } }
2014-03-21 16:25:13,397 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-10:job-738) Changing active number of nics for network id=204 on -1
2014-03-21 16:25:13,449 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Successfully released network resources for the vm VM[User|test6]
2014-03-21 16:25:13,449 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Successfully cleanued up resources for the vm VM[User|test6] in Starting state
2014-03-21 16:25:13,452 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Root volume is ready, need to place VM in volume's cluster
2014-03-21 16:25:13,453 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-738) Vol[64737|vm=64691|ROOT] is READY, changing deployment plan to use this pool's dcId: 1 , podId: 1 , and clusterId: 20
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) DeploymentPlanner allocation algorithm: random
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:20, requested cpu: 2000, requested ram: 2147483648
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: Yes
2014-03-21 16:25:13,454 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) This VM has last host_id specified, trying to choose the same host: 66
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) The last host of this VM is in avoid set
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Cannot choose the last host to deploy this VM
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Cluster: 20
2014-03-21 16:25:13,455 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Cluster: 20
2014-03-21 16:25:13,459 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking resources in Cluster: 20 under Pod: 1
2014-03-21 16:25:13,459 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling HostAllocators to find suitable hosts
2014-03-21 16:25:13,459 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:20
2014-03-21 16:25:13,460 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-66-Routing]]
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-66-Routing]]
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=2048
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host name: xenserver-ivehudzt, hostId: 66 is in avoid set, skipping this and trying other available hosts
2014-03-21 16:25:13,462 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable hosts found
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable hosts found under this Cluster: 20
2014-03-21 16:25:13,462 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) DeploymentPlanner allocation algorithm: random
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:null, requested cpu: 2000, requested ram: 2147483648
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: No
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Is ROOT volume READY (pool already allocated)?: No
2014-03-21 16:25:13,463 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) This VM has last host_id specified, trying to choose the same host: 66
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) The last host of this VM is in avoid set
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Cannot choose the last host to deploy this VM
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Searching resources only under specified Pod: 1
2014-03-21 16:25:13,464 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Pod: 1
2014-03-21 16:25:13,465 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) CPUOverprovisioningFactor considered: 6.0
2014-03-21 16:25:13,466 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Removing from the clusterId list these clusters from avoid set: [20]
2014-03-21 16:25:13,470 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking resources in Cluster: 1 under Pod: 1
2014-03-21 16:25:13,470 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling HostAllocators to find suitable hosts
2014-03-21 16:25:13,470 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1
2014-03-21 16:25:13,471 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-56-Routing]]
2014-03-21 16:25:13,472 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-56-Routing]]
2014-03-21 16:25:13,472 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=2048
2014-03-21 16:25:13,474 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Checking if host: 56 has enough capacity for requested CPU: 2000 and requested RAM: 2147483648 , cpuOverprovisioningFactor: 6.0
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 217536
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Free CPU: 184536 , Requested CPU: 2000
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Free RAM: 6890548352 , Requested RAM: 2147483648
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host has enough CPU and RAM available
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 56, used: 33000, reserved: 0, actual total: 36256, total with overprovisioning: 217536; requested cpu:2000,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-21 16:25:13,476 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738 FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 56, used: 17582522368, reserved: 0, total: 24473070720; requested mem: 2147483648,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-21 16:25:13,476 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Found a suitable host, adding to list: 56
2014-03-21 16:25:13,476 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-738 FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Checking suitable pools for volume (Id, Type): (64737,ROOT)
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) We need to allocate new storagepool for this volume
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling StoragePoolAllocators to find suitable pools
2014-03-21 16:25:13,477 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Calling StoragePoolAllocators to find suitable pools
2014-03-21 16:25:13,477 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-738) Looking for pools in dc: 1 pod:1 cluster:1 having tags:[iscsi]
2014-03-21 16:25:13,478 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-738) No storage pools available for shared volume allocation, returning
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable pools found for volume: Vol[64737|vm=64691|ROOT] under cluster: 1
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable pools found
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) No suitable storagePools found under this Cluster: 1
2014-03-21 16:25:13,478 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-738) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-21 16:25:13,599 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: 66 new host id: null host id before state transition: 66
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) Hosts's actual total CPU: 36256 and CPU after applying overprovisioning: 217536
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) release cpu from host: 66, old used: 4000,reserved: 14000, actual total: 36256, total with overprovisioning: 217536; new used: 2000,reserved:14000; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-738) release mem from host: 66, old used: 4294967296,reserved: 16106127360, total: 24472994112; new used: 2147483648,reserved:16106127360; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,691 WARN [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-738) There was an error starting the user vm id: 64691 on storage pool, cannot complete primary storage maintenance
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|test6]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:597)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2815)
at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,742 ERROR [cloud.api.ApiDispatcher] (Job-Executor-10:job-738) Exception while executing CancelPrimaryStorageMaintenanceCmd:
java.lang.ClassCastException: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2848)
at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: com.cloud.utils.exception.ExecutionException cannot be cast to com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:14,546 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-3:null) Async job-738 completed
2014-03-21 16:25:15,133 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-7:null) Async job-731 completed
2014-03-21 16:25:15,995 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2014-03-21 16:25:16,097 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy
2014-03-21 16:25:16,503 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2014-03-21 08:25:16 GMT
^C
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3277-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3277-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 许叁征
发送时间: 2014年3月21日星期五 14:40
收件人: users-cn@cloudstack.apache.org
主题: 答复: 取消维护ISCSI存储提示错误
部署了两个群集，单独的节点，单独的存储，
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 linuxbqj@gmail.com
发送时间: 2014年3月20日星期四 17:36
收件人: users-cn@cloudstack.apache.org
主题: Re: 取消维护ISCSI存储提示错误
你们是部署了几个存储呢？如果是多个存储，并且主机设置了HA 是可以实现迁移的
在 2014年3月20日 下午4:55，hongweinn@gmail.com <ho...@gmail.com> 写道：
>
>
>
>
>
>
> 我也遇见了同样的问题。XENSERVER+FC-SAN模拟FC宕机后怎么恢复。刚开始的时候系统VM启动不了，然后自动创建也失败，最后把FC删了重新添加了一遍。系统VM创建成功。然后两台XENserver中的一台无法创建虚拟机，准备把FC存储再次删除，但是设置成维护模式就变成两个按钮了。一个是启动维护，一个是取消维护。点取消维护就报同样的错误。
> 已经一下午了，仍然没搞定，如果有消息，互通解决方案
>
>
> hongweinn@gmail.com
> ?发件人：?许叁征发送时间：?2014-03-20?15:04收件人：?users-cn@cloudstack.apache.org主题：?取消维护ISCSI存储提示错误?
> HI ALL
> 今天发现ISCSI无法启动虚拟机，在平台上将ISCSI存储设置成维护 状态 ，然后再取
> 消维护，提示以下错误 ，看看这个是怎么问题？一直是这样的，先谢谢了。
> ?
> com.cloud.utils.exception.ExecutionException cannot be cast to
> com.cloud.exception.ResourceUnavailableException
>
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
答复: 取消维护ISCSI存储提示错误
Posted by 许叁征 <xu...@chinanetcenter.com>.
部署了两个群集，单独的节点，单独的存储，
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:xusz@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-----邮件原件-----
发件人: users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org [mailto:users-cn-return-3265-xusz=chinanetcenter.com@cloudstack.apache.org] 代表 linuxbqj@gmail.com
发送时间: 2014年3月20日星期四 17:36
收件人: users-cn@cloudstack.apache.org
主题: Re: 取消维护ISCSI存储提示错误
你们是部署了几个存储呢？如果是多个存储，并且主机设置了HA 是可以实现迁移的
在 2014年3月20日 下午4:55，hongweinn@gmail.com <ho...@gmail.com> 写道：
>
>
>
>
>
>
> 我也遇见了同样的问题。XENSERVER+FC-SAN模拟FC宕机后怎么恢复。刚开始的时候系统VM启动不了，然后自动创建也失败，最后把FC删了重新添加了一遍。系统VM创建成功。然后两台XENserver中的一台无法创建虚拟机，准备把FC存储再次删除，但是设置成维护模式就变成两个按钮了。一个是启动维护，一个是取消维护。点取消维护就报同样的错误。
> 已经一下午了，仍然没搞定，如果有消息，互通解决方案
>
>
> hongweinn@gmail.com
> ?发件人：?许叁征发送时间：?2014-03-20?15:04收件人：?users-cn@cloudstack.apache.org主题：?取消维护ISCSI存储提示错误?
> HI ALL
> 今天发现ISCSI无法启动虚拟机，在平台上将ISCSI存储设置成维护 状态 ，然后再取
> 消维护，提示以下错误 ，看看这个是怎么问题？一直是这样的，先谢谢了。
> ?
> com.cloud.utils.exception.ExecutionException cannot be cast to
> com.cloud.exception.ResourceUnavailableException
>
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
Re: 取消维护ISCSI存储提示错误
Posted by 網勁科技 黃奕璽 / Carl Huang <ca...@edyna.com>.
�e�`ӍϢ����࣮
2014-03-20 17:35 GMT+08:00 linuxbqj@gmail.com <li...@gmail.com>:
> �����Dz����˼����洢�أ�����Ƕ���洢����������������HA �ǿ���ʵ��Ǩ�Ƶ�
>
> �� 2014��3��20�� ����4:55��hongweinn@gmail.com <ho...@gmail.com> ���
> >
> >
> >
> >
> >
> >
> >
> ��Ҳ������ͬ�������⡣XENSERVER+FC-SANģ��FC崻�����ô�ָ����տ�ʼ��ʱ��ϵͳVM�������ˣ�Ȼ���Զ�����Ҳʧ�ܣ�����FCɾ������������һ�顣ϵͳVM�����ɹ���Ȼ����̨XENserver�е�һ̨�����������������FC�洢�ٴ�ɾ�����������ó�ά��ģʽ�ͱ��������ť�ˡ�һ��������ά����һ����ȡ��ά������ȡ��ά���ͱ�ͬ���Ĵ���
> > �Ѿ�һ�����ˣ���Ȼû�㶨���������Ϣ����ͨ�������
> >
> >
> > hongweinn@gmail.com
> > ?�����ˣ�?����������ʱ�䣺?2014-03-20?15:04�ռ��ˣ�?users-cn@cloudstack.apache.org
> ���⣺?ȡ��ά��ISCSI�洢��ʾ����?
> > HI ALL
> > ���췢��ISCSI���������������ƽ̨�Ͻ�ISCSI�洢���ó�ά�� ״̬ ��Ȼ����ȡ
> > ��ά������ʾ���´��� �������������ô���⣿һֱ�������ģ���лл�ˡ�
> > ?
> > com.cloud.utils.exception.ExecutionException cannot be cast to
> > com.cloud.exception.ResourceUnavailableException
> >
>
>
>
> --
> ����� (Born Bai)
>
> ������ԴԸ����Ϣ��������˾
>
> Mail: linuxbqj@gmail.com
>
--
============================================
eDynamics �W�ſƼ�
������̎
����
�S�ȭt Carl Huang
�Ԓ��+886-2-8797-6373 �֙C��6302
���棺+886-2-8797-6272
E-Mail��carl_huang@edyna.com
̨������˾��̨���ЃȺ��^���· 513 �� 28 ̖ 7 ��
�팚�u www.laibaodao.com
oBuyȫ�I�W www.obuy.tw
�ɰ��W www.joinbao.com
CityTalk����ͨ www.citytalk.tw
============================================
Re: 取消维护ISCSI存储提示错误
Posted by "linuxbqj@gmail.com" <li...@gmail.com>.
你们是部署了几个存储呢？如果是多个存储，并且主机设置了HA 是可以实现迁移的
在 2014年3月20日 下午4:55，hongweinn@gmail.com <ho...@gmail.com> 写道：
>
>
>
>
>
>
> 我也遇见了同样的问题。XENSERVER+FC-SAN模拟FC宕机后怎么恢复。刚开始的时候系统VM启动不了，然后自动创建也失败，最后把FC删了重新添加了一遍。系统VM创建成功。然后两台XENserver中的一台无法创建虚拟机，准备把FC存储再次删除，但是设置成维护模式就变成两个按钮了。一个是启动维护，一个是取消维护。点取消维护就报同样的错误。
> 已经一下午了，仍然没搞定，如果有消息，互通解决方案
>
>
> hongweinn@gmail.com
> ?发件人：?许叁征发送时间：?2014-03-20?15:04收件人：?users-cn@cloudstack.apache.org主题：?取消维护ISCSI存储提示错误?
> HI ALL
> 今天发现ISCSI无法启动虚拟机，在平台上将ISCSI存储设置成维护 状态 ，然后再取
> 消维护，提示以下错误 ，看看这个是怎么问题？一直是这样的，先谢谢了。
> ?
> com.cloud.utils.exception.ExecutionException cannot be cast to
> com.cloud.exception.ResourceUnavailableException
>
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
回复: 取消维护ISCSI存储提示错误
Posted by "hongweinn@gmail.com" <ho...@gmail.com>.
我也遇见了同样的问题。XENSERVER+FC-SAN模拟FC宕机后怎么恢复。刚开始的时候系统VM启动不了，然后自动创建也失败，最后把FC删了重新添加了一遍。系统VM创建成功。然后两台XENserver中的一台无法创建虚拟机，准备把FC存储再次删除，但是设置成维护模式就变成两个按钮了。一个是启动维护，一个是取消维护。点取消维护就报同样的错误。
已经一下午了，仍然没搞定，如果有消息，互通解决方案
hongweinn@gmail.com
?发件人：?许叁征发送时间：?2014-03-20?15:04收件人：?users-cn@cloudstack.apache.org主题：?取消维护ISCSI存储提示错误?
HI ALL
今天发现ISCSI无法启动虚拟机，在平台上将ISCSI存储设置成维护 状态 ，然后再取
消维护，提示以下错误 ，看看这个是怎么问题？一直是这样的，先谢谢了。
?
com.cloud.utils.exception.ExecutionException cannot be cast to
com.cloud.exception.ResourceUnavailableException
取消维护ISCSI存储提示错误
Posted by 许叁征 <xu...@chinanetcenter.com>.
HI ALL
今天发现ISCSI无法启动虚拟机，在平台上将ISCSI存储设置成维护 状态 ，然后再取
消维护，提示以下错误 ，看看这个是怎么问题？一直是这样的，先谢谢了。
com.cloud.utils.exception.ExecutionException cannot be cast to
com.cloud.exception.ResourceUnavailableException
回复: Re: 执行cloud-setup-agent,报不能启动agent错误，请大家帮忙分析分析，谢谢
Posted by ganglin_lan <ga...@tcloudcomputing.com>.
find 一下cloud-agent 的pid文件是否存在，如果存在删除再试试
ganglin_lan
发件人： linuxbqj@gmail.com
发送时间： 2014-03-20 17:34
收件人： users-cn
主题： Re: 执行cloud-setup-agent,报不能启动agent错误，请大家帮忙分析分析，谢谢
你检查下kvm的cgroup配置文件是不是修改过
2014-03-19 19:27 GMT+08:00 淡看浮华 <36...@qq.com>:
> 我是在vmware workstation8中的一台虚拟机里同时安装了cloudstack4.0.2的管理节点和agent,操作系统为ubuntu12.04
>
> 在添加域的过程中,添加主机这一步始终失败,agent.log日志里报错，说不能启动agent
> 执行cloud-setup-agent,也是报错说不能启动agent
>
> **************************************************************
> 具体agent.log日志内容如下：
> ***************************************************************
> 2014-03-19 04:07:51,649 ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent:
> com.cloud.utils.exception.CloudRuntimeException: Cannot recv data: Connection reset by peer
> at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:654)
> at com.cloud.agent.Agent.<init>(Agent.java:163)
> at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:559)
> at com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:514)
> at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:431)
> at com.cloud.agent.AgentShell.start(AgentShell.java:589)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> 2014-03-19 04:08:22,946 INFO [utils.component.ComponentLocator] (main:null) Unable to find components.xml
> 2014-03-19 04:08:22,949 INFO [utils.component.ComponentLocator] (main:null) Skipping configuration using components.xml
> 2014-03-19 04:08:22,949 INFO [cloud.agent.AgentShell] (main:null) Implementation Version is 4.0.2.20130501180711
> 2014-03-19 04:08:22,950 INFO [cloud.agent.AgentShell] (main:null) agent.properties found at /etc/cloud/agent/agent.properties
> 2014-03-19 04:08:22,952 INFO [cloud.agent.AgentShell] (main:null) Defaulting to using properties file for storage
> 2014-03-19 04:08:22,958 INFO [cloud.agent.AgentShell] (main:null) Defaulting to the constant time backoff algorithm
> 2014-03-19 04:08:23,076 INFO [cloud.agent.Agent] (main:null) id is
> 2014-03-19 04:08:23,164 INFO [resource.virtualnetwork.VirtualRoutingResource] (main:null) VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
>
> *************************************************************************************
> setup.log日志内容如下：
> *************************************************************************************
> DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}'
> DEBUG:root:execute:ifconfig cloudbr0
> DEBUG:root:Found default network device:cloudbr0
> DEBUG:root:execute:uname -r
> DEBUG:root:execute:uname -m
> DEBUG:root:execute:hostname -f
> DEBUG:root:execute:kvm-ok
> DEBUG:root:execute:service apparmor status
> DEBUG:root:execute:apparmor_status |grep libvirt
> DEBUG:root:Failed to execute:
> DEBUG:root:execute:sudo /usr/sbin/service network-manager status
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}'
> DEBUG:root:execute:ifconfig cloudbr0
> DEBUG:root:Found default network device:cloudbr0
> DEBUG:root:execute:ifconfig eth0
> DEBUG:root:cloudbr0:eth0 already configured
> DEBUG:root:execute:sudo /usr/sbin/service network-manager status
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:sudo /usr/sbin/service network-manager stop
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:sudo /usr/sbin/service network-manager status
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:sudo /usr/sbin/service network-manager stop
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:sudo update-rc.d -f network-manager remove
> DEBUG:root:execute:ifup cloudbr0
> DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
> DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin stop
> DEBUG:root:execute:sudo update-rc.d -f libvirt-bin remove
> DEBUG:root:execute:sudo update-rc.d -f libvirt-bin defaults
> DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
> DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin start
> DEBUG:root:execute:ufw allow 22
> DEBUG:root:execute:ufw allow 1798
> DEBUG:root:execute:ufw allow 16509
> DEBUG:root:execute:ufw allow proto tcp from any to any port 5900:6100
> DEBUG:root:execute:ufw allow proto tcp from any to any port 49152:49216
> DEBUG:root:execute:sudo /usr/sbin/service ufw status
> DEBUG:root:execute:sudo /usr/sbin/service ufw stop
> DEBUG:root:execute:sudo /usr/sbin/service ufw status
> DEBUG:root:execute:sudo /usr/sbin/service ufw start
> DEBUG:root:execute:sudo /usr/sbin/service cloud-agent status
> DEBUG:root:Failed to execute: * could not access PID file for cloud-agent
> DEBUG:root:execute:sudo /usr/sbin/service cloud-agent stop
> DEBUG:root:execute:sleep 30
> DEBUG:root:execute:sudo update-rc.d -f cloud-agent remove
> DEBUG:root:execute:sudo update-rc.d -f cloud-agent defaults
> DEBUG:root:execute:sudo /usr/sbin/service cloud-agent status
> DEBUG:root:Failed to execute: * could not access PID file for cloud-agent
> DEBUG:root:execute:sudo /usr/sbin/service cloud-agent start
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
Re: 执行cloud-setup-agent,报不能启动agent错误，请大家帮忙分析分析，谢谢
Posted by "linuxbqj@gmail.com" <li...@gmail.com>.
你检查下kvm的cgroup配置文件是不是修改过
2014-03-19 19:27 GMT+08:00 淡看浮华 <36...@qq.com>:
> 我是在vmware workstation8中的一台虚拟机里同时安装了cloudstack4.0.2的管理节点和agent,操作系统为ubuntu12.04
>
> 在添加域的过程中,添加主机这一步始终失败,agent.log日志里报错，说不能启动agent
> 执行cloud-setup-agent,也是报错说不能启动agent
>
> **************************************************************
> 具体agent.log日志内容如下：
> ***************************************************************
> 2014-03-19 04:07:51,649 ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent:
> com.cloud.utils.exception.CloudRuntimeException: Cannot recv data: Connection reset by peer
> at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:654)
> at com.cloud.agent.Agent.<init>(Agent.java:163)
> at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:559)
> at com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:514)
> at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:431)
> at com.cloud.agent.AgentShell.start(AgentShell.java:589)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> 2014-03-19 04:08:22,946 INFO [utils.component.ComponentLocator] (main:null) Unable to find components.xml
> 2014-03-19 04:08:22,949 INFO [utils.component.ComponentLocator] (main:null) Skipping configuration using components.xml
> 2014-03-19 04:08:22,949 INFO [cloud.agent.AgentShell] (main:null) Implementation Version is 4.0.2.20130501180711
> 2014-03-19 04:08:22,950 INFO [cloud.agent.AgentShell] (main:null) agent.properties found at /etc/cloud/agent/agent.properties
> 2014-03-19 04:08:22,952 INFO [cloud.agent.AgentShell] (main:null) Defaulting to using properties file for storage
> 2014-03-19 04:08:22,958 INFO [cloud.agent.AgentShell] (main:null) Defaulting to the constant time backoff algorithm
> 2014-03-19 04:08:23,076 INFO [cloud.agent.Agent] (main:null) id is
> 2014-03-19 04:08:23,164 INFO [resource.virtualnetwork.VirtualRoutingResource] (main:null) VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
>
> *************************************************************************************
> setup.log日志内容如下：
> *************************************************************************************
> DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}'
> DEBUG:root:execute:ifconfig cloudbr0
> DEBUG:root:Found default network device:cloudbr0
> DEBUG:root:execute:uname -r
> DEBUG:root:execute:uname -m
> DEBUG:root:execute:hostname -f
> DEBUG:root:execute:kvm-ok
> DEBUG:root:execute:service apparmor status
> DEBUG:root:execute:apparmor_status |grep libvirt
> DEBUG:root:Failed to execute:
> DEBUG:root:execute:sudo /usr/sbin/service network-manager status
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}'
> DEBUG:root:execute:ifconfig cloudbr0
> DEBUG:root:Found default network device:cloudbr0
> DEBUG:root:execute:ifconfig eth0
> DEBUG:root:cloudbr0:eth0 already configured
> DEBUG:root:execute:sudo /usr/sbin/service network-manager status
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:sudo /usr/sbin/service network-manager stop
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:sudo /usr/sbin/service network-manager status
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:sudo /usr/sbin/service network-manager stop
> DEBUG:root:Failed to execute:network-manager: unrecognized service
> DEBUG:root:execute:sudo update-rc.d -f network-manager remove
> DEBUG:root:execute:ifup cloudbr0
> DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
> DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin stop
> DEBUG:root:execute:sudo update-rc.d -f libvirt-bin remove
> DEBUG:root:execute:sudo update-rc.d -f libvirt-bin defaults
> DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
> DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin start
> DEBUG:root:execute:ufw allow 22
> DEBUG:root:execute:ufw allow 1798
> DEBUG:root:execute:ufw allow 16509
> DEBUG:root:execute:ufw allow proto tcp from any to any port 5900:6100
> DEBUG:root:execute:ufw allow proto tcp from any to any port 49152:49216
> DEBUG:root:execute:sudo /usr/sbin/service ufw status
> DEBUG:root:execute:sudo /usr/sbin/service ufw stop
> DEBUG:root:execute:sudo /usr/sbin/service ufw status
> DEBUG:root:execute:sudo /usr/sbin/service ufw start
> DEBUG:root:execute:sudo /usr/sbin/service cloud-agent status
> DEBUG:root:Failed to execute: * could not access PID file for cloud-agent
> DEBUG:root:execute:sudo /usr/sbin/service cloud-agent stop
> DEBUG:root:execute:sleep 30
> DEBUG:root:execute:sudo update-rc.d -f cloud-agent remove
> DEBUG:root:execute:sudo update-rc.d -f cloud-agent defaults
> DEBUG:root:execute:sudo /usr/sbin/service cloud-agent status
> DEBUG:root:Failed to execute: * could not access PID file for cloud-agent
> DEBUG:root:execute:sudo /usr/sbin/service cloud-agent start
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com