cloudstack 全局设置中的host 参数设置成management-server IP，management.network.cidr 设置成相应的值了吗
ganglin_lan 发件人： 风南 发送时间： 2014-03-22 15:30 收件人： users-cn 主题： Re: [求助] v4.2.1 启动报错 补充一些信息： [root@cs-manager ~]# netstat -antp| grep 9090 tcp 0 0 :::9090 :::* LISTEN 4282/java [root@cs-manager ~]# ps -ef | grep java| grep 4282 cloud 4282 1 4 22:45 ? 00:01:52 /usr/lib/jvm/java/bin/java -Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -classpath :::/etc/cloudstack/management:/usr/share/cloudstack-management/setup:/usr/share/cloudstack-management/bin/bootstrap.jar:/usr/share/cloudstack-management/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/cloudstack-management -Dcatalina.home=/usr/share/cloudstack-management -Djava.endorsed.dirs= -Djava.io.tmpdir=/usr/share/cloudstack-management/temp -Djava.util.logging.config.file=/usr/share/cloudstack-management/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start 2014-03-22 15:23 GMT+08:00 风南 <winnery...@gmail.com>: > 各位好。 > > 不好意思，刚才Gmail的快捷键误发了和一个没有写完的邮件，请管理员删除。 > > 安装的4.2.1一直都没有启动成功过，请各位高手帮忙，非常感谢。 > 环境如下： > > management-server: > 运行在vmware workstation的虚拟机中，网络桥接模式。 > 物理宿主机为windows7，IP：192.168.11.30 > 配置： > CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 两个 > 内存：2GB > 磁盘：80GB > IP： 192.168.11.61 > GW: 192.168.11.1 > Host： > 运行在另一台物理主机，XenServer6.1.0 > 配置： > CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz > 内存：8GB > 磁盘：2TB > IP： 192.168.11.40 > GW: 192.168.11.1 > > 一级存储和二级存储使用NFS模式，NFS服务端：management-server（192.168.11.61） 中： > primary: /export/primary > secondary: /export/secondary > 在Host中挂载NFS读写都没有问题 > > management-server iptables: > [root@cs-manager management]# cat /etc/sysconfig/iptables > # Generated by iptables-save v1.4.7 on Mon Mar 17 06:02:02 2014 > *filter > :INPUT ACCEPT [0:0] > :FORWARD ACCEPT [0:0] > :OUTPUT ACCEPT [999012:2307279867] > -A INPUT -p tcp -m tcp --dport 9090 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 8250 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 7080 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 111 -j ACCEPT > -A INPUT -p udp -m udp --dport 111 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 2049 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 32803 -j ACCEPT > -A INPUT -p udp -m udp --dport 32769 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 892 -j ACCEPT > -A INPUT -p udp -m udp --dport 892 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 875 -j ACCEPT > -A INPUT -p udp -m udp --dport 875 -j ACCEPT > -A INPUT -p tcp -m tcp --dport 662 -j ACCEPT > -A INPUT -p udp -m udp --dport 662 -j ACCEPT > -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT > -A INPUT -p icmp -j ACCEPT > -A INPUT -i lo -j ACCEPT > -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT > -A INPUT -j REJECT --reject-with icmp-host-prohibited > -A FORWARD -j REJECT --reject-with icmp-host-prohibited > COMMIT > # Completed on Mon Mar 17 06:02:02 2014 > > 完整日志文件请见：http://hctysoft.com/management-server.log > 从日志中分析来看在启动Console Proxy VM的报错，下面是我截取的一些关键的management-server日志片段： > catalina.out: > > INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) register cluster > listener class com.cloud.cluster.LockMasterListener > INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Trying to connect to > 192.168.11.61 > ERROR [cloud.cluster.ClusterManagerImpl] (Timer-2:) Unable to ping > management server at 192.168.11.61:9090 due to ConnectException > java.net.ConnectException: Connection refused > at sun.nio.ch.Net.connect0(Native Method) > at sun.nio.ch.Net.connect(Net.java:465) > at sun.nio.ch.Net.connect(Net.java:457) > at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670) > at > com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) > at > com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) > at > com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) > at > com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) > at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > > management-server.log > 2014-03-22 22:45:57,912 INFO [cloud.cluster.ClusterManagerImpl] > (Timer-2:null) Cluster node IP : 192.168.11.61 > 2014-03-22 22:45:57,959 DEBUG [utils.db.ConnectionConcierge] > (Timer-2:null) Registering a database connection for LockMaster1 > 2014-03-22 22:45:57,959 INFO [utils.db.Merovingian2] (Timer-2:null) > Cleaning up locks for 52243566829 > 2014-03-22 22:45:57,960 INFO [utils.db.Merovingian2] (Timer-2:null) > Released 0 locks for 52243566829 > 2014-03-22 22:45:57,960 INFO [cloud.cluster.ClusterManagerImpl] > (Timer-2:null) register cluster listener class > com.cloud.cluster.LockMasterListener > 2014-03-22 22:45:57,988 INFO [cloud.cluster.ClusterManagerImpl] > (Timer-2:null) Trying to connect to 192.168.11.61 > 2014-03-22 22:45:57,993 ERROR [cloud.cluster.ClusterManagerImpl] > (Timer-2:null) Unable to ping management server at 192.168.11.61:9090 due > to ConnectException > java.net.ConnectException: Connection refused > at sun.nio.ch.Net.connect0(Native Method) > at sun.nio.ch.Net.connect(Net.java:465) > at sun.nio.ch.Net.connect(Net.java:457) > at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670) > at > com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) > at > com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) > at > com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) > at > com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) > at > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > 2014-03-22 22:45:57,994 INFO [cloud.cluster.ClusterManagerImpl] > (Timer-2:null) Detected that another management node with the same IP > 192.168.11.61 is considered as running in DB, however it is not pingable, > we will continue cluster initialization with this management server node > 2014-03-22 22:45:57,995 INFO [cloud.cluster.ClusterManagerImpl] > (Timer-2:null) Cluster manager is configured. > > > > > > 2014-03-22 22:47:28,883 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 27744 and > CPU after applying overprovisioning: 27744 > 2014-03-22 22:47:28,883 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:FirstFitRoutingAllocator) Free CPU: 27744 , Requested CPU: 500 > 2014-03-22 22:47:28,883 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:FirstFitRoutingAllocator) Free RAM: 3773286656 , Requested > RAM: 268435456 > 2014-03-22 22:47:28,884 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM > available > 2014-03-22 22:47:28,884 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 1, > used: 0, reserved: 0, actual total: 27744, total with overprovisioning: > 27744; requested cpu:500,alloc_from_last_host?:false > ,considerReservedCapacity?: true > 2014-03-22 22:47:28,884 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 1, > used: 0, reserved: 0, total: 3773286656; requested mem: > 268435456,alloc_from_last_host?:false ,considerReservedCapacity?: true > 2014-03-22 22:47:28,884 DEBUG [allocator.impl.FirstFitAllocator] > (secstorage-1:FirstFitRoutingAllocator) Found a suitable host, adding to > list: 1 > 2014-03-22 22:47:28,884 DEBUG [allocator.impl.FirstFitAllocator] > (secstorage-1:FirstFitRoutingAllocator) Host Allocator returning 1 suitable > hosts > 2014-03-22 22:47:28,885 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) Checking suitable pools for volume (Id, Type): > (109,ROOT) > 2014-03-22 22:47:28,885 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) We need to allocate new storagepool for this volume > 2014-03-22 22:47:28,885 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) Calling StoragePoolAllocators to find suitable pools > 2014-03-22 22:47:28,886 DEBUG > [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) > LocalStoragePoolAllocator trying to find storage pool to fit the vm > 2014-03-22 22:47:28,888 DEBUG > [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) > LocalStoragePoolAllocator returning 0 suitable storage pools > 2014-03-22 22:47:28,888 DEBUG > [storage.allocator.ClusterScopeStoragePoolAllocator] (secstorage-1:null) > ClusterScopeStoragePoolAllocator looking for storage pool > 2014-03-22 22:47:28,888 DEBUG > [storage.allocator.ZoneWideStoragePoolAllocator] (secstorage-1:null) > ZoneWideStoragePoolAllocator to find storage pool > 2014-03-22 22:47:28,888 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) No suitable pools found for volume: > Vol[109|vm=108|ROOT] under cluster: 1 > 2014-03-22 22:47:28,888 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) No suitable pools found > 2014-03-22 22:47:28,888 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) No suitable storagePools found under this Cluster: 1 > 2014-03-22 22:47:28,888 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (consoleproxy-1:null) Trying to deploy VM, vm has dcId: 1 and podId: null > 2014-03-22 22:47:28,888 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (consoleproxy-1:null) Deploy avoids pods: null, clusters: null, hosts: null > 2014-03-22 22:47:28,889 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) Could not find suitable Deployment Destination for this > VM under any clusters, returning. > 2014-03-22 22:47:28,889 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) Searching all possible resources under this Zone: 1 > 2014-03-22 22:47:28,890 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) Deploy avoids pods: null, clusters: null, hosts: null > 2014-03-22 22:47:28,890 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) Listing clusters in order of aggregate capacity, that > have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 > 2014-03-22 22:47:28,890 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) DeploymentPlanner allocation algorithm: > com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_c03f8c9@27cf6eb9 > 2014-03-22 22:47:28,890 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) Trying to allocate a host and storage pools from > dc:1, pod:null,cluster:null, requested cpu: 500, requested ram: 1073741824 > 2014-03-22 22:47:28,890 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) Is ROOT volume READY (pool already allocated)?: No > 2014-03-22 22:47:28,890 DEBUG [cloud.deploy.FirstFitPlanner] > (consoleproxy-1:null) Searching all possible resources under this Zone: 1 > 2014-03-22 22:47:28,891 DEBUG [cloud.deploy.FirstFitPlanner] > (consoleproxy-1:null) Listing clusters in order of aggregate capacity, that > have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 > 2014-03-22 22:47:28,892 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) Removing from the clusterId list these clusters from > avoid set: [1] > 2014-03-22 22:47:28,892 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) No clusters found after removing disabled clusters and > clusters in avoid list, returning. > 2014-03-22 22:47:28,896 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) Checking resources in Cluster: 1 under Pod: 1 > 2014-03-22 22:47:28,896 DEBUG [allocator.impl.FirstFitAllocator] > (consoleproxy-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 > cluster:1 > 2014-03-22 22:47:28,898 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Starting to Stopped with > event: OperationFailedvm's original host id: null new host id: null host id > before state transition: null > 2014-03-22 22:47:28,898 DEBUG [allocator.impl.FirstFitAllocator] > (consoleproxy-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to > check for allocation: [Host[-1-Routing]] > 2014-03-22 22:47:28,900 WARN > [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) > Exception while trying to start secondary storage vm > com.cloud.exception.InsufficientServerCapacityException: Unable to create > a deployment for VM[SecondaryStorageVm|s-108-VM]Scope=interface > com.cloud.dc.DataCenter; id=1 > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:570) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:267) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:696) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > 2014-03-22 22:47:28,900 DEBUG [allocator.impl.FirstFitAllocator] > (consoleproxy-1:FirstFitRoutingAllocator) Found 1 hosts for allocation > after prioritization: [Host[-1-Routing]] > 2014-03-22 22:47:28,900 DEBUG [allocator.impl.FirstFitAllocator] > (consoleproxy-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=1024 > 2014-03-22 22:47:28,905 INFO > [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable > to start secondary storage vm for standby capacity, secStorageVm vm Id : > 108, will recycle it and start a new one > 2014-03-22 22:47:28,906 INFO > [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) > Primary secondary storage is not even started, wait until next turn > 2014-03-22 22:47:28,910 DEBUG [cloud.capacity.CapacityManagerImpl] > (consoleproxy-1:FirstFitRoutingAllocator) Checking if host: 1 has enough > capacity for requested CPU: 500 and requested RAM: 1073741824 , > cpuOverprovisioningFactor: 1.0 > 2014-03-22 22:47:28,913 DEBUG [cloud.capacity.CapacityManagerImpl] > (consoleproxy-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 27744 > and CPU after applying overprovisioning: 27744 > 2014-03-22 22:47:28,913 DEBUG [cloud.capacity.CapacityManagerImpl] > (consoleproxy-1:FirstFitRoutingAllocator) Free CPU: 27744 , Requested CPU: > 500 > 2014-03-22 22:47:28,913 DEBUG [cloud.capacity.CapacityManagerImpl] > (consoleproxy-1:FirstFitRoutingAllocator) Free RAM: 3773286656 , Requested > RAM: 1073741824 > 2014-03-22 22:47:28,913 DEBUG [cloud.capacity.CapacityManagerImpl] > (consoleproxy-1:FirstFitRoutingAllocator) Host has enough CPU and RAM > available > 2014-03-22 22:47:28,913 DEBUG [cloud.capacity.CapacityManagerImpl] > (consoleproxy-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from host: > 1, used: 0, reserved: 0, actual total: 27744, total with overprovisioning: > 27744; requested cpu:500,alloc_from_last_host?:false > ,considerReservedCapacity?: true > 2014-03-22 22:47:28,913 DEBUG [cloud.capacity.CapacityManagerImpl] > (consoleproxy-1:FirstFitRoutingAllocator) STATS: Can alloc MEM from host: > 1, used: 0, reserved: 0, total: 3773286656; requested mem: > 1073741824,alloc_from_last_host?:false ,considerReservedCapacity?: true > 2014-03-22 22:47:28,913 DEBUG [allocator.impl.FirstFitAllocator] > (consoleproxy-1:FirstFitRoutingAllocator) Found a suitable host, adding to > list: 1 > 2014-03-22 22:47:28,913 DEBUG [allocator.impl.FirstFitAllocator] > (consoleproxy-1:FirstFitRoutingAllocator) Host Allocator returning 1 > suitable hosts > 2014-03-22 22:47:28,915 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) Checking suitable pools for volume (Id, Type): > (1,ROOT) > 2014-03-22 22:47:28,915 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) We need to allocate new storagepool for this volume > 2014-03-22 22:47:28,915 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) Calling StoragePoolAllocators to find suitable pools > 2014-03-22 22:47:28,915 DEBUG > [storage.allocator.LocalStoragePoolAllocator] (consoleproxy-1:null) > LocalStoragePoolAllocator trying to find storage pool to fit the vm > 2014-03-22 22:47:28,917 DEBUG > [storage.allocator.LocalStoragePoolAllocator] (consoleproxy-1:null) > LocalStoragePoolAllocator returning 0 suitable storage pools > 2014-03-22 22:47:28,917 DEBUG > [storage.allocator.ClusterScopeStoragePoolAllocator] (consoleproxy-1:null) > ClusterScopeStoragePoolAllocator looking for storage pool > 2014-03-22 22:47:28,917 DEBUG > [storage.allocator.ZoneWideStoragePoolAllocator] (consoleproxy-1:null) > ZoneWideStoragePoolAllocator to find storage pool > 2014-03-22 22:47:28,917 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) No suitable pools found for volume: Vol[1|vm=1|ROOT] > under cluster: 1 > 2014-03-22 22:47:28,918 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) No suitable pools found > 2014-03-22 22:47:28,918 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) No suitable storagePools found under this Cluster: 1 > 2014-03-22 22:47:28,919 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (consoleproxy-1:null) Could not find suitable Deployment Destination for > this VM under any clusters, returning. > 2014-03-22 22:47:28,919 DEBUG [cloud.deploy.FirstFitPlanner] > (consoleproxy-1:null) Searching all possible resources under this Zone: 1 > 2014-03-22 22:47:28,920 DEBUG [cloud.deploy.FirstFitPlanner] > (consoleproxy-1:null) Listing clusters in order of aggregate capacity, that > have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 > 2014-03-22 22:47:28,924 DEBUG [cloud.deploy.FirstFitPlanner] > (consoleproxy-1:null) Removing from the clusterId list these clusters from > avoid set: [1] > 2014-03-22 22:47:28,924 DEBUG [cloud.deploy.FirstFitPlanner] > (consoleproxy-1:null) No clusters found after removing disabled clusters > and clusters in avoid list, returning. > 2014-03-22 22:47:28,930 DEBUG [cloud.capacity.CapacityManagerImpl] > (consoleproxy-1:null) VM state transitted from :Starting to Stopped with > event: OperationFailedvm's original host id: null new host id: null host id > before state transition: null > 2014-03-22 22:47:28,933 WARN [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) 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.advanceStart(VirtualMachineManagerImpl.java:841) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:570) > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556) > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:928) > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1672) > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157) > at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > 2014-03-22 22:47:29,941 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers to update status. > 2014-03-22 22:47:29,945 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. > 2014-03-22 22:47:35,105 DEBUG [host.dao.HostDaoImpl] > (ClusteredAgentManager Timer:null) Resetting hosts suitable for reconnect > 2014-03-22 22:47:35,106 DEBUG [host.dao.HostDaoImpl] > (ClusteredAgentManager Timer:null) Completed resetting hosts suitable for > reconnect > 2014-03-22 22:47:35,106 DEBUG [host.dao.HostDaoImpl] > (ClusteredAgentManager Timer:null) Acquiring hosts for clusters already > owned by this management server > 2014-03-22 22:47:35,107 DEBUG [host.dao.HostDaoImpl] > (ClusteredAgentManager Timer:null) Completed acquiring hosts for clusters > already owned by this management server > 2014-03-22 22:47:35,107 DEBUG [host.dao.HostDaoImpl] > (ClusteredAgentManager Timer:null) Acquiring hosts for clusters not owned > by any management server > 2014-03-22 22:47:35,108 DEBUG [host.dao.HostDaoImpl] > (ClusteredAgentManager Timer:null) Completed acquiring hosts for clusters > not owned by any management server > 2014-03-22 22:47:58,729 DEBUG > [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 > is ready to launch secondary storage VM > 2014-03-22 22:47:58,744 INFO > [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) > No running secondary storage vms found in datacenter id=1, starting one > 2014-03-22 22:47:58,760 INFO > [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Found > a stopped secondary storage vm, bring it up to running pool. secStorageVm > vm id : 108 > 2014-03-22 22:47:58,782 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Stopped to Starting with > event: StartRequestedvm's original host id: null new host id: null host id > before state transition: null > 2014-03-22 22:47:58,782 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) Successfully transitioned to start state for > VM[SecondaryStorageVm|s-108-VM] reservation id = > 18559088-89bb-4647-bad8-bf23e3ec8122 > 2014-03-22 22:47:58,786 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) Trying to deploy VM, vm has dcId: 1 and podId: null > 2014-03-22 22:47:58,786 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) Deploy avoids pods: null, clusters: null, hosts: null > 2014-03-22 22:47:58,788 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) Deploy avoids pods: null, clusters: null, hosts: null > 2014-03-22 22:47:58,789 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) DeploymentPlanner allocation algorithm: > com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_c03f8c9@27cf6eb9 > 2014-03-22 22:47:58,789 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) Trying to allocate a host and storage pools from dc:1, > pod:null,cluster:null, requested cpu: 500, requested ram: 268435456 > 2014-03-22 22:47:58,789 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (secstorage-1:null) Is ROOT volume READY (pool already allocated)?: No > 2014-03-22 22:47:58,789 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) Searching all possible resources under this Zone: 1 > 2014-03-22 22:47:58,790 DEBUG [cloud.deploy.FirstFitPlanner] > (secstorage-1:null) Listing clusters in order of aggregate capacity, that > have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 > > > > > -- > Best Regards > > > > -- Best Regards
