cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darren Tang <darrentang...@gmail.com>
Subject Re: 答复: cloudstack4.3.1+esxi5.5无法正常启动系统VM和虚拟路由器
Date Mon, 24 Nov 2014 04:48:24 GMT
哥们,下次描述问题时,注意思维逻辑,你的描述我都快看迷糊了。

能否说明下,光钎提供的这个Lun,你是直接挂载到具体某个主机了,还是挂载到cluster中了?

另外,你可以测试下启动本地存储,然后修改system.vm.use.local.storage变量为true。看是否能正常创建在本地存储上。

看日志报错是主存储没准备好。



2014-11-24 11:03 GMT+08:00 gx.zhu <gx.zhu@beyonditsm.com>:

> Hi
>     我已经检查了好多变,实在发现不了问题所在,nfs二级存储正常,能查询到。
> showmount -e 192.168.200.21
> Export list for 192.168.200.21:
> /export *
>
> # df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/vg_rhel62-lv_root
> 49G 4.9G 42G 11% /
> tmpfs 3.9G 88K 3.9G 1% /dev/shm
> /dev/sda1 485M 37M 424M 8% /boot
> 192.168.200.21:/export/secondary
> 49G 4.9G 42G 11% /secondary
>
> # ll /export/secondary/template/tmpl/1/8
> total 596628
> -rw-r--r--. 1 root root 305465344 Nov 18 23:19
> 0518848f-5bff-4058-b568-881286ce5b8d.ova
> -rw-r--r--. 1 64 64 305454080 Jan 16 2014
> systemvm64template-2014-01-14-master-vmware-disk1.vmdk
> -rw-r--r--. 1 64 64 199 Jan 16 2014
> systemvm64template-2014-01-14-master-vmware.mf
> -rw-r--r--. 1 64 64 8012 Jan 16 2014
> systemvm64template-2014-01-14-master-vmware.ovf
> -rw-r--r--. 1 root root 283 Nov 24 08:49 template.properties
>
>
>
> 发件人: Star Guo
> 发送时间: 2014-11-24 09:14
> 收件人: users-cn@cloudstack.apache.org
> 主题: 答复: cloudstack4.3.1+esxi5.5无法正常启动系统VM和虚拟路由器
> 你好,
>
> INFO [c.c.c.ConfigurationManagerImpl] (catalina-exec-6:ctx-63e982f9
> ctx-328d0287) No storage traffic type was specified by admin, create
> default
> storage traffic on physical network 200 with same configure of management
> traffic type
> INFO [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-971a2b28) No
> stopped console proxy is available, need to allocate a new console proxy
> WARN [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-971a2b28)
> Exception
> while trying to start console proxy
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[ConsoleProxy|v-1-VM]Scope=interface
> com.cloud.dc.DataCenter; id=1
>
>
> 按照官方文档的描述,重新检查一次系统,同时检查nfs二级存储是否正常。
>
>
> Best Regards,
>
> Star Guo
>
>
> 发件人: gx.zhu [mailto:gx.zhu@beyonditsm.com]
> 发送时间: 2014年11月22日 22:56
> 收件人: users-cn
> 主题: cloudstack4.3.1+esxi5.5无法正常启动系统VM和虚拟路由器
>
>
>
> 大家好,
>
>     我配置了cloudstack4.3.1,虚拟主机192.168.200.23使用esxi5.5,虚拟主机使用
> 自带硬盘和光纤连接的一个LUN,格式化为vmfs。vcenter主机配置在一台192.168.200.
> 20的虚拟机上,cs主机配置在192.168.200.21的虚拟机上,这两台虚拟机位于192.168.
> 200.25的物理主机上。网络均使用一个192.168.200.X网段互通.
>
>
>
>
> 现在是cs安装后,svvm无法启动,vroute未启动,辅助存储大小为0,主存储显示为虚
> 拟主机192.168.200.23全部存储大小。
>
> 我的困惑在于svvm、vroute和辅助存储相互的关系是什么?到底是因为哪个环节出现了
> 问题导致系统无法正常使用。
>
>
> 附件为相关日志,请大家帮忙看看,非常感谢!
>
> 下面为部分日志:
>
>
>
>
> INFO [c.c.h.v.r.VmwareResource] (DirectAgent-2:ctx-4a1d9f3c 192.168.200.24)
> Executing resource ReadyCommand: {"dcId":1,"hostId":1,"wait":0}
> INFO [c.c.h.v.u.VmwareContextPool] (DirectAgent-2:ctx-4a1d9f3c
> 192.168.200.24) Return a VmwareContext from the idle pool:
> administrator@vsphere.local@192.168.200.20. current pool size: 0,
> outstanding count: 1
> INFO [c.c.h.v.u.VmwareContextPool] (DirectAgent-2:ctx-4a1d9f3c
> 192.168.200.24) Recycle VmwareContext into idle pool:
> administrator@vsphere.
> local@192.168.200.20, current idle pool size: 1, outstanding count: 1
> INFO [c.c.r.ResourceManagerImpl] (catalina-exec-3:ctx-d614db0a
> ctx-51eebb04)
> External cluster has been successfully discovered by VMware Discover
> INFO [c.c.h.v.r.VmwareResource] (DirectAgent-1:ctx-712d35e7 192.168.200.24)
> Executing resource ModifyStoragePoolCommand:
>
> {"add":true,"pool":{"id":1,"uuid":"31f21f69-18ad-3926-92b2-a2ccf879bc96","ho
> st":"VMFS datastore:
>
> /PC1/datastore24xiv","path":"/PC1/datastore24xiv","port":0,"type":"VMFS"},"l
> ocalPath":"/mnt//92e92b85-4b93-33cc-981b-5adf070c2d00","wait":0}
> INFO [c.c.h.v.u.VmwareContextPool] (DirectAgent-1:ctx-712d35e7
> 192.168.200.24) Return a VmwareContext from the idle pool:
> administrator@vsphere.local@192.168.200.20. current pool size: 0,
> outstanding count: 1
> INFO [c.c.h.v.u.VmwareContextPool] (DirectAgent-1:ctx-712d35e7
> 192.168.200.24) Recycle VmwareContext into idle pool:
> administrator@vsphere.
> local@192.168.200.20, current idle pool size: 1, outstanding count: 1
> INFO [o.a.c.s.d.p.DefaultHostListener] (catalina-exec-25:ctx-601305d5
> ctx-3fae7d27) Connection established between
> org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@3536023a
> host +
> 1
> INFO [o.a.c.s.d.l.CloudStackImageStoreLifeCycleImpl]
> (catalina-exec-4:ctx-d2f11a56 ctx-52adde16) Trying to add a new data store
> at nfs://192.168.200.21/export/secondary to data center 1
> INFO [c.c.c.ConfigurationManagerImpl] (catalina-exec-6:ctx-63e982f9
> ctx-328d0287) No storage traffic type was specified by admin, create
> default
> storage traffic on physical network 200 with same configure of management
> traffic type
> INFO [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-971a2b28) No
> stopped console proxy is available, need to allocate a new console proxy
> WARN [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-971a2b28)
> Exception
> while trying to start console proxy
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[ConsoleProxy|v-1-VM]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManage
> rImpl.java:922)
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
> l.java:761)
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
> l.java:745)
> at
>
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManage
> rImpl.java:555)
> at
>
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyMan
> agerImpl.java:941)
> at
>
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManage
> rImpl.java:1666)
> at
>
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManage
> rImpl.java:157)
> at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:118)
> at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:35)
> at
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:88)
> at
>
> com.cloud.vm.SystemVmLoadScanner$1.runInContext(SystemVmLoadScanner.java:79)
> at
>
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedCo
> ntextRunnable.java:49)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Defa
> ultManagedContext.java:56)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCon
> text(DefaultManagedContext.java:103)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCont
> ext(DefaultManagedContext.java:53)
> at
>
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCont
> extRunnable.java:46)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$
> 201(ScheduledThreadPoolExecutor.java:165)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sch
> eduledThreadPoolExecutor.java:267)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
> 10)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
> 03)
> at java.lang.Thread.run(Thread.java:679)
> INFO [c.c.s.PremiumSecondaryStorageManagerImpl] (secstorage-1:ctx-8707020a)
> No running secondary storage vms found in datacenter id=1, starting one
> INFO [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-8707020a) No
> stopped secondary storage vm is available, need to allocate a new secondary
> storage vm
> WARN [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-8707020a)
> Exception while trying to start secondary storage vm
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[SecondaryStorageVm|s-2-VM]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManage
> rImpl.java:922)
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
> l.java:761)
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
> l.java:745)
> at
>
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(Se
> condaryStorageManagerImpl.java:261)
> at
>
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(Second
> aryStorageManagerImpl.java:694)
> at
>
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(Secondary
> StorageManagerImpl.java:1278)
> at
>
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSeco
> ndaryStorageManagerImpl.java:123)
> at
>
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSeco
> ndaryStorageManagerImpl.java:50)
> at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
> at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:35)
> at
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:88)
> at
>
> com.cloud.vm.SystemVmLoadScanner$1.runInContext(SystemVmLoadScanner.java:79)
> at
>
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedCo
> ntextRunnable.java:49)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Defa
> ultManagedContext.java:56)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCon
> text(DefaultManagedContext.java:103)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCont
> ext(DefaultManagedContext.java:53)
> at
>
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCont
> extRunnable.java:46)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$
> 201(ScheduledThreadPoolExecutor.java:165)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sch
> eduledThreadPoolExecutor.java:267)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
> 10)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
> 03)
> at java.lang.Thread.run(Thread.java:679)
> INFO [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-8707020a)
> Unable to start secondary storage vm for standby capacity, secStorageVm vm
> Id : 2, will recycle it and start a new one
> INFO [c.c.s.PremiumSecondaryStorageManagerImpl] (secstorage-1:ctx-8707020a)
> Primary secondary storage is not even started, wait until next turn
> INFO [c.c.h.v.u.VmwareContextPool] (DirectAgent-4:ctx-c98b8c75
> 192.168.200.24) Return a VmwareContext from the idle pool:
> administrator@vsphere.local@192.168.200.20. current pool size: 0,
> outstanding count: 1
> INFO [c.c.h.v.u.VmwareContextPool] (DirectAgent-4:ctx-c98b8c75
> 192.168.200.24) Recycle VmwareContext into idle pool:
> administrator@vsphere.
> local@192.168.200.20, current idle pool size: 1, outstanding count: 1
> INFO [c.c.h.v.u.VmwareContext] (DirectAgent-3:ctx-107363e4 192.168.200.24)
> New VmwareContext object, current outstanding count: 2
> INFO [c.c.h.v.u.VmwareContextPool] (DirectAgent-3:ctx-107363e4
> 192.168.200.24) Recycle VmwareContext into idle pool:
> administrator@vsphere.
> local@192.168.200.20, current idle pool size: 2, outstanding count: 2
> INFO [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-b31ebe3f) Found a
> stopped console proxy, bring it up to running pool. proxy vm id : 1
> WARN [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-b31ebe3f)
> Exception
> while trying to start console proxy
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[ConsoleProxy|v-1-VM]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManage
> rImpl.java:922)
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
> l.java:761)
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
> l.java:745)
> at
>
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManage
> rImpl.java:555)
> at
>
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyMan
> agerImpl.java:941)
> at
>
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManage
> rImpl.java:1666)
> at
>
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManage
> rImpl.java:157)
> at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:118)
> at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:35)
> at
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:88)
> at
>
> com.cloud.vm.SystemVmLoadScanner$1.runInContext(SystemVmLoadScanner.java:79)
> at
>
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedCo
> ntextRunnable.java:49)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Defa
> ultManagedContext.java:56)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCon
> text(DefaultManagedContext.java:103)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCont
> ext(DefaultManagedContext.java:53)
> at
>
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCont
> extRunnable.java:46)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$
> 201(ScheduledThreadPoolExecutor.java:165)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sch
> eduledThreadPoolExecutor.java:267)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
> 10)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
> 03)
> at java.lang.Thread.run(Thread.java:679)
> INFO [c.c.s.PremiumSecondaryStorageManagerImpl] (secstorage-1:ctx-62fb65a9)
> No running secondary storage vms found in datacenter id=1, starting one
> INFO [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-62fb65a9)
> Found
> a stopped secondary storage vm, bring it up to running pool. secStorageVm
> vm
> id : 2
> WARN [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-62fb65a9)
> Exception while trying to start secondary storage vm
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[SecondaryStorageVm|s-2-VM]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManage
> rImpl.java:922)
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
> l.java:761)
> at
>
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
> l.java:745)
> at
>
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(Se
> condaryStorageManagerImpl.java:261)
> at
>
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(Second
> aryStorageManagerImpl.java:694)
> at
>
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(Secondary
> StorageManagerImpl.java:1278)
> at
>
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSeco
> ndaryStorageManagerImpl.java:123)
> at
>
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSeco
> ndaryStorageManagerImpl.java:50)
> at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
> at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:35)
> at
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:88)
> at
>
> com.cloud.vm.SystemVmLoadScanner$1.runInContext(SystemVmLoadScanner.java:79)
> at
>
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedCo
> ntextRunnable.java:49)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Defa
> ultManagedContext.java:56)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCon
> text(DefaultManagedContext.java:103)
> at
>
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCont
> ext(DefaultManagedContext.java:53)
> at
>
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCont
> extRunnable.java:46)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$
> 201(ScheduledThreadPoolExecutor.java:165)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sch
> eduledThreadPoolExecutor.java:267)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
> 10)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
> 03)
> at java.lang.Thread.run(Thread.java:679)
>
>
>
>
>
>
>
>
>
>
>   _____
>
>
>
>
> 朱高校
>
>
> 邮箱:gx.zhu@beyonditsm.com
>
>
>
>

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