[GitHub] [cloudstack] fangyi1008 commented on issue #7053: cant not instance

GitBox Thu, 05 Jan 2023 02:30:12 -0800


fangyi1008 commented on issue #7053:
URL: https://github.com/apache/cloudstack/issues/7053#issuecomment-1372040099


   > > > 你能分享更多日志吗？
   > > > 管理日志：
   > > 
   > > 
   > > ## 2023-01-05 17:52:11,528 DEBUG [ccvVmWorkJobDispatcher] 
(Work-Job-Executor-98:ctx-00ddfb01 job-446/job-447) (logid:564609bc) 完成运行 VM 
工作作业：com.cloud VM 101 的 .vm.VmWorkStart，作业来源：446
   > > 2023-01-05 17:52:11,528 错误 [ccvVmWorkJobDispatcher] 
(Work-Job-Executor-98:ctx-00ddfb01 job-446/job-447) (logid:564609bc) 无法完成 
AsyncJobVO: {id:447, userId : 2, accountId: 2, instanceType: null, instanceId: 
null, cmd: com.cloud.vm.VmWorkStart, cmdInfo:
   > > 
BRG5OaGRtVmtYM0JoYzNOM2IzSmt4cA，cmdVersion：0，状态：IN_PROGRESS，processStatus：0，resultCode：0，结果：null，initMsid：261833773422727，completeMsid：null，lastUpdated：null，lastPolled：null，创建时间：Thu
 Jan 05 17:51:5263 CST 5263 
，已删除：null}，作业来源：446com.cloud.exception.InsufficientServerCapacityException：无法为 
VM 实例创建部署 {id：“101”，名称：“i-2-101-VM”，uuid：“60093c58-bba6 
-470e-a958-0d30e5507628", type="User"}Scope=interface com.cloud.dc.DataCenter; 
id=1 InsufficientServerCapacityException: 无法为 VM 实例创建部署 {id: "101", name: 
"i-2-101-VM", uuid: "60093c58-bba6-470e-a958-0d30e5507628", type="User"}Scope 
=接口com.cloud.dc.DataCenter；id=1 InsufficientServerCapacityException: 无法为 VM 
实例创建部署 {id: "101", name: "i-2-101-VM", uuid: 
"60093c58-bba6-470e-a958-0d30e5507628", type="User"}Scope 
=接口com.cloud.dc.DataCenter；id=1
   > > 在 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1140)
   > > 在 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5315)
   > > 在 jdk.internal.reflect.GeneratedMethodAccessor554.invoke(Unknown Source)
   > > 在 java 
.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   > > 在 java.base/java.lang.reflect.Method.invoke(Method.java:566)
   > > 在 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob 
(VmWorkJobHandlerProxy.java:107)
   > > 在 
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5439)
   > > 在 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
   > > 在 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
   > > 在 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
   > > 在 org.apache 
.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
   > > 在 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
   > > 在 org.apache.cloudstack。 
managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
   > > 在 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
   > > 在 org.apache.cloudstack.framework.jobs.impl。 
AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
   > > 在 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
   > > 在 java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
   > > 在 java.base/java 
.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
   > > 在 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
   > > 在 java.base/java.lang.Thread.run (Thread.java:829) 
   > > 2023-01-05 17:52:11,541 INFO [oacfjiAsyncJobMonitor] 
(Work-Job-Executor-98:ctx-00ddfb01 job-446/job-447) (logid:564609bc) 删除作业 
447从作业监控
   > > 2023-01-05 17:52:11,554 DEBUG [ccvUserVmManagerImpl] 
(API-Job-Executor-117:ctx-f896976b job-446 ctx-c292f039) (logid:564609bc) 销毁 vm 
VM 实例 {id: "101", name : "i-2-101-VM", uuid: 
"60093c58-bba6-470e-a958-0d30e5507628", type="User"} 因为它无法
   > > 在 ID 为：12023-01-05 17:52 的主机上创建： 11,571 调试 [cccCapacityManagerImpl] 
(API-Job-Executor-117:ctx-f896976b job-446 ctx-c292f039) (logid:564609bc) VM 实例 
{id: "101", name: "i-2-101-VM", uuid: "60093c58-bba6-470e-a958-0d30e5507628", 
type="User"} 状态从 [Stopped] 转变为 [
   > > 错误] 与事件 
[OperationFailedToError]。VM的原始主机：null，新主机：null，状态转换前的主机：null2023-01-05 
17:52:11,586 DEBUG [ccrResourceLimitManagerImpl] 
(API-Job-Executor-117:ctx-f896976b job-446 ctx-c292f039) ( logid:564609bc) 
更新资源类型 = 帐户的数量 = 2 操作 = 减少数量 = 1 
   > > 2023-01-05 17:52:11,595 DEBUG [ccrResourceLimitManagerImpl] 
(API-Job-Executor-117:ctx-f896976b job-446 ctx -c292f039) (logid:564609bc) 
更新资源类型 = 帐户的主要存储计数 = 2 操作 = 减少数量 = (20.00 GB) 21474836480
   > > 2023-01-05 17:52:11,614 警告 [ccaAlertManagerImpl] 
(API-Job-Executor-117:ctx-f896976b job-446 ctx-c292f039) (logid:564609bc) 
alertType=[8] dataCenterId=[1] podId= [1] clusterId=[null] message=[无法在 ID 为 1 
的主机上部署 ID 为 101 的虚拟机]。
   > > 2023-01-05 17:52:11,621 WARN [ccaAlertManagerImpl] 
(API-Job-Executor-117:ctx-f896976b job-446 ctx-c292f039) (logid:564609bc) 
全局设置中未设置收件人 'alert.email.addresses '，跳过发送主题为 [无法在主机 w 上部署 ID 为 101 的 Vm 的警报
   > > ith Id: 1] 和内容 [无法在 ID 为 1 的主机上部署 ID 为 101 的 Vm].2023-01-05 17:52:11,622 
DEBUG [ccrResourceLimitManagerImpl] (API-Job-Executor-117:ctx- f896976b job-446 
ctx-c292f039) (logid:564609bc) 更新资源类型 = 帐户的 user_vm 计数 = 2 操作 = 减少数量 = 1 
   > > 2023-01-05 17:52:11,630 DEBUG [ccrResourceLimitManagerImpl] 
(API-Job-Executor- 117:ctx-f896976b job-446 ctx-c292f039) (logid:564609bc) 
更新资源类型 = 帐户的 cpu 计数 = 2 操作 = 减少数量 = 1 
   > > 2023-01-05 17:52:11,637 DEBUG [ccrResourceLimitManagerImpl] (API- 
Job-Executor-117:ctx-f896976b job-446 ctx-c292f039) (logid:564609bc) 更新资源类型 = 
帐户的内存计数 = 2 操作 = 减少数量 = 512
   > > 2023-01-05 17:52:11,653 错误 [ccaApiAsyncJobDispatcher] 
(API-Job-Executor-117:ctx-f896976b job-446) (logid:564609bc) 执行 
org.apache.cloudstack.api.command.admin 时出现意外异常.vm.DeployVMCmdByAdmin 
   > > com.cloud.utils.exception.CloudRuntimeException：无法启动 VM 
[60093c58-bba6-470e-a958-0d30e5507628] 由于 [无法为 VM 实例创建部署 {id：“101”，名称： 
“i-2-101-VM”，uuid：“60093c58-bba6-470e-a958-0d30e5507628”，类型 =“用户”}]。
   > > 在 
com.cloud.vm.VirtualMachineManagerImpl.start（VirtualMachineManagerImpl.java:803）
   > > 在 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine（VMEntityManagerImpl.java:243）
   > > 在 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
   > > 在 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:5311)
   > > 在 com.cloud.vm.UserVmManagerImpl 
.startVirtualMachine(UserVmManagerImpl.java:5161)
   > > 在 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4788)
   > > 在 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4777)
   > > 在 java.base/jdk。 internal.reflect.NativeMethodAccessorImpl.invoke0（本机方法）
   > > 在 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）
   > > 在 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java
 :43)
   > > 在 java.base/java.lang.reflect.Method.invoke(Method.java:566)
   > > 在 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
   > > 在 org.springframework.aop.framework.ReflectiveMethodInvocation 
.invokeJoinpoint（ReflectiveMethodInvocation.java:198）
   > > 在 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed（ReflectiveMethodInvocation.java:163）
   > > 在 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke（EventUtils.java
 :107)
   > > 在 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
   > > 在 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:52)
   > > 在 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
   > > 在 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
   > > 在 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed 
（ReflectiveMethodInvocation.java:186）
   > > 在 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke（JdkDynamicAopProxy.java:215）
   > > 在 com.sun.proxy.$Proxy180.startVirtualMachine（未知来源）
   > > 在 
org.apache.cloudstack.api。命令.user.vm.DeployVMCmd.execute（DeployVMCmd.java:714）
   > > 在com.cloud.api.ApiDispatcher.dispatch（ApiDispatcher.java:163）
   > > 
在com.cloud.api.ApiAsyncJobDispatcher.runJob（ApiAsyncJobDispatcher.java:106）
   > > 在 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
   > > 在 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
   > > 在 org.apache 
.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
   > > 在 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
   > > 在 org.apache.cloudstack。 
managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
   > > 在 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
   > > 在 org.apache.cloudstack.framework.jobs.impl。 
AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
   > > 在 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
   > > 在 java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
   > > 在 java.base/java 
.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
   > > 在 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
   > > 在 java.base/java.lang.Thread.run (Thread.java:829)
   > > 原因：com.cloud.exception.InsufficientServerCapacityException：无法为 VM 实例创建部署 
{id：“101”，名称：“i-2-101-VM”，uuid：“60093c58- bba6-470e-a958-0d30e5507628", 
type="User"}Scope=interface com.cloud.dc.DataCenter; id=1
   > > 在 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart（VirtualMachineManagerImpl.java:1140）
   > > 在 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart（VirtualMachineManagerImpl.java:5315）
   > > 在 jdk.internal.reflect.GeneratedMethodAccessor554.invoke（未知来源）
   > > ... 17 更多
   > > 2023-01-05 17:52:11,664 信息 [oacfjiAsyncJobMonitor] 
(API-Job-Executor-117:ctx-f896976b job-446) (logid:564609bc) 从作业监控中删除 job-446 
   > > 2023-01-05 17:52:11,768 DEBUG [ccaApiServlet] 
(qtp1747352992-8705:ctx-d2189185 ) (logid:b61b54a5) ===START=== 192.168.0.102 
-- GET 
jobId=564609bc-a5e0-43eb-a1a9-45f5513d3ee0&command=queryAsyncJobResult&response=json
   > > 2023-01-05 17:52:11,772 DEBUG [ccaApiServer] 
(qtp1747352992-8705:ctx-d2189185 ctx-cbaabce4) (logid:b61b54a5) 来自哪个帐户的 CIDR 
[2217c707-8817-11ed-9cb1-dae1-0442admin] -- 账户{"id": 2, "name": "admin", 
"uuid": "2217c707-8817-11ed-9cb1-04421a1ae40d 
   > > "}'允许执行API调用：0.0.0.0/0,:: /0
   > > 代理日志：2023-01-05 17:52:04,529 DEBUG 
[resource.virtualnetwork.VirtualRoutingResource] (agentRequest-Handler-2:null) 
(logid:564609bc) 尝试连接到 169.254.236.18 2023-01-05 17:52 :05,532 DEBUG 
[kvm.resource.LibvirtComputingResource] (UgentTask-5:null) (logid:) 
执行：/usr/share/cloudstack-common/scripts/vm/network/security_group.py 
get_rule_logs_for_vms 2023-01-05 17:52 :05,534 DEBUG 
[kvm.resource.LibvirtComputingResource] (UgentTask-5:null) (logid:) 
超时执行：1800000 2023-01-05 17:52:05,624 DEBUG 
[kvm.resource.LibvirtComputingResource] (UgentTask-5: null) (logid:) 
执行成功。2023-01-05 17:52:05,625 DEBUG [kvm.resource.LibvirtConnection] 
(UgentTask-5:null) (logid:) 在以下位置寻找 libvirtd 连接：qemu:///system 2023-01-05 
17:52： 05,641 DEBUG [cloud.agent.Agent] (UgentTask-5:null) (logid: 
LibvirtComputingResource] (agentRequest-Handler-5:null) (logid:564609bc) 
执行成功。2023-01-05 17:52:08,842 DEBUG [kvm.resource.LibvirtComputingResource] (ag
 entRequest-Handler-5:null) (logid:564609bc) 清理虚拟机 r-99-VM 虚拟机快照的元数据 2023-01-05 
17:52:08,843 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:564609bc) 首先尝试停止虚拟机 2023-01-05 
17:52:10,951 DEBUG [kvm.resource. LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:564609bc) 成功关闭 vm r-99-VM 2023-01-05 
17:52:10,951 WARN [kvm.resource.LibvirtKvmAgentHook] (agentRequest-Handler-5: 
null) (logid:564609bc) Groovy 脚本 
'/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' 
不可用。不会应用转换。2023-01-05 17:52:10,951 警告 [kvm.resource。LibvirtKvmAgentHook] 
(agentRequest-Handler-5:null) (logid:564609bc) Groovy 
脚本引擎未初始化。跳过数据转换。2023-01-05 17:52:10,951 DEBUG 
[kvm.storage.KVMStoragePoolManager] (agentRequest-Handler-5:null) 
(logid:564609bc) 通过路径断开物理磁盘：/var/lib/libvirt/images/68bbe57a-a958 
-430f-8a97-f3a4cc2d4b4e 2023-01-05 17:52
 :10,951 调试 [kvm.storage.StorPoolStorageAdaptor] (agentRequest-Handler-5:null) 
(logid:564609bc) disconnectPhysicalDiskByPath: 
localPath=/var/lib/libvirt/images /68bbe57a-a958-430f-8a97-f3a4cc2d4b4e 
2023-01-05 17:52:10,951 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:564609bc) 
无法使用空路径清理磁盘（也许是空光驱）：跳过数据转换。2023-01-05 17:52:10,951 DEBUG 
[kvm.storage.KVMStoragePoolManager] (agentRequest-Handler-5:null) 
(logid:564609bc) 通过路径断开物理磁盘：/var/lib/libvirt/images/68bbe57a-a958 
-430f-8a97-f3a4cc2d4b4e 2023-01-05 17:52:10,951 调试 
[kvm.storage.StorPoolStorageAdaptor] (agentRequest-Handler-5:null) 
(logid:564609bc) disconnectPhysicalDiskByPath: 
localPath=/var/lib/libvirt/images /68bbe57a-a958-430f-8a97-f3a4cc2d4b4e 
2023-01-05 17:52:10,951 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:564609bc) 无法使用空路径清理磁盘（也许是空光驱�
 �：跳过数据转换。2023-01-05 17:52:10,951 DEBUG [kvm.storage.KVMStoragePoolManager] 
(agentRequest-Handler-5:null) (logid:564609bc) 
通过路径断开物理磁盘：/var/lib/libvirt/images/68bbe57a-a958 -430f-8a97-f3a4cc2d4b4e 
2023-01-05 17:52:10,951 调试 [kvm.storage.StorPoolStorageAdaptor] 
(agentRequest-Handler-5:null) (logid:564609bc) disconnectPhysicalDiskByPath: 
localPath=/var/lib/libvirt/images /68bbe57a-a958-430f-8a97-f3a4cc2d4b4e 
2023-01-05 17:52:10,951 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:564609bc) 无法使用空路径清理磁盘（也许是空光驱）：
   > > 2023-01-05 17:52:10,951 DEBUG [utils.script.Script] 
(agentRequest-Handler-5:null) (logid:564609bc) 执行：/bin/bash -c ls 
/sys/class/net/cloudbr0 2023 -01-05 17:52:10,953 DEBUG [utils.script.Script] 
(agentRequest-Handler-5:null) (logid:564609bc) 超时执行：3600000 2023-01-05 
17:52:10,957 DEBUG [utils .script.Script] (agentRequest-Handler-5:null) 
(logid:564609bc) 执行成功。2023-01-05 17:52:10,958 DEBUG [utils.script.Script] 
(agentRequest-Handler-5:null) (logid:564609bc) 执行：/bin/bash -c ls 
/sys/class/net/cloudbr0/简介 | tr ' ' ' ' 2023-01-05 17:52:10,960 DEBUG 
[utils.script.Script] (agentRequest-Handler-5:null) (logid:564609bc) 
超时执行：3600000 2023-01-05 17: 52:10,964 DEBUG [utils.script.Script] 
(agentRequest-Handler-5:null) (logid:564609bc) 执行成功。2023-01-05 17:52:10,965 
DEBUG [utils.script.Script] (agentRequest-Handler-5:null) (logid:564609bc) 
执行：/bin/bash -c ls /sys/class/net/cloud0 2023 -01-05 17:52:10,966 DEBUG 
[utils.script.Script] (
 agentRequest-Handler-5:null) (logid:564609bc) 超时执行：3600000 2023-01-05 
17:52:10,969 DEBUG [utils .script.Script] (agentRequest-Handler-5:null) 
(logid:564609bc) 执行成功。2023-01-05 17:52:10,969 DEBUG [utils.script.Script] 
(agentRequest-Handler-5:null) (logid:564609bc) 执行：/bin/bash -c ls 
/sys/class/net/cloud0/简介 | tr ' ' ' ' 2023-01-05 17:52:10,970 DEBUG 
[utils.script.Script] (agentRequest-Handler-5:null) (logid:564609bc) 
超时执行：3600000 2023-01-05 17: 52:10,974 DEBUG [utils.script.Script] 
(agentRequest-Handler-5:null) (logid:564609bc) 执行成功。011 信息 
[kvm.resource.LibvirtConnection] (agentRequest-Handler-1:null) (logid:564609bc) 
找不到现有的 libvirtd 连接。打开一个新的 2023-01-05 17:52:11,013 DEBUG 
[kvm.resource.LibvirtConnection] (agentRequest-Handler-1:null) (logid:564609bc) 
找不到实例的 LXC 连接：r-99-VM，继续。2023-01-05 17:52:11,013 WARN 
[kvm.resource.LibvirtConnection] (agentRequest-Handler-1:null) (logid:564
 609bc) 找不到实例 r-99-VM 的连接。假设默认连接。2023-01-05 17:52:11,013 DEBUG 
[kvm.resource.LibvirtConnection] (agentRequest-Handler-1:null) (logid:564609bc) 
在以下位置寻找 libvirtd 连接：qemu:///system 2023-01-05 17 ：52：11,026 DEBUG 
[kvm.resource.LibvirtComputingResource]（agentRequest-Handler-1：null）（logid：564609bc）无法获取dom
 xml：org.libvirt.LibvirtException：找不到域：null) (logid:564609bc) Executing while 
with timeout : 1800000 2023-01-05 17:52:11,124 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null) 
(logid:564609bc) 执行成功。2023-01-05 17:52:11,125 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null) 
(logid:564609bc) 无法获取虚拟机：找不到域：没有匹配名称 'r-99 的域-VM' 2023-01-05 17:52:11,125 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null) 
(logid:564609bc) 首先尝试停止虚拟机 2023-01-05 17:52 :11,126 DEBUG [kvm.re
 source.LibvirtComputingResource] (agentRequest-Handler-1:null) 
(logid:564609bc) VM r-99-VM 不存在，无需停止它 2023-01-05 17:52:11,126警告 
[kvm.resource.LibvirtKvmAgentHook] (agentRequest-Handler-1:null) 
(logid:564609bc) Groovy 脚本 ' 
/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' 
不可用。不会应用转换。2023-01-05 17:52:11,126 WARN [kvm.resource.LibvirtKvmAgentHook] 
(agentRequest-Handler-1:null) (logid:564609bc) Groovy 
脚本引擎未初始化。跳过数据转换。2023-01-05 17:52:11,126 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-1:null) (logid:564609bc) Seq 1-4745668107341661097: { 
Ans: , MgmtId: 261833773422727, via: 1, Ver : v1, 标志: 10, 
[{"com.cloud.agent.api.StopAnswer":{"result":"true","wait":"0","bypassHostMaintenan
 ce":"false"}}] } 2023-01-05 17:52:11,239 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-4:null) (logid:564609bc) Request:Seq 
1-4745668107341661098: { Cmd, MgmtId: 261833773422727, 通过: 1,版本：v1，标志：10001
 1，null) (logid:564609bc) 找不到实例的 KVM 连接：i-2-101-VM，继续。2023-01-05 17:52:11,252 
DEBUG [kvm.resource.LibvirtConnection] (agentRequest-Handler-4:null) 
(logid:564609bc) 在以下位置寻找 libvirtd 连接：lxc:/// 2023-01-05 17： 52:11,252 INFO 
[kvm.resource.LibvirtConnection] (agentRequest-Handler-4:null) (logid:564609bc) 
找不到现有的 libvirtd 连接。打开一个新的 2023-01-05 17:52:11,253 DEBUG 
[kvm.resource.LibvirtConnection] (agentRequest-Handler-4:null) (logid:564609bc) 
找不到实例的 LXC 连接：i-2-101-虚拟机，继续。2023-01-05 17:52:11,253 WARN 
[kvm.resource.LibvirtConnection] (agentRequest-Handler-4:null) (logid:564609bc) 
找不到实例 i-2-101-VM 的连接。假设默认连接。2023-01-05 17:52:11,253 调试 [kvm.resource。266 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) 
(logid:564609bc) 
执行：/usr/share/cloudstack-common/scripts/vm/network/security_group.py 
destroy_network_rules_for_vm --
 vmname i-2 -101-VM 2023-01-05 17:52:11,267 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) 
(logid:564609bc) 超时执行：1800000 2023-01-05 17:52 :11,448 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) 
(logid:564609bc) 执行成功。2023-01-05 17:52:11,449 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) 
(logid:564609bc) ebtables：没有链/目标/匹配该名称 ebtables：没有链/目标/按那个名字匹配 
ebtables：没有链/目标/匹配那个名字 ebtables：没有链/目标/匹配那个名字 ebtables：没有那个名字的链/目标/匹配 
ebtables：没有那个名字的链/目标/匹配 
iptables：没有那个名字的链/目标/匹配。iptables：没有那个名字的链/目标/匹配。iptables：没有那个名字的链/目标/匹配。iptables：没有那个名字的链/目标/匹配。iptables：没有那个名字的链/目标/匹配。iptables：没有那个名字的链/目�
 ��/匹配。ipset v7.1：具有给定名称的集合不存在
   > > 2023-01-05 17:52:11,450 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-4:null) (logid:564609bc) 
无法获取虚拟机：找不到域：没有匹配名称“i-2”的域-101-VM' 2023-01-05 17:52:11,450 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) 
(logid:564609bc) 首先尝试停止虚拟机 2023-01-05 17 :52:11,450 DEBUG 
[kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) 
(logid:564609bc) VM i-2-101-VM 不存在，无需停止 2023-01-05 17 :52:11,450 WARN 
[kvm.resource.LibvirtKvmAgentHook] (agentRequest-Handler-4:null) 
(logid:564609bc) Groovy 脚本 
'/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' 
不是可用的。不会应用转换。2023-01-05 17:52:11,451 警告 [kvm.resource.LibvirtKvmAgentHook] 
(agentRequest-Handler-4: null) (logid:564609bc) Groovy 
脚本引擎未初始化。跳过数据转换。2023-01-05 17:52:11,451 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-4:null) (logid:564609bc)
  Seq 1-4745668107341661098: { Ans: , MgmtId: 261833773422727, via: 1, Ver : 
v1, 标志: 10, 
[{"com.cloud.agent.api.StopAnswer":{"result":"true","wait":"0","bypassHostMaintenan
 ce":"false"}}] } 2023-01-05 17:52:33,939 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-3:null) (logid:d8ff1a24) 
处理命令：com.cloud.agent.api.GetStorageStatsCommand 2023-01-05 17 :52:33,940 INFO 
[kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-3:null) 
(logid:d8ff1a24) 尝试从 libvirt 获取存储池 9c23d00b-a619-4842-a7d1-045727e46f0e 
564609bc) Groovy 脚本引擎未初始化。跳过数据转换。2023-01-05 17:52:11,451 DEBUG 
[cloud.agent.Agent] (agentRequest-Handler-4:null) (logid:564609bc) Seq 
1-4745668107341661098: { Ans: , MgmtId: 261833773422727, via: 1, Ver : v1, 标志: 
10, 
[{"com.cloud.agent.api.StopAnswer":{"result":"true","wait":"0","bypassHostMaintenan
 ce":"false"}}] } 2023-01-05 17:52:33,939 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-3:null) (logid:d8ff1a24) 处理命令�
 �com.cloud.agent.api.GetStorageStatsCommand 2023-01-05 17 :52:33,940 INFO 
[kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-3:null) 
(logid:d8ff1a24) 尝试从 libvirt 获取存储池 9c23d00b-a619-4842-a7d1-045727e46f0e 
564609bc) Groovy 脚本引擎未初始化。跳过数据转换。2023-01-05 17:52:11,451 DEBUG 
[cloud.agent.Agent] (agentRequest-Handler-4:null) (logid:564609bc) Seq 
1-4745668107341661098: { Ans: , MgmtId: 261833773422727, via: 1, Ver : v1, 标志: 
10, 
[{"com.cloud.agent.api.StopAnswer":{"result":"true","wait":"0","bypassHostMaintenan
 ce":"false"}}] } 2023-01-05 17:52:33,939 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-3:null) (logid:d8ff1a24) 
处理命令：com.cloud.agent.api.GetStorageStatsCommand 2023-01-05 17 :52:33,940 INFO 
[kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-3:null) 
(logid:d8ff1a24) 尝试从 libvirt 获取存储池 9c23d00b-a619-4842-a7d1-045727e46f0e
   > 
   > @fangyi1008 启动 VR 时出现问题。
   > 
   > ```
   > 2023-01-05 17:52:08,515 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-2:null) (logid:564609bc) Executing: 
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh 
get_template_version.sh 169.254.236.18
   > 2023-01-05 17:52:08,517 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-2:null) (logid:564609bc) Executing while with timeout : 
1800000
   > 2023-01-05 17:52:08,598 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-2:null) (logid:564609bc) Exit value is 255
   > ```
   > 
   > 你能检查 VR 是否是从正确的模板创建的吗？
   
   
![image](https://user-images.githubusercontent.com/89246132/210758715-0d8713b4-d349-4ccd-84d6-9a7ef51cb8ac.png)
   <img width="283" alt="4abba8537f57dcba24e277670106efc" 
src="https://user-images.githubusercontent.com/89246132/210758743-01b9c6cf-b8d4-4472-b347-432f7a179f9e.png";>
   `2023-01-05 18:26:51,015 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) GetDomRVersionCmd failed
   2023-01-05 18:26:51,015 WARN  [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Command: com.cloud.agent.api.GetDomRVersionCommand failed 
while starting virtual router
   2023-01-05 18:26:51,015 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) The guru did not like the answers so stopping VM instance {id: 
"99", name: "r-99-VM", uuid: "4fcea489-51f8-4bd9-baef-65dc2282
   8a94", type="DomainRouter"}2023-01-05 18:26:51,026 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Seq 1-4100808935697547316: Sending  { Cmd , MgmtId: 
279278805475902, via: 1(cluster13), Ver: v1, Flags: 100011, 
[{"com.cloud.agent.api.StopCo
   
mmand":{"isProxy":"false","checkBeforeCleanup":"false","controlIp":"169.254.37.251","forceStop":"false","vlanToPersistenceMap":{"untagged":"true"},"volumesToDisconnect":[],"vmName":"r-99-VM","executeInSequence":"false","wait":"0","bypassHostMaintenance":"false"}}]
 }2023-01-05 18:26:51,188 DEBUG [c.c.a.ApiServlet] 
(qtp1747352992-37:ctx-558cfce4) (logid:aeb58cdb) ===START===  192.168.0.103 -- 
GET  
jobId=1c5b362f-6ddc-4ee0-b0f7-6b5b2c8f9dc3&command=queryAsyncJobResult&response=json
   2023-01-05 18:26:51,193 DEBUG [c.c.a.ApiServer] 
(qtp1747352992-37:ctx-558cfce4 ctx-9d61d1fb) (logid:aeb58cdb) CIDRs from which 
account 'Acct[2217c707-8817-11ed-9cb1-04421a1ae40d-admin] -- Account {"id": 2, 
"name": "admin", "uuid": "2217c707-8817-11ed-9cb1-04421a1ae40d"}
   ' is allowed to perform API calls: 0.0.0.0/0,::/02023-01-05 18:26:51,202 
DEBUG [c.c.a.ApiServlet] (qtp1747352992-37:ctx-558cfce4 ctx-9d61d1fb) 
(logid:aeb58cdb) ===END===  192.168.0.103 -- GET  
jobId=1c5b362f-6ddc-4ee0-b0f7-6b5b2c8f9dc3&command=queryAsyncJobResult&response=json
   2023-01-05 18:26:52,210 DEBUG [c.c.c.ClusterManagerImpl] 
(Cluster-Heartbeat-1:ctx-52c7c052) (logid:04db3ddc) Detected management node 
left, id:7, nodeIP:192.168.0.13
   2023-01-05 18:26:52,210 INFO  [c.c.c.ClusterManagerImpl] 
(Cluster-Heartbeat-1:ctx-52c7c052) (logid:04db3ddc) Trying to connect to 
192.168.0.13
   2023-01-05 18:26:52,210 INFO  [c.c.c.ClusterManagerImpl] 
(Cluster-Heartbeat-1:ctx-52c7c052) (logid:04db3ddc) Management node 7 is 
detected inactive by timestamp but is pingable
   2023-01-05 18:26:53,709 DEBUG [c.c.c.ClusterManagerImpl] 
(Cluster-Heartbeat-1:ctx-0eb73d18) (logid:d790ec50) Detected management node 
left, id:7, nodeIP:192.168.0.13
   2023-01-05 18:26:53,709 INFO  [c.c.c.ClusterManagerImpl] 
(Cluster-Heartbeat-1:ctx-0eb73d18) (logid:d790ec50) Trying to connect to 
192.168.0.13
   2023-01-05 18:26:53,709 INFO  [c.c.c.ClusterManagerImpl] 
(Cluster-Heartbeat-1:ctx-0eb73d18) (logid:d790ec50) Management node 7 is 
detected inactive by timestamp but is pingable
   2023-01-05 18:26:53,917 DEBUG [c.c.a.t.Request] 
(AgentManager-Handler-6:null) (logid:) Seq 1-4100808935697547316: Processing:  
{ Ans: , MgmtId: 279278805475902, via: 1, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.StopAnswer":{"result":"true","wait":"0","bypassHostMainten
   ance":"false"}}] }2023-01-05 18:26:53,917 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Seq 1-4100808935697547316: Received:  { Ans: , MgmtId: 
279278805475902, via: 1(cluster13), Ver: v1, Flags: 10, { StopAnswer } }
   2023-01-05 18:26:53,917 ERROR [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Failed to start instance VM instance {id: "99", name: 
"r-99-VM", uuid: "4fcea489-51f8-4bd9-baef-65dc22828a94", type="DomainRo
   uter"}com.cloud.utils.exception.ExecutionException: Unable to start  
VM:4fcea489-51f8-4bd9-baef-65dc22828a94 due to error in finalizeStart, not 
retrying
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1299)
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5315)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at 
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
        at 
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5439)
        at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
        at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
        at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
        at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
   2023-01-05 18:26:53,922 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Cleaning up resources for the vm VM instance {id: "99", name: 
"r-99-VM", uuid: "4fcea489-51f8-4bd9-baef-65dc22828a94", type="
   DomainRouter"} in Starting state2023-01-05 18:26:53,934 DEBUG 
[c.c.a.t.Request] (Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 
ctx-84952946) (logid:1c5b362f) Seq 1-4100808935697547317: Sending  { Cmd , 
MgmtId: 279278805475902, via: 1(cluster13), Ver: v1, Flags: 100011, 
[{"com.cloud.agent.api.StopCo
   
mmand":{"isProxy":"false","checkBeforeCleanup":"false","controlIp":"169.254.37.251","forceStop":"false","vlanToPersistenceMap":{"untagged":"true"},"volumesToDisconnect":[],"vmName":"r-99-VM","executeInSequence":"false","wait":"0","bypassHostMaintenance":"false"}}]
 }2023-01-05 18:26:54,109 DEBUG [c.c.a.t.Request] (AgentManager-Handler-7:null) 
(logid:) Seq 1-4100808935697547317: Processing:  { Ans: , MgmtId: 
279278805475902, via: 1, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.StopAnswer":{"result":"true","wait":"0","bypassHostMainten
   ance":"false"}}] }2023-01-05 18:26:54,109 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Seq 1-4100808935697547317: Received:  { Ans: , MgmtId: 
279278805475902, via: 1(cluster13), Ver: v1, Flags: 10, { StopAnswer } }
   2023-01-05 18:26:54,113 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Successfully updated user statistics as a part of domR VM 
instance {id: "99", name: "r-99-VM", uuid: "4fcea489-51f
   8-4bd9-baef-65dc22828a94", type="DomainRouter"} reboot/stop2023-01-05 
18:26:54,119 DEBUG [c.c.n.NetworkModelImpl] (Work-Job-Executor-4:ctx-bdb6d533 
job-516/job-517 ctx-84952946) (logid:1c5b362f) Service SecurityGroup is not 
supported in the network id=204
   2023-01-05 18:26:54,128 DEBUG [c.c.n.g.ControlNetworkGuru] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Released nic: NicProfile 
{"broadcastUri":null,"iPv4Address":null,"id":202,"reservationId":null,"vmId":99}
   2023-01-05 18:26:54,134 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Successfully released network resources for the VM VM instance 
{id: "99", name: "r-99-VM", uuid: "4fcea489-51f8-4bd9-baef-65d
   c22828a94", type="DomainRouter"} in Starting state2023-01-05 18:26:54,138 
DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-4:ctx-bdb6d533 
job-516/job-517 ctx-84952946) (logid:1c5b362f) Successfully released storage 
resources for the VM VM instance {id: "99", name: "r-99-VM", uuid: 
"4fcea489-51f8-4bd9-baef-65d
   c22828a94", type="DomainRouter"} in Starting state2023-01-05 18:26:54,138 
DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-4:ctx-bdb6d533 
job-516/job-517 ctx-84952946) (logid:1c5b362f) Successfully cleaned up 
resources for the VM VM instance {id: "99", name: "r-99-VM", uuid: 
"4fcea489-51f8-4bd9-baef-65dc22828
   a94", type="DomainRouter"} in Starting state2023-01-05 18:26:54,150 DEBUG 
[c.c.c.CapacityManagerImpl] (Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 
ctx-84952946) (logid:1c5b362f) VM instance {id: "99", name: "r-99-VM", uuid: 
"4fcea489-51f8-4bd9-baef-65dc22828a94", type="DomainRouter"} state transited 
from [St
   arting] to [Stopped] with event [OperationFailed]. VM's original host: null, 
new host: null, host before state transition: Host {"id": "1", "name": 
"cluster13", "uuid": "cf71da72-bd76-40b5-9f4a-98599b3359f3", 
"type"="Routing"}2023-01-05 18:26:54,154 DEBUG [c.c.c.CapacityManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Hosts's actual total CPU: 256000000 and CPU after applying 
overprovisioning: 256000000
   2023-01-05 18:26:54,154 DEBUG [c.c.c.CapacityManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Hosts's actual total RAM: (502.52 GB) 539572183040 and RAM 
after applying overprovisioning: (502.52 GB) 539572174848
   2023-01-05 18:26:54,154 DEBUG [c.c.c.CapacityManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) release cpu from host: 1, old used: 1500,reserved: 0, actual 
total: 256000000, total with overprovisioning: 256000000; new used: 10
   00,reserved:0; movedfromreserved: false,moveToReserveredfalse2023-01-05 
18:26:54,154 DEBUG [c.c.c.CapacityManagerImpl] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) release mem from host: 1, old used: (1.75 GB) 
1879048192,reserved: (0 bytes) 0, total: (502.52 GB) 539572174848; new used: 
(1.50 GB
   ) 1610612736,reserved:(0 bytes) 0; movedfromreserved: 
false,moveToReserveredfalse2023-01-05 18:26:54,158 ERROR 
[c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 
ctx-84952946) (logid:1c5b362f) Invocation exception, caused by: 
com.cloud.exception.AgentUnavailableException: Resource [Host:1] is 
unreachable: Host 1: Unable 
   to start instance due to Unable to start  
VM:4fcea489-51f8-4bd9-baef-65dc22828a94 due to error in finalizeStart, not 
retrying2023-01-05 18:26:54,158 INFO  [c.c.v.VmWorkJobHandlerProxy] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517 ctx-84952946) 
(logid:1c5b362f) Rethrow exception 
com.cloud.exception.AgentUnavailableException: Resource [Host:1] is 
unreachable: Host 1: Unable to start instan
   ce due to Unable to start  VM:4fcea489-51f8-4bd9-baef-65dc22828a94 due to 
error in finalizeStart, not retrying2023-01-05 18:26:54,158 DEBUG 
[c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517) 
(logid:1c5b362f) Done with run of VM work job: com.cloud.vm.VmWorkStart for VM 
99, job origin: 516
   2023-01-05 18:26:54,158 ERROR [c.c.v.VmWorkJobDispatcher] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517) (logid:1c5b362f) Unable to 
complete AsyncJobVO: {id:517, userId: 2, accountId: 2, instanceType: null, 
instanceId: null, cmd: com.cloud.vm.VmWorkStart, cmdInfo: r
   
O0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAAAAAAAAAACAAAAAAAAAAIAAAAAAAAAY3QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAAAAAAAAAHBwcHBwcHBwc3IAEWphdmEudXRpbC5IYXNoTWFwBQfawcMWYNEDAAJGAApsb2FkRmFjdG9ySQAJdGhyZXNob2xkeHA_QAAAAAAADHcIAAAAEAAAAAF0AA5SZXN0YXJ0TmV0d29ya3QAP3JPMEFCWE55QUJGcVlYWmhMbXhoYm1jdVFtOXZiR1ZoYnMwZ2NvRFZuUHJ1QWdBQldnQUZkbUZzZFdWNGNBRXhw,
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 279278805475902, completeMsid: null, lastUpdated: null, 
lastPolled: null,
  created: Thu Jan 05 18:26:35 CST 2023, removed: null}, job 
origin:516com.cloud.exception.AgentUnavailableException: Resource [Host:1] is 
unreachable: Host 1: Unable to start instance due to Unable to start  
VM:4fcea489-51f8-4bd9-baef-65dc22828a94 due to error in finalizeStart, not 
retrying
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1335)
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5315)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at 
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
        at 
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5439)
        at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
        at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
        at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
        at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
   Caused by: com.cloud.utils.exception.ExecutionException: Unable to start  
VM:4fcea489-51f8-4bd9-baef-65dc22828a94 due to error in finalizeStart, not 
retrying
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1299)
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5315)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        ... 18 more
   2023-01-05 18:26:54,175 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(Work-Job-Executor-4:ctx-bdb6d533 job-516/job-517) (logid:1c5b362f) Remove 
job-517 from job monitoring
   2023-01-05 18:26:54,195 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-4:ctx-25433880 job-516) (logid:1c5b362f) Unexpected exception 
while executing org.apache.cloudstack.api.command.admin.router.StartRouterCmd
   com.cloud.exception.AgentUnavailableException: Resource [Host:1] is 
unreachable: Host 1: Unable to start instance due to Unable to start  
VM:4fcea489-51f8-4bd9-baef-65dc22828a94 due to error in finalizeStart, not 
retrying
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1335)
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5315)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at 
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
        at 
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5439)
        at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
        at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
        at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
        at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
   Caused by: com.cloud.utils.exception.ExecutionException: Unable to start  
VM:4fcea489-51f8-4bd9-baef-65dc22828a94 due to error in finalizeStart, not 
retrying
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1299)
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5315)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        ... 18 more
   2023-01-05 18:26:54,204 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(API-Job-Executor-4:ctx-25433880 job-516) (logid:1c5b362f) Remove job-516 from 
job monitoring
   2023-01-05 18:26:54,355 DEBUG [c.c.a.ApiServlet] 
(qtp1747352992-40:ctx-131d1182) (logid:0ddf6efa) ===START===  192.168.0.103 -- 
GET  
jobId=1c5b362f-6ddc-4ee0-b0f7-6b5b2c8f9dc3&command=queryAsyncJobResult&response=json
   2023-01-05 18:26:54,360 DEBUG [c.c.a.ApiServer] 
(qtp1747352992-40:ctx-131d1182 ctx-d7d071b3) (logid:0ddf6efa) CIDRs from which 
account 'Acct[2217c707-8817-11ed-9cb1-04421a1ae40d-admin] -- Account {"id": 2, 
"name": "admin", "uuid": "2217c707-8817-11ed-9cb1-04421a1ae40d"}
   ' is allowed to perform API calls: 0.0.0.0/0,::/02023-01-05 18:26:54,371 
DEBUG [c.c.a.ApiServlet] (qtp1747352992-40:ctx-131d1182 ctx-d7d071b3) 
(logid:0ddf6efa) ===END===  192.168.0.103 -- GET  
jobId=1c5b362f-6ddc-4ee0-b0f7-6b5b2c8f9dc3&command=queryAsyncJobResult&response=json
   2023-01-05 18:26:54,461 DEBUG [c.c.a.ApiServlet] 
(qtp1747352992-37:ctx-bff314b1) (logid:516f1d8c) ===START===  192.168.0.103 -- 
GET  
listall=true&projectid=-1&id=4fcea489-51f8-4bd9-baef-65dc22828a94&page=1&pagesize=20&command=listRouters&response=json
   2023-01-05 18:26:54,466 DEBUG [c.c.a.ApiServer] 
(qtp1747352992-37:ctx-bff314b1 ctx-22ea9ae1) (logid:516f1d8c) CIDRs from which 
account 'Acct[2217c707-8817-11ed-9cb1-04421a1ae40d-admin] -- Account {"id": 2, 
"name": "admin", "uuid": "2217c707-8817-11ed-9cb1-04421a1ae40d"}
   ' is allowed to perform API calls: 0.0.0.0/0,::/0`
   Failed to start vr


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

[GitHub] [cloudstack] fangyi1008 commented on issue #7053: cant not instance

Reply via email to