You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users-cn@cloudstack.apache.org by xusz <xu...@chinanetcenter.com> on 2015/01/04 07:19:31 UTC

SSVM启动不起来问题

 

HI ALL

虚拟化平台SSVM启动不起来,出现以下错误 ,on: Unable to get a storage network ip addressScope=interface com.cloud.dc.Pod; id=1

 

是什么意思,出现什么问题,应如何解决,多谢!

 

 

2015-01-04 14:17:11,669 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Asking VpcVirtualRouter to prepare for Nic[26426-7235-411940c2-07c2-4bf4-94f9-666998b27ef6-192.168.3.122]

2015-01-04 14:17:11,669 WARN  [network.element.VpcVirtualRouterElement] (secstorage-1:null) Network Ntwk[201|Management|2] is not associated with any VPC

2015-01-04 14:17:11,669 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Asking NiciraNvp to prepare for Nic[26426-7235-411940c2-07c2-4bf4-94f9-666998b27ef6-192.168.3.122]

2015-01-04 14:17:11,670 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Lock is acquired for network id 203 as a part of network implement

2015-01-04 14:17:11,670 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Network id=203 is already implemented

2015-01-04 14:17:11,671 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Lock is released for network id 203 as a part of network implement

2015-01-04 14:17:11,713 DEBUG [db.Transaction.Transaction] (secstorage-1:null) Rolling back the transaction: Time = 1 Name =  -SystemVmLoadScanner$1.run:71-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; called by -Transaction.rollback:887-StorageNetworkIpAddressDaoImpl.takeIpAddress:94-DatabaseCallback.intercept:34-StorageNetworkManagerImpl.acquireIpAddress:347-StorageNetworkGuru.reserve:130-NetworkManagerImpl.prepareNic:2143-NetworkManagerImpl.prepare:2113-VirtualMachineManagerImpl.advanceStart:752-VirtualMachineManagerImpl.start:472-VirtualMachineManagerImpl.start:465-SecondaryStorageManagerImpl.startSecStorageVm:257-SecondaryStorageManagerImpl.allocCapacity:684

2015-01-04 14:17:11,716 DEBUG [db.Transaction.Transaction] (secstorage-1:null) Rolling back the transaction: Time = 1 Name =  -SystemVmLoadScanner$1.run:71-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; called by -Transaction.rollback:887-StorageNetworkIpAddressDaoImpl.takeIpAddress:94-DatabaseCallback.intercept:34-StorageNetworkManagerImpl.acquireIpAddress:347-StorageNetworkGuru.reserve:130-NetworkManagerImpl.prepareNic:2143-NetworkManagerImpl.prepare:2113-VirtualMachineManagerImpl.advanceStart:752-VirtualMachineManagerImpl.start:472-VirtualMachineManagerImpl.start:465-SecondaryStorageManagerImpl.startSecStorageVm:257-SecondaryStorageManagerImpl.allocCapacity:684

2015-01-04 14:17:11,717 INFO  [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Insufficient capacity 

com.cloud.exception.InsufficientAddressCapacityException: Unable to get a storage network ip addressScope=interface com.cloud.dc.Pod; id=1


Re: SSVM启动不起来问题

Posted by "linuxbqj@gmail.com" <li...@gmail.com>.
看错误是因为网络的原因引起的
建议检查下网络是不是通的

另外提问题的时候,建议说明下基本架构信息,方便其他人分析

2015-01-04 14:19 GMT+08:00 xusz <xu...@chinanetcenter.com>:
>
>
> HI ALL
>
> 虚拟化平台SSVM启动不起来,出现以下错误 ,on: Unable to get a storage network ip addressScope=interface com.cloud.dc.Pod; id=1
>
>
>
> 是什么意思,出现什么问题,应如何解决,多谢!
>
>
>
>
>
> 2015-01-04 14:17:11,669 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Asking VpcVirtualRouter to prepare for Nic[26426-7235-411940c2-07c2-4bf4-94f9-666998b27ef6-192.168.3.122]
>
> 2015-01-04 14:17:11,669 WARN  [network.element.VpcVirtualRouterElement] (secstorage-1:null) Network Ntwk[201|Management|2] is not associated with any VPC
>
> 2015-01-04 14:17:11,669 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Asking NiciraNvp to prepare for Nic[26426-7235-411940c2-07c2-4bf4-94f9-666998b27ef6-192.168.3.122]
>
> 2015-01-04 14:17:11,670 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Lock is acquired for network id 203 as a part of network implement
>
> 2015-01-04 14:17:11,670 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Network id=203 is already implemented
>
> 2015-01-04 14:17:11,671 DEBUG [cloud.network.NetworkManagerImpl] (secstorage-1:null) Lock is released for network id 203 as a part of network implement
>
> 2015-01-04 14:17:11,713 DEBUG [db.Transaction.Transaction] (secstorage-1:null) Rolling back the transaction: Time = 1 Name =  -SystemVmLoadScanner$1.run:71-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; called by -Transaction.rollback:887-StorageNetworkIpAddressDaoImpl.takeIpAddress:94-DatabaseCallback.intercept:34-StorageNetworkManagerImpl.acquireIpAddress:347-StorageNetworkGuru.reserve:130-NetworkManagerImpl.prepareNic:2143-NetworkManagerImpl.prepare:2113-VirtualMachineManagerImpl.advanceStart:752-VirtualMachineManagerImpl.start:472-VirtualMachineManagerImpl.start:465-SecondaryStorageManagerImpl.startSecStorageVm:257-SecondaryStorageManagerImpl.allocCapacity:684
>
> 2015-01-04 14:17:11,716 DEBUG [db.Transaction.Transaction] (secstorage-1:null) Rolling back the transaction: Time = 1 Name =  -SystemVmLoadScanner$1.run:71-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; called by -Transaction.rollback:887-StorageNetworkIpAddressDaoImpl.takeIpAddress:94-DatabaseCallback.intercept:34-StorageNetworkManagerImpl.acquireIpAddress:347-StorageNetworkGuru.reserve:130-NetworkManagerImpl.prepareNic:2143-NetworkManagerImpl.prepare:2113-VirtualMachineManagerImpl.advanceStart:752-VirtualMachineManagerImpl.start:472-VirtualMachineManagerImpl.start:465-SecondaryStorageManagerImpl.startSecStorageVm:257-SecondaryStorageManagerImpl.allocCapacity:684
>
> 2015-01-04 14:17:11,717 INFO  [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Insufficient capacity
>
> com.cloud.exception.InsufficientAddressCapacityException: Unable to get a storage network ip addressScope=interface com.cloud.dc.Pod; id=1
>



-- 
白清杰 (Born Bai)

Mail: linuxbqj@gmail.com