玩死人不偿命的CLOUDSTACK

玩过CLOUDSTACK(CS)的人,一定不会陌生下面的LOG:

2013-12-27 18:26:43,861 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-35:job-35 = [ e1ebce9d-18d7-4cf0-98de-22399a6ec49e ] FirstFitRoutingAllocator) Host name: xenserver-PHL1, hostId: 2 is in avoid set, skipping this and trying other available hosts

 

[root@cscontroller01 ~]# cat  /var/log/cloudstack/management/management-server.log|egrep ‘exception|unable|fail|invalid|leak|warn|error’

2014-04-06 10:02:25,538 DEBUG [c.c.v.UserVmManagerImpl] (Job-Executor-14:ctx-e7a720a9 ctx-4439442c) Destroying vm VM[User|centos64] as it failed to create on Host with Id:null
2014-04-06 10:02:25,593 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-14:ctx-e7a720a9) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to insufficient capacity
Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|centos64]Scope=interface com.cloud.dc.DataCenter; id=1
2014-04-06 10:02:25,597 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-14:ctx-e7a720a9) Complete async job-18, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{“uuidList”:[],”errorcode”:530,”errortext”:”Unable to start a VM due to insufficient capacity”}

INFO  [c.c.a.ApiServer] (catalina-exec-13:ctx-a070bab6 ctx-f5c3b729) Authentication error
INFO  [c.c.r.ResourceManagerImpl] (catalina-exec-6:ctx-ae25920d ctx-392c7d67) Trying to add a new host at http://10.15.200.12 in data center 1
WARN  [c.c.u.n.Link] (AgentManager-Selector:null) SSL: Fail to find the generated keystore. Loading fail-safe one to continue.
INFO  [c.c.n.s.SecurityGroupListener] (AgentConnectTaskPool-1:ctx-bd7c7342) Received a host startup notification
INFO  [c.c.n.s.SecurityGroupListener] (AgentConnectTaskPool-1:ctx-bd7c7342) Scheduled network rules cleanup, interval=1976
INFO  [c.c.n.s.SecurityGroupListener] (AgentConnectTaskPool-1:ctx-bd7c7342) Received a host startup notification
INFO  [c.c.a.ApiServer] (catalina-exec-8:ctx-cff2473a ctx-2b8f64e0) zone wide storage pool is not supported for hypervisor type undefined
INFO  [c.c.a.ApiServer] (catalina-exec-12:ctx-ecf66584 ctx-f4aedae5) zone wide storage pool is not supported for hypervisor type undefined
INFO  [c.c.a.ApiServer] (catalina-exec-20:ctx-d4cc92b9 ctx-3c36bc30) zone wide storage pool is not supported for hypervisor type undefined
INFO  [o.a.c.s.d.p.DefaultHostListener] (catalina-exec-16:ctx-cafd071d ctx-0c6aea0d) Connection established between org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@19c2544d host + 1
INFO  [o.a.c.s.d.l.CloudStackImageStoreLifeCycleImpl] (catalina-exec-14:ctx-c782a320 ctx-b8ee3e6d) Trying to add a new data store at nfs://10.15.200.15/export/secondary to data center 1
INFO  [c.c.c.ConfigurationManagerImpl] (catalina-exec-2:ctx-08699631 ctx-ce7df1d2) 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.s.PremiumSecondaryStorageManagerImpl] (secstorage-1:ctx-678bb08f) No running secondary storage vms found in datacenter id=1, starting one
INFO  [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-678bb08f) No stopped secondary storage vm is available, need to allocate a new secondary storage vm
INFO  [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-86f1f6c9) No stopped console proxy is available, need to allocate a new console proxy
WARN  [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-86f1f6c9) Exception while trying to start console proxy
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[ConsoleProxy|v-2-VM]Scope=interface com.cloud.dc.DataCenter; id=1

2014-04-07 15:18:47,515 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) VM state transitted from :Starting to Starting with event: OperationRetryvm’s original host id: null new host id: 1 host id before state transition: null
2014-04-07 15:18:47,529 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Hosts’s actual total CPU: 57456 and CPU after applying overprovisioning: 57456
2014-04-07 15:18:47,529 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) We are allocating VM, increasing the used capacity of this host:1
2014-04-07 15:18:47,529 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Current Used CPU: 2500 , Free CPU:54956 ,Requested CPU: 1000
2014-04-07 15:18:47,530 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Current Used RAM: 2818572288 , Free RAM:149442248704 ,Requested RAM: 1073741824
2014-04-07 15:18:47,530 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) CPU STATS after allocation: for host: 1, old used: 2500, old reserved: 0, actual total: 57456, total with overprovisioning: 57456; new used:3500, reserved:0; requested cpu:1000,alloc_from_last:false
2014-04-07 15:18:47,530 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) RAM STATS after allocation: for host: 1, old used: 2818572288, old reserved: 0, total: 152260820992; new used: 3892314112, reserved: 0; requested mem: 1073741824,alloc_from_last:false
2014-04-07 15:18:47,533 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) VM is being created in podId: 1
2014-04-07 15:18:47,543 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Network id=204 is already implemented
2014-04-07 15:18:47,570 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Changing active number of nics for network id=204 on 1
2014-04-07 15:18:47,576 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Asking VirtualRouter to prepare for Nic[12-5-48153f75-135d-4d61-a46a-ddabcf5d42bd-10.15.200.105]
2014-04-07 15:18:47,588 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Lock is acquired for network id 204 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type–>Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(5|ROOT–>Pool(1))]
2014-04-07 15:18:47,591 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Lock is released for network id 204 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type–>Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(5|ROOT–>Pool(1))]
2014-04-07 15:18:47,619 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (Job-Executor-9:ctx-b21fb5e3 ctx-e574d838) Applying dhcp entry in network Ntwk[204|Guest|6]

 

~~~~~~~~~~~~

继上次的几个点之后,又有几个点要指:

A,如果用高级模式,公网IP一定要够,要不然,故障百出。

B,如果是基本网络,管理IP及存储IP要够用,要不然,又故障百出。

C,千万注意CS4.3的系统虚拟机的模板版本。大约是4.2版本用2013-06-12左右的。之前的版可以用12-02什么的。但4.3,一定要用64位2014-01-14的。。不然,真的玩死人不偿命哈。。一会了AVOID SET一定资源不足之类的。

 

《玩死人不偿命的CLOUDSTACK》

《玩死人不偿命的CLOUDSTACK》

点赞