答复: xenserver添加的存储找不到磁盘镜盘问题

2014-10-07 文章



还没有,还是存在问题,在xenserver添加存储提示the vdi is not aviable


-邮件原件-
发件人: users-cn-return-4009-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-4009-xusz=chinanetcenter@cloudstack.apache.org] 代表 
Guo Star
发送时间: 2014年10月5日星期日 14:25
收件人: users-cn@cloudstack.apache.org
主题: Re: xenserver添加的存储找不到磁盘镜盘问题

请问已经解决了? 见到xenserver有正确的设备信息? Log日志如何?

在 2014年10月3日 下午10:46,许叁征 写道:

> HI ALL
>
>   国庆快乐。
>
> 求助:公司机房出现故障,原来的ISCSI存储它无法连接了,我重新上载了一下,添加
> 成功,但是发现容量是有1T占用了,600GB左右,但是在xenserver上却无法看到
>
> 虚拟机的磁盘镜像,比如root- DATA-这样的磁盘,点了下rescan面板下,显
> 示 the vdi is not available 这是怎么回事,为何变空掉,如何解决,谢谢
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>


xenserver添加的存储找不到磁盘镜盘问题

2014-10-03 文章
HI ALL 

  国庆快乐。

求助:公司机房出现故障,原来的ISCSI存储它无法连接了,我重新上载了一下,添加
成功,但是发现容量是有1T占用了,600GB左右,但是在xenserver上却无法看到

虚拟机的磁盘镜像,比如root- DATA-这样的磁盘,点了下rescan面板下,显
示 the vdi is not available 这是怎么回事,为何变空掉,如何解决,谢谢

 

 

 

 

 

 

 



cs环境下的虚拟机备份

2014-04-29 文章
 

HI ALL 

  目前虚拟机使用XENserver +CS

,现在转为本地存储,这些虚拟机如何作备份,大家有什么自己的心得?phdvirtual导
入ova发现网卡配置了IP,网络一直不通,这个问题有人碰过吗,求指导

 

 

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



cloudstack能否接受已格式化的EXT3 ISCSI存储空间

2014-04-22 文章
 HI ALL
   目前想需要备份CS的ISCSI的数据,由于使用XENserver,免费版本,
  1.什么办法可以备份xenserver主机内的虚拟机?
  2. cloudstack能否接受已格式化的EXT3 ISCSI存储空间?



答复: 答复: 二级存储丢失

2014-04-17 文章

目前 使用的环境 是CS主机具有虚拟机文件,全为home目录下,
那这个CS备用机器/home目录下是不是也要同步,这个同步是如何用的同步?。



 



-邮件原件-
发件人: users-cn-return-3501-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3501-xusz=chinanetcenter@cloudstack.apache.org] 代表 
ganglin_lan
发送时间: 2014年4月17日星期四 16:05
收件人: users-cn
主题: Re: 答复: 二级存储丢失

cloudstack高可用可以配置cloudstack slave 
服务器,正常安装cloudstack,初始化数据库时,不要用--deploy-as参数,这样两个cloudstack就可以同时管理了,当然前面还可以加个ngiinx之类的做负载均衡,重点是mysql数据库要做主从




ganglin_lan

发件人: 许叁征
发送时间: 2014-04-17 16:02
收件人: users-cn@cloudstack.apache.org
主题: 答复: 答复: 二级存储丢失
Hi  linuxbqj 
故障修复过程,北京-steelen会发布一个恢复过程到社区里面哈,另外后面发现服务器硬盘坏了,现在又要开始迁移的过程恢复数据了。。
对了,想问大家一个问题,如何做高可用的cloudstack,就是说一台cloudstac k主机宕机机了,另一台备机cloudstac k仍能工作。
目前cloudstack能做到吗?如果有,可有推荐的解决方案链接。。求解。谢谢






-邮件原件-
发件人: users-cn-return-3491-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3491-xusz=chinanetcenter@cloudstack.apache.org] 代表 
linux...@gmail.com
发送时间: 2014年4月16日星期三 15:11
收件人: users-cn@cloudstack.apache.org
主题: Re: 答复: 二级存储丢失

hey 叁征,是否可以把你的解决过程整理一个文章发布到社区网站呢

2014-04-16 14:12 GMT+08:00 Royal Yang :
> 添加一个服务方案,勾选高可用,将虚拟机的服务方案更改为这个新建的方案。当host故障的时候应用此方案的虚拟机就能自动启动了
>
>
> 2014-04-16 13:23 GMT+08:00 许叁征 :
>
>>
>>
>>  
>> 二级存储是使用NFS的,后面经“北京-steelen”的协助支持下,启用本地存储后经相应检查后,虚拟机多数可以启动了。在这里面要特别感谢下steelen,来到厦门的时候,记得告诉我,请你吃大餐以表心意,
>>  目前有两个问题,在平时中一直困扰的。
>> 1.使用两台XENserver为一个pool集群后,xenserver,有自时它会自动在XEN面板上变红色图标,然后节点会自动消失,一台xenserver
>> 就会ping不通掉,看起来是机器在重启了。这样就造成虚拟机也瞬间停止运行了。。隔了2分钟后,它会可能会自动加载成同一个pool。
>>1.1想问下各位,造成这个问题的原因是什么,如何处理?
>>1.2 如何在节点故障恢复后,虚拟机也能自动启动起来免人工手动启动。
>> 谢谢大家了。
>>
>>
>> -邮件原件-
>> 发件人: 
>> users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org[mailto:
>> users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org] 代表
>> linux...@gmail.com
>> 发送时间: 2014年4月16日星期三 7:49
>> 收件人: users-cn@cloudstack.apache.org
>> 主题: Re: 二级存储丢失
>>
>> 二级存储是使用的iscsi还是NFS呢?
>>
>> 二级存储手动挂载有没有问题?看日志,分析是二级存储挂载不上
>>
>>
>> 2014-04-15 10:18 GMT+08:00 许叁征 :
>>
>> >   HI ALL
>> >
>> >  最近一节点因为innode文件满了,造成虚拟机挺止,修复好节点却发现虚拟机无法启动,
>> >
>> > 环境:CS4.0.1 +XENSERVER。
>> >
>> >  添加了XEN主存储还是不能启动虚拟机。
>> >
>> > 2014-04-15 10:12:48,114 DEBUG
>> > [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) Unable
>> to
>> > find storage pool to fit the vm
>> >
>> > 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) No suitable pools found for volume:
>> > Vol[67635|vm=67556|ROOT] under cluster: 20
>> >
>> > 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) No suitable pools found
>> >
>> > 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) No suitable storagePools found under this Cluster: 20
>> >
>> > 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) Checking resources in Cluster: 1 under Pod: 1
>> >
>> > 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) Calling HostAllocators to find suitable hosts
>> >
>> > 2014-04-15 10:12:48,115 DEBUG [allocator.impl.FirstFitAllocator]
>> > (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1  pod:1
>> > cluster:1
>> >
>> > 2014-04-15 10:12:48,117 DEBUG [allocator.impl.FirstFitAllocator]
>> > (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to
>> > check for allocation: [Host[-68-Routing]]
>> >
>> > 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator]
>> > (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for allocation
>> after
>> > prioritization: [Host[-68-Routing]]
>> >
>> > 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator]
>> > (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=256
>> >
>> > 2014-04-15 10:12:48,120 DEBUG [cloud.capacity.CapacityManagerImpl]
>> > (secstorage-1:FirstFitRoutingAllocator) Checking if host: 68 has enough
>> > capacity for requested CPU: 500 and requested RAM: 268435456 ,
>> > cpuOverprovisioningFactor: 6.0
>> >
>> > 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
>> > (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 34128
>> and
>> > CPU after applying overprovisioning: 204768
>> >
>> > 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
>> > 

答复: 答复: 二级存储丢失

2014-04-17 文章
Hi  linuxbqj 
故障修复过程,北京-steelen会发布一个恢复过程到社区里面哈,另外后面发现服务器硬盘坏了,现在又要开始迁移的过程恢复数据了。。
对了,想问大家一个问题,如何做高可用的cloudstack,就是说一台cloudstac k主机宕机机了,另一台备机cloudstac k仍能工作。
目前cloudstack能做到吗?如果有,可有推荐的解决方案链接。。求解。谢谢


 



-邮件原件-
发件人: users-cn-return-3491-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3491-xusz=chinanetcenter@cloudstack.apache.org] 代表 
linux...@gmail.com
发送时间: 2014年4月16日星期三 15:11
收件人: users-cn@cloudstack.apache.org
主题: Re: 答复: 二级存储丢失

hey 叁征,是否可以把你的解决过程整理一个文章发布到社区网站呢

2014-04-16 14:12 GMT+08:00 Royal Yang :
> 添加一个服务方案,勾选高可用,将虚拟机的服务方案更改为这个新建的方案。当host故障的时候应用此方案的虚拟机就能自动启动了
>
>
> 2014-04-16 13:23 GMT+08:00 许叁征 :
>
>>
>>
>>  
>> 二级存储是使用NFS的,后面经“北京-steelen”的协助支持下,启用本地存储后经相应检查后,虚拟机多数可以启动了。在这里面要特别感谢下steelen,来到厦门的时候,记得告诉我,请你吃大餐以表心意,
>>  目前有两个问题,在平时中一直困扰的。
>> 1.使用两台XENserver为一个pool集群后,xenserver,有自时它会自动在XEN面板上变红色图标,然后节点会自动消失,一台xenserver
>> 就会ping不通掉,看起来是机器在重启了。这样就造成虚拟机也瞬间停止运行了。。隔了2分钟后,它会可能会自动加载成同一个pool。
>>1.1想问下各位,造成这个问题的原因是什么,如何处理?
>>1.2 如何在节点故障恢复后,虚拟机也能自动启动起来免人工手动启动。
>> 谢谢大家了。
>>
>>
>> -邮件原件-
>> 发件人: 
>> users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org[mailto:
>> users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org] 代表
>> linux...@gmail.com
>> 发送时间: 2014年4月16日星期三 7:49
>> 收件人: users-cn@cloudstack.apache.org
>> 主题: Re: 二级存储丢失
>>
>> 二级存储是使用的iscsi还是NFS呢?
>>
>> 二级存储手动挂载有没有问题?看日志,分析是二级存储挂载不上
>>
>>
>> 2014-04-15 10:18 GMT+08:00 许叁征 :
>>
>> >   HI ALL
>> >
>> >  最近一节点因为innode文件满了,造成虚拟机挺止,修复好节点却发现虚拟机无法启动,
>> >
>> > 环境:CS4.0.1 +XENSERVER。
>> >
>> >  添加了XEN主存储还是不能启动虚拟机。
>> >
>> > 2014-04-15 10:12:48,114 DEBUG
>> > [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) Unable
>> to
>> > find storage pool to fit the vm
>> >
>> > 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) No suitable pools found for volume:
>> > Vol[67635|vm=67556|ROOT] under cluster: 20
>> >
>> > 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) No suitable pools found
>> >
>> > 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) No suitable storagePools found under this Cluster: 20
>> >
>> > 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) Checking resources in Cluster: 1 under Pod: 1
>> >
>> > 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner]
>> > (secstorage-1:null) Calling HostAllocators to find suitable hosts
>> >
>> > 2014-04-15 10:12:48,115 DEBUG [allocator.impl.FirstFitAllocator]
>> > (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1  pod:1
>> > cluster:1
>> >
>> > 2014-04-15 10:12:48,117 DEBUG [allocator.impl.FirstFitAllocator]
>> > (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to
>> > check for allocation: [Host[-68-Routing]]
>> >
>> > 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator]
>> > (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for allocation
>> after
>> > prioritization: [Host[-68-Routing]]
>> >
>> > 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator]
>> > (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=256
>> >
>> > 2014-04-15 10:12:48,120 DEBUG [cloud.capacity.CapacityManagerImpl]
>> > (secstorage-1:FirstFitRoutingAllocator) Checking if host: 68 has enough
>> > capacity for requested CPU: 500 and requested RAM: 268435456 ,
>> > cpuOverprovisioningFactor: 6.0
>> >
>> > 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
>> > (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 34128
>> and
>> > CPU after applying overprovisioning: 204768
>> >
>> > 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
>> > (secstorage-1:FirstFitRoutingAllocator) Free CPU: 204768 , Requested CPU:
>> > 500
>> >
>> > 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
>> > (secstorage-1:FirstFitRoutingAllocator) Free RAM: 24472994112 , Requested
>> > RAM: 268435456
>> >
>> > 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
>> > (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM
>> > available
>> >
>> > 2014-04-15 10:12:48,122 DEBUG [cloud.ca

答复: 二级存储丢失

2014-04-15 文章

 
二级存储是使用NFS的,后面经“北京-steelen”的协助支持下,启用本地存储后经相应检查后,虚拟机多数可以启动了。在这里面要特别感谢下steelen,来到厦门的时候,记得告诉我,请你吃大餐以表心意,
 目前有两个问题,在平时中一直困扰的。
1.使用两台XENserver为一个pool集群后,xenserver,有自时它会自动在XEN面板上变红色图标,然后节点会自动消失,一台xenserver 
就会ping不通掉,看起来是机器在重启了。这样就造成虚拟机也瞬间停止运行了。。隔了2分钟后,它会可能会自动加载成同一个pool。 
   1.1想问下各位,造成这个问题的原因是什么,如何处理?
   1.2 如何在节点故障恢复后,虚拟机也能自动启动起来免人工手动启动。
谢谢大家了。


-邮件原件-
发件人: users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org] 代表 
linux...@gmail.com
发送时间: 2014年4月16日星期三 7:49
收件人: users-cn@cloudstack.apache.org
主题: Re: 二级存储丢失

二级存储是使用的iscsi还是NFS呢?

二级存储手动挂载有没有问题?看日志,分析是二级存储挂载不上


2014-04-15 10:18 GMT+08:00 许叁征 :

>   HI ALL
>
>  最近一节点因为innode文件满了,造成虚拟机挺止,修复好节点却发现虚拟机无法启动,
>
> 环境:CS4.0.1 +XENSERVER。
>
>  添加了XEN主存储还是不能启动虚拟机。
>
> 2014-04-15 10:12:48,114 DEBUG
> [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) Unable to
> find storage pool to fit the vm
>
> 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
> (secstorage-1:null) No suitable pools found for volume:
> Vol[67635|vm=67556|ROOT] under cluster: 20
>
> 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
> (secstorage-1:null) No suitable pools found
>
> 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner]
> (secstorage-1:null) No suitable storagePools found under this Cluster: 20
>
> 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner]
> (secstorage-1:null) Checking resources in Cluster: 1 under Pod: 1
>
> 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner]
> (secstorage-1:null) Calling HostAllocators to find suitable hosts
>
> 2014-04-15 10:12:48,115 DEBUG [allocator.impl.FirstFitAllocator]
> (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1  pod:1
> cluster:1
>
> 2014-04-15 10:12:48,117 DEBUG [allocator.impl.FirstFitAllocator]
> (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to
> check for allocation: [Host[-68-Routing]]
>
> 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator]
> (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for allocation after
> prioritization: [Host[-68-Routing]]
>
> 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator]
> (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=256
>
> 2014-04-15 10:12:48,120 DEBUG [cloud.capacity.CapacityManagerImpl]
> (secstorage-1:FirstFitRoutingAllocator) Checking if host: 68 has enough
> capacity for requested CPU: 500 and requested RAM: 268435456 ,
> cpuOverprovisioningFactor: 6.0
>
> 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
> (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 34128 and
> CPU after applying overprovisioning: 204768
>
> 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
> (secstorage-1:FirstFitRoutingAllocator) Free CPU: 204768 , Requested CPU:
> 500
>
> 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
> (secstorage-1:FirstFitRoutingAllocator) Free RAM: 24472994112 , Requested
> RAM: 268435456
>
> 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
> (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM
> available
>
> 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
> (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 68,
> used: 0, reserved: 0, actual total: 34128, total with overprovisioning:
> 204768; requested cpu:500,alloc_from_last_host?:false
> ,considerReservedCapacity?: true
>
> 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl]
> (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 68,
> used: 0, reserved: 0, total: 24472994112; requested mem:
> 268435456,alloc_from_last_host?:false ,considerReservedCapacity?: true
>
> 2014-04-15 10:12:48,122 DEBUG [allocator.impl.FirstFitAllocator]
> (secstorage-1:FirstFitRoutingAllocator) Found a suitable host, adding to
> list: 68
>
> 2014-04-15 10:12:48,122 DEBUG [allocator.impl.FirstFitAllocator]
> (secstorage-1:FirstFitRoutingAllocator) Host Allocator returning 1 suitable
> hosts
>
> 2014-04-15 10:12:48,123 DEBUG [cloud.deploy.FirstFitPlanner]
> (secstorage-1:null) Checking suitable pools for volume (Id, Type):
> (67635,ROOT)
>
> 2014-04-15 10:12:48,124 DEBUG [cloud.deploy.FirstFitPlanner]
> (secstorage-1:null) We need to allocate new storagepool for this volume
>
> 2014-04-15 10:12:48,124 DEBUG [cloud.deploy.FirstFitPlanner]
> (secstorage-1:null) Calling StoragePoolAllocators to find suitable pools
>
> 2014-04-15 10:12:48,124 DEBUG
> [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null)
> LocalStoragePoolAllocator tryi

二级存储丢失

2014-04-14 文章
olExecutor.
java:1110)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
03)

at java.lang.Thread.run(Thread.java:679)

2014-04-15 10:12:48,277 INFO
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable
to start secondary storage vm for standby capacity, secStorageVm vm Id :
67556, will recycle it and start a new one

2014-04-15 10:12:48,277 INFO
[cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null)
Primary secondary storage is not even started, wait until next turn

2014-04-15 10:12:49,247 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers. 

2014-04-15 10:12:58,920 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) StorageCollector is running...

2014-04-15 10:12:58,923 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) There is no secondary storage VM for secondary
storage host nfs://172.16.0.130/home/share/secondary

2014-04-15 10:12:58,925 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) There is no secondary storage VM for secondary
storage host nfs://172.16.0.130/home/secondary

2014-04-15 10:12:58,933 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-55:null) Seq 68-1544683570: Executing request

2014-04-15 10:12:59,859 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-55:null) Seq 68-1544683570: Response Received: 

2014-04-15 10:12:59,859 DEBUG [agent.transport.Request]
(StatsCollector-3:null) Seq 68-1544683570: Received:  { Ans: , MgmtId:
690716573693, via: 68, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }

2014-04-15 10:12:59,864 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-133:null) Seq 68-1544683571: Executing request

^C

 

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



答复: 答复: 上海聚餐

2014-04-01 文章
什么时候也组织一次在厦门的沙龙啊。 


-邮件原件-
发件人: users-cn-return-3402-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3402-xusz=chinanetcenter@cloudstack.apache.org] 代表 
Carlos Xue - Oneasia (SH)
发送时间: 2014年4月1日星期二 16:09
收件人: users-cn@cloudstack.apache.org; cloudstack-users...@incubator.apache.org
主题: 答复: 答复: 上海聚餐

可以啊,等沙龙结束后

Best Regards

Carlos Xue
Cloud Engineer
Tel +86 3332 2375
Mobile +86 15618577265
E-mail: carlos...@oneas1a.com
www.oneas1a.com


-邮件原件-
发件人: Liu Fred [mailto:fred_...@tcloudcomputing.com]
发送时间: 2014年4月1日 星期二 下午 16:06
收件人: users-cn@cloudstack.apache.org; cloudstack-users...@incubator.apache.org
主题: Re: 答复: 上海聚餐

可以在上海沙龙后组织一场,AA,上海有同学组织吗?

在 14-4-1 下午4:02, "许叁征"  写入:

>
>我没有在上海,我在厦门,有在厦门的有兴趣来讨论行业和聚餐交流。。。
>
>
>
>
>许叁征
>网宿科技股份有限公司  厦门分公司 运营技术支持部
>
>Tel:13860125907
>E-mail:x...@chinanetcenter.com
>http://www.chinanetcenter.com
>
>分公司:北京-上海-广州-深圳
>免费咨询热线:800-820-0001
>网宿科技 --卓越的互联网业务平台提供商
>
>
>
>-邮件原件-
>发件人: users-cn-return-3397-xusz=chinanetcenter@cloudstack.apache.org
>[mailto:users-cn-return-3397-xusz=chinanetcenter.com@cloudstack.apache.
>org
>] 代表 Lu Heng
>发送时间: 2014年4月1日星期二 15:47
>收件人: cloudstack-users...@incubator.apache.org
>主题: 上海聚餐
>
>有没有在上海的朋友有兴趣聚餐的,聊聊云也聊聊行业。
>
>--
>--
>Kind regards.
>Lu
>
>This transmission is intended solely for the addressee(s) shown above.
>It may contain information that is privileged, confidential or
>otherwise protected from disclosure. Any review, dissemination or use
>of this transmission or its contents by persons other than the intended
>addressee(s) is strictly prohibited. If you have received this
>transmission in error, please notify this office immediately and e-mail
>the original at the sender's address above by replying to this message
>and including the text of the transmission received.



OneAsia DISCLAIMER: This e-mail message (including any attachment) is intended 
only for the personal use of the recipient(s) named above. This message is 
confidential and may be legally privileged. If you are not an intended 
recipient, you may not review, copy or distribute this message. If you have 
received this communication in error, please notify us immediately by e-mail 
and delete the original message. Any views or opinions expressed in this 
message are those of the author only. Furthermore, this message (including any 
attachment) does not create any legally binding rights or obligations 
whatsoever, which may only be created by the exchange of hard copy documents 
signed by a duly authorized representative of OneAsia Network Limited.


答复: 上海聚餐

2014-04-01 文章

我没有在上海,我在厦门,有在厦门的有兴趣来讨论行业和聚餐交流。。。




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 


-邮件原件-
发件人: users-cn-return-3397-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3397-xusz=chinanetcenter@cloudstack.apache.org] 代表 
Lu Heng
发送时间: 2014年4月1日星期二 15:47
收件人: cloudstack-users...@incubator.apache.org
主题: 上海聚餐

有没有在上海的朋友有兴趣聚餐的,聊聊云也聊聊行业。

-- 
--
Kind regards.
Lu

This transmission is intended solely for the addressee(s) shown above.
It may contain information that is privileged, confidential or
otherwise protected from disclosure. Any review, dissemination or use
of this transmission or its contents by persons other than the
intended addressee(s) is strictly prohibited. If you have received
this transmission in error, please notify this office immediately and
e-mail the original at the sender's address above by replying to this
message and including the text of the transmission received.


添加ISCSI存储的虚拟机出现闪退

2014-03-31 文章
 HI ALL
 最近新上两个节点XENserver,添加节点各项正常,同时也添加了ISCSI存储。
 启动虚拟机发现无法启动,资源 也够,检查二级存储发现是0.0KB 但是使用SSVM也启动正常,通过原有模板创建的也能正常创建。


问题来了,虚拟机创建一直不能成功,指定了ISCSI存储和新增的节点标签,发现在ISCSI的存储上,虚拟机启动出现一闪而过,在ISCSI存储发现它创建了文件,而后又删除掉了。
虚拟机就失败掉了。
这是怎么回事,问题要如何解决,谢谢


cloudstack平台无法打开

2014-03-25 文章
HI ALL
   昨天虚拟机平台机器宕机后,重启发现平台无法打开,cloudstack 4.0.1 以及
mysql日志报错如下:
  请教 这个要如何处理,谢谢!



[root@manager ~]#  tailf /usr/share/cloud/management/logs/management-server.
log
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
2014-03-26 10:56:26,367 INFO  [utils.component.ComponentLocator] (main:null)
Config file found at /etc/cloud/management/components.xml.  Configuring
system-integrity-checker
2014-03-26 10:56:26,372 DEBUG [utils.component.ComponentLocator] (main:null)
Looking for class com.cloud.cluster.ManagementServerNode
2014-03-26 10:56:26,391 INFO  [utils.component.ComponentLocator] (main:null)
Found component: com.cloud.utils.component.SystemIntegrityChecker in
com.cloud.cluster.ManagementServerNode - ManagementServerNode
2014-03-26 10:56:26,391 INFO  [utils.component.ComponentLocator] (main:null)
Adding system integrity checker: ManagementServerNode
2014-03-26 10:56:26,391 DEBUG [utils.component.ComponentLocator] (main:null)
Looking for class com.cloud.utils.crypt.EncryptionSecretKeyChecker
2014-03-26 10:56:26,400 INFO  [utils.component.ComponentLocator] (main:null)
Found component: com.cloud.utils.component.SystemIntegrityChecker in
com.cloud.utils.crypt.EncryptionSecretKeyChecker -
EncryptionSecretKeyChecker
2014-03-26 10:56:26,400 INFO  [utils.component.ComponentLocator] (main:null)
Adding system integrity checker: EncryptionSecretKeyChecker
2014-03-26 10:56:26,400 DEBUG [utils.component.ComponentLocator] (main:null)
Looking for class com.cloud.upgrade.DatabaseIntegrityChecker
2014-03-26 10:56:26,401 INFO  [utils.component.ComponentLocator] (main:null)
Found component: com.cloud.utils.component.SystemIntegrityChecker in
com.cloud.upgrade.DatabaseIntegrityChecker - DatabaseIntegrityChecker
2014-03-26 10:56:26,402 INFO  [utils.component.ComponentLocator] (main:null)
Adding system integrity checker: DatabaseIntegrityChecker
2014-03-26 10:56:26,402 DEBUG [utils.component.ComponentLocator] (main:null)
Looking for class com.cloud.upgrade.PremiumDatabaseUpgradeChecker
2014-03-26 10:56:26,403 INFO  [utils.component.ComponentLocator] (main:null)
Found component: com.cloud.utils.component.SystemIntegrityChecker in
com.cloud.upgrade.PremiumDatabaseUpgradeChecker - DatabaseUpgradeChecker
2014-03-26 10:56:26,403 INFO  [utils.component.ComponentLocator] (main:null)
Adding system integrity checker: DatabaseUpgradeChecker
2014-03-26 10:56:26,474 DEBUG [utils.crypt.EncryptionSecretKeyChecker]
(main:null) Encryption Type: file
2014-03-26 10:56:26,557 INFO  [cloud.upgrade.DatabaseIntegrityChecker]
(main:null) Grabbing lock to check for database integrity.
2014-03-26 10:56:30,774 ERROR [db.Transaction.Transaction] (main:null)
Unexpected exception: 
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could
not create connection to database server. Attempted reconnect 3 times.
Giving up.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
sorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
torAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1013)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:927)
at
com.mysql.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:2238)
at
com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2159)
at com.mysql.jdbc.ConnectionImpl.(ConnectionImpl.java:792)
at com.mysql.jdbc.JDBC4Connection.(JDBC4Connection.java:49)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
sorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
torAccessorImpl.java:45)
at java.lang.reflect.Co

答复: 答复: 取消维护ISCSI存储提示错误

2014-03-21 文章

是的,存储出问题, 不过存储问题已解决。之前把xenserver 
的ISCSI不小心给forget掉了,现在找不到这个磁盘,重新通过XENserver面板添加的ISCSI可以显示name 
35510305-6f6f-3ca0-90ae-797b47b29ae3
但是UUID却不能变成原来XENserver“4e2cc197-fdec-5688-131a-746e0fc16262” 
尝试以下办法 添加 提示出错,有什么办法 可以恢复cloudstack正常连接xenserver上的iscsi, ?让原来的使用iscsi存储启动起来。

[root@xen122 ~]#  xe pbd-create sr-uuid=4e2cc197-fdec-5688-131a-746e0fc16262 
host-uuid=ea339c35-2574-4813-b873-35c24f47e5e1 
device-config:target=192.168.0.28 
device-config:targetIQN=iqn.2014-01.net.xsz:iscsi.disk0-target 
device-config:SCSIlid=35510305-6f6f-3ca0-90ae-797b47b29ae3
The uuid you supplied was invalid.
type: SR
uuid: 4e2cc197-fdec-5688-131a-746e0fc16262

许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: users-cn-return-3281-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3281-xusz=chinanetcenter@cloudstack.apache.org] 代表 
ganglin_lan
发送时间: 2014年3月21日星期五 16:46
收件人: users-cn
主题: Re: 答复: 取消维护ISCSI存储提示错误

这应该不是cloudstack的问题,存储出问题了




ganglin_lan

发件人: 许叁征
发送时间: 2014-03-21 16:27
收件人: users-cn@cloudstack.apache.org
主题: 答复: 取消维护ISCSI存储提示错误
贴一下详细的日志,供大家分析下




Task failed! Task record: uuid: 
513c8151-9139-7a39-6b24-0dedd5def7db
   nameLabel: Async.VM.start_on
 nameDescription: 
   allowedOperations: []
   currentOperations: {}
 created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
  status: FAILURE
  residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: 
  result: 
   errorInfo: [VM_REQUIRES_SR, 
OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, 
OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
 otherConfig: {}
   subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []

at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3142)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3254)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at 
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN  [xen.resource.CitrixResourceBase] 
(DirectAgent-193:null) Catch Exception: class 
com.cloud.utils.exception.CloudRuntimeException due to 
com.cloud.utils.exception.CloudRuntimeException: Unable to start 
VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task 
failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
   nameLabel: Async.VM.start_on
 nameDescription: 
   allowedOperations: []
   currentOperations: {}
 created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
  status: FAILURE
  residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: 
  result: 
   errorInfo: [VM_REQUIRES_SR, 
OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, 
OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
 otherConfig: {}
   subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []

com.cloud.utils.exception.CloudRuntimeException: Unable to start 
VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task 
failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
   nameLabel: Async.VM.start_on
 nameDescription: 
   allowedOperations: []
   currentOperations: {}
 created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
  status: FAILURE
  residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: 
  result: 
   errorInfo: [VM_REQUIRES_SR, 
OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861, 
OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
 otherConfig: {}
   subtaskOf: com.xensource.xenapi.Task@aaf13f6f

答复: 取消维护ISCSI存储提示错误

2014-03-21 文章
irstFitPlanner] 
(Job-Executor-10:job-738) Could not find suitable Deployment Destination for 
this VM under any clusters, returning. 
2014-03-21 16:25:13,599 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-10:job-738) VM state transitted from :Starting to Stopped with 
event: OperationFailedvm's original host id: 66 new host id: null host id 
before state transition: 66
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-10:job-738) Hosts's actual total CPU: 36256 and CPU after 
applying overprovisioning: 217536
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-10:job-738) release cpu from host: 66, old used: 4000,reserved: 
14000, actual total: 36256, total with overprovisioning: 217536; new used: 
2000,reserved:14000; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,604 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-10:job-738) release mem from host: 66, old used: 
4294967296,reserved: 16106127360, total: 24472994112; new used: 
2147483648,reserved:16106127360; movedfromreserved: false,moveToReserveredfalse
2014-03-21 16:25:13,691 WARN  [cloud.storage.StorageManagerImpl] 
(Job-Executor-10:job-738) There was an error starting the user vm id: 64691 on 
storage pool, cannot complete primary storage maintenance
com.cloud.exception.InsufficientServerCapacityException: Unable to create a 
deployment for VM[User|test6]Scope=interface com.cloud.dc.DataCenter; id=1
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:597)
at 
com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2815)
at 
com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at 
com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at 
com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at 
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,742 ERROR [cloud.api.ApiDispatcher] 
(Job-Executor-10:job-738) Exception while executing 
CancelPrimaryStorageMaintenanceCmd:
java.lang.ClassCastException: com.cloud.utils.exception.ExecutionException 
cannot be cast to com.cloud.exception.ResourceUnavailableException
at 
com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:2848)
at 
com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at 
com.cloud.storage.StorageManagerImpl.cancelPrimaryStorageForMaintenance(StorageManagerImpl.java:215)
at 
com.cloud.api.commands.CancelPrimaryStorageMaintenanceCmd.execute(CancelPrimaryStorageMaintenanceCmd.java:105)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at 
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 
530, result: Error Code: 530 Error text: 
com.cloud.utils.exception.ExecutionException cannot be cast to 
com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:13,743 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-10:job-738) Complete async job-738, jobStatus: 2, resultCode: 
530, result: Error Code: 530 Error text: 
com.cloud.utils.exception.ExecutionException cannot be cast to 
com.cloud.exception.ResourceUnavailableException
2014-03-21 16:25:14,546 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-3:null) Async job-738 completed
2014-03-21 16:25:15,133 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-7:null) Async job-731 completed
2014-03-21 16:25:15,995 DEBUG [storage.secondary.SecondaryStorageManagerImpl] 
(sec

答复: Re: 物理主机上能做NFS共享吗

2014-03-20 文章


好,大家一起来解决问题,不过我现在发现是ISCSI服务端发布的存储存在问题,主机找不到虚拟机磁盘组,一直是I/O错误 ,。
Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 
4096 167480688640, Input/output error 
Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 
512 1151535746560, Input/output error 
Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0xafa1500 28 -1 
512 1151539949056, Input/output error 
Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 
512 1151535746560, Input/output error 
Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 
4096 166025674752, Input/output error 
Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 
4096 166025674752, Input/output error 
Mar 20 15:21:07 localhost kernel: scsi 1:2:1:0: rejecting I/O to dead device
Mar 20 15:21:08 localhost last message repeated 5 times
Mar 20 15:21:08 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 
4096 167480688640, Input/output error 
Mar 20 15:21:08 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 
512 1151535746560, Input/output error

后面重启了tgtd的主机,发现机器找不到逻辑卷vg (sdc 实际上有17TB左右,是提供给虚拟化的存储使用) 奇怪的是,它为什么找不到虚拟磁盘组,vg1 

各位大神有什么办法 能恢复逻辑卷吗?  



VG   #PV #LV #SN Attr   VSize  VFree 
  vg 1  10   0 wz--n- 21.83T 14.70T
[root@localhost ~]# blkid
/dev/sda1: LABEL="/boot" UUID="600c84c5-cd60-4896-9a0f-56f70f585bec" 
TYPE="ext3" 
/dev/sda2: TYPE="swap" LABEL="SWAP-sda2" 
/dev/sda3: LABEL="/" UUID="51146b28-b3c5-44c4-94bc-6a216a35604d" TYPE="ext3" 
/dev/sdb1: UUID="pTXddZ-O0pw-weQr-MXqs-ExLo-sUAc-CsECL6" TYPE="lvm2pv" 
[root@localhost ~]# fdisk -l

Disk /dev/sda: 299.4 GB, 299439751168 bytes
255 heads, 63 sectors/track, 36404 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *   1  25  200781   83  Linux
/dev/sda2  26818465537167+  82  Linux swap / Solaris
/dev/sda38185   36404   226677150   83  Linux

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk 
doesn't support GPT. Use GNU Parted.


WARNING: The size of this disk is 24.0 TB (24000277250048 bytes).
DOS partition table format can not be used on drives for volumes
larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID 
partition table format (GPT).


Disk /dev/sdb: 24000.2 GB, 24000277250048 bytes
255 heads, 63 sectors/track, 2917867 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sdb1   1  267350  2147483647+  ee  EFI GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk 
doesn't support GPT. Use GNU Parted.


Disk /dev/sdc: 18000.2 GB, 18000207937536 bytes
255 heads, 63 sectors/track, 2188400 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdc doesn't contain a valid partition table



[root@localhost ~]# vgcfgrestore --file  /etc/lvm/backup/vg1 vg1
  Couldn't find device with uuid KyGefy-Vctk-GjiG-OTMr-jF8W-JQ2A-Qmcila.
  Cannot restore Volume Group vg1 with 1 PVs marked as missing. 
  Restore failed.


许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: users-cn-return-3276-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3276-xusz=chinanetcenter@cloudstack.apache.org] 代表 
網勁科技 黃奕璽 / Carl Huang
发送时间: 2014年3月21日星期五 10:56
收件人: users-cn@cloudstack.apache.org; xushy1
主题: Re: Re: 物理主机上能做NFS共享吗

可以


2014-03-19 18:28 GMT+08:00 徐诗云 :

>
> 我是没存储空间了,想拿主机上的空间做一级 二级存储
> 发件人: linux...@gmail.com
> 发送时间: 2014-03-19 17:36
> 收件人: users-cn; xushy1
> 主题: Re: 物理主机上能做NFS共享吗
> 请具体描述下你的问题
>
> 一般情况下物理主机是可以做NFS共享
>
> 2014-03-19 17:25 GMT+08:00 徐诗云 :
> >
> >
> >
> >
> >
> >
>
>
>
> --
> 白清杰 (Born Bai)
>
> 北京开源愿景信息技术有限公司
>
> Mail: linux...@gmail.com
>



-- 

eDynamics 網勁科技

總管理處
主任
黃奕璽   Carl Huang
電話:+886-2-8797-6373 分機:6302
傳真:+886-2-8797-6272
E-Mail:carl_hu...@edyna.com
台北總公司:台北市內湖區瑞光路 513 巷 28 號 7 樓

來寶島  www.laibaodao.com
oBuy全買網  www.obuy.tw
荷包網  www.joinbao.com
CityTalk城市通 www.citytalk.tw



答复: 取消维护ISCSI存储提示错误

2014-03-20 文章

部署了两个群集,单独的节点,单独的存储,




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 


-邮件原件-
发件人: users-cn-return-3265-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-3265-xusz=chinanetcenter@cloudstack.apache.org] 代表 
linux...@gmail.com
发送时间: 2014年3月20日星期四 17:36
收件人: users-cn@cloudstack.apache.org
主题: Re: 取消维护ISCSI存储提示错误

你们是部署了几个存储呢?如果是多个存储,并且主机设置了HA 是可以实现迁移的

在 2014年3月20日 下午4:55,hongwe...@gmail.com  写道:
>
>
>
>
>
>
> 我也遇见了同样的问题。XENSERVER+FC-SAN模拟FC宕机后怎么恢复。刚开始的时候系统VM启动不了,然后自动创建也失败,最后把FC删了重新添加了一遍。系统VM创建成功。然后两台XENserver中的一台无法创建虚拟机,准备把FC存储再次删除,但是设置成维护模式就变成两个按钮了。一个是启动维护,一个是取消维护。点取消维护就报同样的错误。
> 已经一下午了,仍然没搞定,如果有消息,互通解决方案
>
>
> hongwe...@gmail.com
> ?发件人:?许叁征发送时间:?2014-03-20?15:04收件人:?users-cn@cloudstack.apache.org主题:?取消维护ISCSI存储提示错误?
> HI ALL
>  今天发现ISCSI无法启动虚拟机,在平台上将ISCSI存储设置成维护 状态 ,然后再取
> 消维护,提示以下错误 ,看看这个是怎么问题?一直是这样的,先谢谢了。
> ?
> com.cloud.utils.exception.ExecutionException cannot be cast to
> com.cloud.exception.ResourceUnavailableException
>



-- 
白清杰 (Born Bai)

北京开源愿景信息技术有限公司

Mail: linux...@gmail.com


取消维护ISCSI存储提示错误

2014-03-20 文章

HI ALL
 今天发现ISCSI无法启动虚拟机,在平台上将ISCSI存储设置成维护 状态 ,然后再取
消维护,提示以下错误 ,看看这个是怎么问题?一直是这样的,先谢谢了。

com.cloud.utils.exception.ExecutionException cannot be cast to
com.cloud.exception.ResourceUnavailableException


cs 系统路由器无法启动问题,消失掉

2014-03-06 文章
HI ALL
  碰到一个难题,系统路由器消失不见了,重启网络 提示fail to restart network
,导致 创建的虚拟机一直不能自动分配IP,求如何处理方法。。先谢谢了。



root@manager ~]# tailf
/usr/share/cloud/management/logs/management-server.log |grep -v 192.168
|grep -v  Asking 
2014-03-06 18:25:32,872 WARN  [cloud.api.ApiDispatcher]
(Job-Executor-102:job-535) class com.cloud.api.ServerApiException : Failed
to restart network
2014-03-06 18:25:32,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-102:job-535) Complete async job-535, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: Failed to restart network
2014-03-06 18:25:33,006 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-102:job-535) Sync queue (1) is currently empty
2014-03-06 18:25:33,013 WARN  [cloud.async.AsyncJobManagerImpl]
(Job-Executor-102:job-535) Unable to unregister active job 535 from JMX
monitoring
2014-03-06 18:25:37,530 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) Async job-535 completed
2014-03-06 18:25:42,172 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1
is ready to launch secondary storage VM
2014-03-06 18:25:42,259 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2014-03-06 18:25:42,932 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers. 
2014-03-06 18:25:51,157 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-460:null) Ping from 56
2014-03-06 18:25:52,120 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-412:null) Seq 56-1534525442: Executing request
2014-03-06 18:25:52,602 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-412:null) Seq 56-1534525442: Response Received: 
2014-03-06 18:25:52,603 DEBUG [agent.transport.Request]
(DirectAgent-412:null) Seq 56-1534525442: Processing:  { Ans: , MgmtId:
690716573693, via: 56, Ver: v1, Flags: 10,
[{"ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"r
esult":true,"wait":0}}] }
2014-03-06 18:25:55,664 DEBUG [cloud.server.StatsCollector]
(StatsCollector-2:null) VmStatsCollector is running...
2014-03-06 18:25:55,703 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-406:null) Seq 56-1534532114: Executing request
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 4.42
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 3.32
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 86.854999
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 5.15
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 5.155
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 5.695
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 4.665
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 5.075
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 5.8505
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 4.825
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 4.62
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 86.804999
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 2.875
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 0.02
2014-03-06 18:25:56,136 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-406:null) Vm cpu utilization 4.39
2014-03-06 18:25:56,137 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-406:null) Seq 56-1534532114: Response Received: 
2014-03-06 18:25:56,137 DEBUG [agent.transport.Request]
(StatsCollector-2:null) Seq 56-1534532114: Received:  { Ans: , MgmtId:
690716573693, via: 56, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
2014-03-06 18:25:56,149 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-480:null) Seq 65-598478431: Executing request
2014-03-06 18:25:56,420 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-480:null) Vm cpu utilization 0.18997
2014-03-06 18:25:56,420 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-480:null) Vm cpu utilization 2.65
2014-03-06 18:25:56,420 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-480:null) Vm cpu utilization 3.575
2014-03-06 18:25:56,420 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-480:null) Vm cpu utilization 2.63
2014-03-06 18:25:56,420 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-480:null) Vm cpu utilization 2.63
2014-03-06 18:25:56,420 DEBUG [agent.manag

答复: Re: 在windows下编译cloudstack4.1.1

2014-03-04 文章
 HI ALL  

 碰到一个问题,SSVM和CVM不能启动, 以下是日志,请教 大家这是问题出在哪,应如何解决,谢谢了。




014-03-04 17:16:08,012 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-22:job-344) Cleaning up resources for the vm 
VM[ConsoleProxy|v-62160-VM] in Starting state
2014-03-04 17:16:08,014 DEBUG [agent.transport.Request] 
(Job-Executor-22:job-344) Seq 56-1158480075: Sending  { Cmd , MgmtId: 
690716573693, via: 56, Ver: v1, Flags: 100111, 
[{"StopCommand":{"isProxy":false,"vmName":"v-62160-VM","wait":0}}] }
2014-03-04 17:16:08,014 DEBUG [agent.transport.Request] 
(Job-Executor-22:job-344) Seq 56-1158480075: Executing:  { Cmd , MgmtId: 
690716573693, via: 56, Ver: v1, Flags: 100111, 
[{"StopCommand":{"isProxy":false,"vmName":"v-62160-VM","wait":0}}] }
2014-03-04 17:16:08,014 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-250:null) Seq 56-1158480075: Executing request
2014-03-04 17:16:08,174 INFO  [xen.resource.CitrixResourceBase] 
(DirectAgent-250:null) VM does not exist on 
XenServerf2f076b1-1405-451c-b37e-caf3605b6656
2014-03-04 17:16:08,174 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-250:null) Seq 56-1158480075: Response Received: 
2014-03-04 17:16:08,174 DEBUG [agent.transport.Request] (DirectAgent-250:null) 
Seq 56-1158480075: Processing:  { Ans: , MgmtId: 690716573693, via: 56, Ver: 
v1, Flags: 110, [{"StopAnswer":{"vncPort":0,"result":true,"details":"VM does 
not exist","wait":0}}] }
2014-03-04 17:16:08,174 DEBUG [agent.manager.AgentAttache] 
(DirectAgent-250:null) Seq 56-1158480075: No more commands found
2014-03-04 17:16:08,174 DEBUG [agent.transport.Request] 
(Job-Executor-22:job-344) Seq 56-1158480075: Received:  { Ans: , MgmtId: 
690716573693, via: 56, Ver: v1, Flags: 110, { StopAnswer } }
2014-03-04 17:16:08,243 DEBUG [cloud.network.NetworkManagerImpl] 
(Job-Executor-22:job-344) Provider SecurityGroupProvider is not enabled in 
physical network id=200
2014-03-04 17:16:08,447 DEBUG [network.guru.ControlNetworkGuru] 
(Job-Executor-22:job-344) Released nic: NicProfile[248067-62160-null-null-null
2014-03-04 17:16:08,583 DEBUG [dc.dao.DataCenterIpAddressDaoImpl] 
(Job-Executor-22:job-344) Releasing ip address for 
reservationId=3ebb6122-552e-49ef-aa7c-60e6db77163d, instance=248068
2014-03-04 17:16:08,647 DEBUG [network.guru.PodBasedNetworkGuru] 
(Job-Executor-22:job-344) Released nic: NicProfile[248068-62160-null-null-null
2014-03-04 17:16:08,714 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-22:job-344) Successfully released network resources for the vm 
VM[ConsoleProxy|v-62160-VM]
2014-03-04 17:16:08,714 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-22:job-344) Successfully cleanued up resources for the vm 
VM[ConsoleProxy|v-62160-VM] in Starting state
2014-03-04 17:16:08,716 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) DeploymentPlanner allocation algorithm: random
2014-03-04 17:16:08,716 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) Trying to allocate a host and storage pools from 
dc:1, pod:1,cluster:null, requested cpu: 500, requested ram: 1073741824
2014-03-04 17:16:08,716 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) Is ROOT volume READY (pool already allocated)?: No
2014-03-04 17:16:08,716 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) Searching resources only under specified Pod: 1
2014-03-04 17:16:08,716 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) Searching resources only under specified Pod: 1
2014-03-04 17:16:08,718 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) Listing clusters in order of aggregate capacity, that 
have (atleast one host with) enough CPU and RAM capacity under this Pod: 1
2014-03-04 17:16:08,719 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) CPUOverprovisioningFactor considered: 6.0
2014-03-04 17:16:08,726 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) Checking resources in Cluster: 1 under Pod: 1
2014-03-04 17:16:08,726 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-344) Calling HostAllocators to find suitable hosts
2014-03-04 17:16:08,726 DEBUG [allocator.impl.FirstFitAllocator] 
(Job-Executor-22:job-344 FirstFitRoutingAllocator) Looking for hosts in dc: 1  
pod:1  cluster:1
2014-03-04 17:16:08,728 DEBUG [allocator.impl.FirstFitAllocator] 
(Job-Executor-22:job-344 FirstFitRoutingAllocator) FirstFitAllocator has 2 
hosts to check for allocation: [Host[-55-Routing], Host[-56-Routing]]
2014-03-04 17:16:08,731 DEBUG [allocator.impl.FirstFitAllocator] 
(Job-Executor-22:job-344 FirstFitRoutingAllocator) Found 2 hosts for allocation 
after prioritization: [Host[-55-Routing], Host[-56-Routing]]
2014-03-04 17:16:08,731 DEBUG [allocator.impl.FirstFitAllocator] 
(Job-Executor-22:job-344 FirstFitRoutingAllocator) Looking for speed=500Mhz, 
Ram=1024
2014-03-04 17:16:08,732 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-22:job-344 FirstFitRoutingAllocator) Checking if host: 55 has 
enough capacity for re

SSVM无法启动

2014-02-27 文章
Hi ALL 
 CS出现故障,无法启动系统虚拟机,系统二级存储找不到,在面板上显示为0. 以下是
日志,请求大家分析是什么原因导致



om :Starting to Stopped with event: OperationFailedvm's original host id:
null new host id: null host id before state transition: 48
2014-02-27 22:11:08,418 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-8:job-119) Hosts's actual total CPU: 34128 and CPU after
applying overprovisioning: 34128
2014-02-27 22:11:08,418 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-8:job-119) release cpu from host: 48, old used:
13000,reserved: 0, actual total: 34128, total with overprovisioning: 34128;
new used: 12500,reserved:0; movedfromreserved: false,moveToReserveredfalse
2014-02-27 22:11:08,418 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-8:job-119) release mem from host: 48, old used:
6845104128,reserved: 0, total: 24472994112; new used: 6576668672,reserved:0;
movedfromreserved: false,moveToReserveredfalse
2014-02-27 22:11:08,464 WARN
[storage.secondary.SecondaryStorageManagerImpl] (Job-Executor-8:job-119)
Exception while trying to start secondary storage vm
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[SecondaryStorageVm|s-56979-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImp
l.java:734)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:
472)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:
465)
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(Se
condaryStorageManagerImpl.java:257)
at
com.cloud.server.ManagementServerImpl.startSecondaryStorageVm(ManagementServ
erImpl.java:2604)
at
com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.java:36)
at
com.cloud.server.ManagementServerImpl.startSystemVM(ManagementServerImpl.jav
a:2730)
at com.cloud.api.commands.StartSystemVMCmd.execute(StartSystemVMCmd.
java:107)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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)
2014-02-27 22:11:08,532 WARN  [cloud.api.ApiDispatcher]
(Job-Executor-8:job-119) class com.cloud.api.ServerApiException : Fail to
start system vm
2014-02-27 22:11:08,532 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-119) Com




答复: 删除iscsi存储出错

2014-02-25 文章
要不我加下你QQ好吧,这样不太好说哦





许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 


-邮件原件-
发件人: users-cn-return-2966-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-2966-xusz=chinanetcenter@cloudstack.apache.org] 代表 
leo
发送时间: 2014年2月26日星期三 8:44
收件人: users-cn
主题: Re: 删除iscsi存储出错

不能在线迁移有什么log? 迁移失败还是pending? 
你现在是原有存储继续加?删除之后需要查一下还有什么相关引用吧?
在 2014年2月25日,上午9:22,许叁征  写道:

> 
> 原来是可以的,原来都可以正常启动的,现在感觉一台XENserver节点开了很多的虚拟机,一节只启动了四台虚拟机,它不能在线迁移了现在
> 
> 
> 
> 许叁征
> 网宿科技股份有限公司  厦门分公司 运营技术支持部
> 
> Tel:13860125907  
> E-mail:x...@chinanetcenter.com
> http://www.chinanetcenter.com
> 
> 分公司:北京-上海-广州-深圳   
> 免费咨询热线:800-820-0001
> 网宿科技 --卓越的互联网业务平台提供商
> 
> 
> 
> -邮件原件-
> 发件人: users-cn-return-2964-xusz=chinanetcenter@cloudstack.apache.org 
> [mailto:users-cn-return-2964-xusz=chinanetcenter@cloudstack.apache.org] 
> 代表 leo
> 发送时间: 2014年2月24日星期一 20:29
> 收件人: users-cn
> 主题: Re: 删除iscsi存储出错
> 
> pool的错误? 你用的是xen ?还是~ 没遇到过这个错误。
> 
> 用模版在原有存储创建vm可以么?
> 
> 在 2014年2月24日,下午5:04,许叁征  写道:
> 
>> 
>> 改好了,现在创建虚拟机出现以下错误,模板是以前使用NFS建立的,现在新添加了ISCSI存储,就出现以下错误 ,这是什么问题,要怎么处理
>> a44-bc97-47452038ce23.vhd due to 
>> com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
>> 5cd20626-1d26-fe5e-bdfa-c5b72c9baa49
>> 2014-02-24 16:32:51,824 DEBUG [cloud.template.TemplateManagerImpl] 
>> (Job-Executor-1:job-167) Template 235 download to pool 219 failed due to 
>> Catch Exception com.cloud.utils.exception.CloudRuntimeException on 
>> host:ea339c35-2574-4813-b873-35c24f47e5e1 for template: 
>> nfs://172.16.0.130/home/share/secondary/template/tmpl/4/235//1cf2a012-4e65-3a44-bc97-47452038ce23.vhd
>>  due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi 
>> in sr 5cd20626-1d26-fe5e-bdfa-c5b72c9baa49
>> 2014-02-24 16:32:51,825 DEBUG [cloud.template.TemplateManagerImpl] 
>> (Job-Executor-1:job-167) Template 235 is not found on and can not be 
>> downloaded to pool 219
>> 2014-02-24 16:32:51,825 DEBUG [cloud.storage.StorageManagerImpl] 
>> (Job-Executor-1:job-167) Cannot use this pool Pool[219|IscsiLUN] because we 
>> can't propagate template 
>> Tmpl[235-VHD-235-4-65d92273-e12a-3aa5-a41b-724b476338ca
>> 2014-02-24 16:32:51,883 INFO  [cloud.vm.VirtualMachineManagerImpl] 
>> (Job-Executor-1:job-167) Unable to contact resource.
>> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:219] 
>> is unreachable: Unable to create Vol[56940|vm=56890|ROOT] 
>> 
>> 
>> 
>> 
>> 
>> 许叁征
>> 网宿科技股份有限公司  厦门分公司 运营技术支持部
>> 
>> Tel:13860125907  
>> E-mail:x...@chinanetcenter.com
>> http://www.chinanetcenter.com
>> 
>> 分公司:北京-上海-广州-深圳   
>> 免费咨询热线:800-820-0001
>> 网宿科技 --卓越的互联网业务平台提供商
>> 
>> 
>> 
>> -邮件原件-
>> 发件人: users-cn-return-2962-xusz=chinanetcenter@cloudstack.apache.org 
>> [mailto:users-cn-return-2962-xusz=chinanetcenter@cloudstack.apache.org] 
>> 代表 leo
>> 发送时间: 2014年2月24日星期一 16:28
>> 收件人: users-cn
>> 主题: Re: 删除iscsi存储出错
>> 
>> 改数据库吧? 不是正常删除。
>> 在 2014年2月24日,下午3:59,许叁征  写道:
>> 
>>> HI ALL
>>> 平台删除ISCSI存储,提示fail to delete storage存储, 
>>> 求教各位这个要怎么处理解决,(iqn.2014-01.net.xsz:iscsi.disk0/5实际已不存在了)
>>> 
>>> 
>>> 
>>> 2014-02-24 15:02:03,197 DEBUG [agent.transport.Request] 
>>> (DirectAgent-137:null) Seq 48-1831426618: Processing:  { Ans: , MgmtId: 
>>> 690716573693, via: 48, Ver: v1, Flags: 10, 
>>> [{"Answer":{"result":false,"details":"DeleteStoragePoolCommand 
>>> XenAPIException:Can not see storage pool: 
>>> c5b6f16e-acee-3a60-8764-5adcad839fba from on 
>>> host:b26cd46a-3dad-466c-a010-cd4aacf4670f 
>>> host:b26cd46a-3dad-466c-a010-cd4aacf4670f pool: 
>>> 192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5","wait":0}}] }
>>> 2014-02-24 15:02:03,197 DEBUG [agent.transport.Request] 
>>> (catalina-exec-21:null) Seq 48-1831426618: Received:  { Ans: , MgmtId: 
>>> 690716573693, via: 48, Ver: v1, Flags: 10, { Answer } }
>>> 2014-02-24 15:02:03,197 DEBUG [agent.manager.AgentManagerImpl] 
>>> (catalina-exec-21:null) Details from executing class 
>>> com.cloud.agent.api.DeleteStoragePoolCommand: DeleteStoragePoolCommand 
>>> XenAPIException:Can not see storage pool: 
>>> c5b6f16e-acee-3a60-8764-5adcad839fba from on 
>>> host:b26cd46a-3dad-466c-

答复: 删除iscsi存储出错

2014-02-24 文章

原来是可以的,原来都可以正常启动的,现在感觉一台XENserver节点开了很多的虚拟机,一节只启动了四台虚拟机,它不能在线迁移了现在




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: users-cn-return-2964-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-2964-xusz=chinanetcenter@cloudstack.apache.org] 代表 
leo
发送时间: 2014年2月24日星期一 20:29
收件人: users-cn
主题: Re: 删除iscsi存储出错

pool的错误? 你用的是xen ?还是~ 没遇到过这个错误。

用模版在原有存储创建vm可以么?

在 2014年2月24日,下午5:04,许叁征  写道:

> 
> 改好了,现在创建虚拟机出现以下错误,模板是以前使用NFS建立的,现在新添加了ISCSI存储,就出现以下错误 ,这是什么问题,要怎么处理
> a44-bc97-47452038ce23.vhd due to 
> com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
> 5cd20626-1d26-fe5e-bdfa-c5b72c9baa49
> 2014-02-24 16:32:51,824 DEBUG [cloud.template.TemplateManagerImpl] 
> (Job-Executor-1:job-167) Template 235 download to pool 219 failed due to 
> Catch Exception com.cloud.utils.exception.CloudRuntimeException on 
> host:ea339c35-2574-4813-b873-35c24f47e5e1 for template: 
> nfs://172.16.0.130/home/share/secondary/template/tmpl/4/235//1cf2a012-4e65-3a44-bc97-47452038ce23.vhd
>  due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi 
> in sr 5cd20626-1d26-fe5e-bdfa-c5b72c9baa49
> 2014-02-24 16:32:51,825 DEBUG [cloud.template.TemplateManagerImpl] 
> (Job-Executor-1:job-167) Template 235 is not found on and can not be 
> downloaded to pool 219
> 2014-02-24 16:32:51,825 DEBUG [cloud.storage.StorageManagerImpl] 
> (Job-Executor-1:job-167) Cannot use this pool Pool[219|IscsiLUN] because we 
> can't propagate template 
> Tmpl[235-VHD-235-4-65d92273-e12a-3aa5-a41b-724b476338ca
> 2014-02-24 16:32:51,883 INFO  [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-1:job-167) Unable to contact resource.
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:219] 
> is unreachable: Unable to create Vol[56940|vm=56890|ROOT] 
> 
> 
> 
> 
> 
> 许叁征
> 网宿科技股份有限公司  厦门分公司 运营技术支持部
> 
> Tel:13860125907  
> E-mail:x...@chinanetcenter.com
> http://www.chinanetcenter.com
> 
> 分公司:北京-上海-广州-深圳   
> 免费咨询热线:800-820-0001
> 网宿科技 --卓越的互联网业务平台提供商
> 
> 
> 
> -邮件原件-
> 发件人: users-cn-return-2962-xusz=chinanetcenter@cloudstack.apache.org 
> [mailto:users-cn-return-2962-xusz=chinanetcenter@cloudstack.apache.org] 
> 代表 leo
> 发送时间: 2014年2月24日星期一 16:28
> 收件人: users-cn
> 主题: Re: 删除iscsi存储出错
> 
> 改数据库吧? 不是正常删除。
> 在 2014年2月24日,下午3:59,许叁征  写道:
> 
>> HI ALL
>> 平台删除ISCSI存储,提示fail to delete storage存储, 
>> 求教各位这个要怎么处理解决,(iqn.2014-01.net.xsz:iscsi.disk0/5实际已不存在了)
>> 
>> 
>> 
>> 2014-02-24 15:02:03,197 DEBUG [agent.transport.Request] 
>> (DirectAgent-137:null) Seq 48-1831426618: Processing:  { Ans: , MgmtId: 
>> 690716573693, via: 48, Ver: v1, Flags: 10, 
>> [{"Answer":{"result":false,"details":"DeleteStoragePoolCommand 
>> XenAPIException:Can not see storage pool: 
>> c5b6f16e-acee-3a60-8764-5adcad839fba from on 
>> host:b26cd46a-3dad-466c-a010-cd4aacf4670f 
>> host:b26cd46a-3dad-466c-a010-cd4aacf4670f pool: 
>> 192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5","wait":0}}] }
>> 2014-02-24 15:02:03,197 DEBUG [agent.transport.Request] 
>> (catalina-exec-21:null) Seq 48-1831426618: Received:  { Ans: , MgmtId: 
>> 690716573693, via: 48, Ver: v1, Flags: 10, { Answer } }
>> 2014-02-24 15:02:03,197 DEBUG [agent.manager.AgentManagerImpl] 
>> (catalina-exec-21:null) Details from executing class 
>> com.cloud.agent.api.DeleteStoragePoolCommand: DeleteStoragePoolCommand 
>> XenAPIException:Can not see storage pool: 
>> c5b6f16e-acee-3a60-8764-5adcad839fba from on 
>> host:b26cd46a-3dad-466c-a010-cd4aacf4670f 
>> host:b26cd46a-3dad-466c-a010-cd4aacf4670f pool: 
>> 192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5
>> 2014-02-24 15:02:03,197 WARN  [cloud.storage.StorageManagerImpl] 
>> (catalina-exec-21:null) Failed to Delete storage pool id: 214
>> 2014-02-24 15:02:03,202 DEBUG [cloud.alert.AlertManagerImpl] 
>> (catalina-exec-21:null) Have already sent: 1 emails for alert type '20' -- 
>> skipping send email
>> 2014-02-24 15:02:03,204 WARN  [cloud.api.ApiDispatcher] 
>> (catalina-exec-21:null) class com.cloud.api.ServerApiException : Failed to 
>> delete storage pool
>> 2014-02-24 15:02:03,204 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null) 
>> ===END===  192.168.1.232 -- GET  
>> command=deleteStoragePool&id=c5b6f16e-acee-3a60-8764-5adcad839fba&forced=true&response=json&sessionkey=ApA%2F0TJnBexiE5xYrvLm6MUAdLY%3D&_=1393225318515
>> 
>> 2014-02-24 15

答复: 删除iscsi存储出错

2014-02-24 文章

改好了,现在创建虚拟机出现以下错误,模板是以前使用NFS建立的,现在新添加了ISCSI存储,就出现以下错误 ,这是什么问题,要怎么处理
a44-bc97-47452038ce23.vhd due to 
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
5cd20626-1d26-fe5e-bdfa-c5b72c9baa49
2014-02-24 16:32:51,824 DEBUG [cloud.template.TemplateManagerImpl] 
(Job-Executor-1:job-167) Template 235 download to pool 219 failed due to Catch 
Exception com.cloud.utils.exception.CloudRuntimeException on 
host:ea339c35-2574-4813-b873-35c24f47e5e1 for template: 
nfs://172.16.0.130/home/share/secondary/template/tmpl/4/235//1cf2a012-4e65-3a44-bc97-47452038ce23.vhd
 due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi in 
sr 5cd20626-1d26-fe5e-bdfa-c5b72c9baa49
2014-02-24 16:32:51,825 DEBUG [cloud.template.TemplateManagerImpl] 
(Job-Executor-1:job-167) Template 235 is not found on and can not be downloaded 
to pool 219
2014-02-24 16:32:51,825 DEBUG [cloud.storage.StorageManagerImpl] 
(Job-Executor-1:job-167) Cannot use this pool Pool[219|IscsiLUN] because we 
can't propagate template Tmpl[235-VHD-235-4-65d92273-e12a-3aa5-a41b-724b476338ca
2014-02-24 16:32:51,883 INFO  [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-1:job-167) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:219] is 
unreachable: Unable to create Vol[56940|vm=56890|ROOT] 
 





许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 


-邮件原件-
发件人: users-cn-return-2962-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-2962-xusz=chinanetcenter@cloudstack.apache.org] 代表 
leo
发送时间: 2014年2月24日星期一 16:28
收件人: users-cn
主题: Re: 删除iscsi存储出错

改数据库吧? 不是正常删除。
在 2014年2月24日,下午3:59,许叁征  写道:

> HI ALL
>  平台删除ISCSI存储,提示fail to delete storage存储, 
> 求教各位这个要怎么处理解决,(iqn.2014-01.net.xsz:iscsi.disk0/5实际已不存在了)
>  
>  
>  
> 2014-02-24 15:02:03,197 DEBUG [agent.transport.Request] 
> (DirectAgent-137:null) Seq 48-1831426618: Processing:  { Ans: , MgmtId: 
> 690716573693, via: 48, Ver: v1, Flags: 10, 
> [{"Answer":{"result":false,"details":"DeleteStoragePoolCommand 
> XenAPIException:Can not see storage pool: 
> c5b6f16e-acee-3a60-8764-5adcad839fba from on 
> host:b26cd46a-3dad-466c-a010-cd4aacf4670f 
> host:b26cd46a-3dad-466c-a010-cd4aacf4670f pool: 
> 192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5","wait":0}}] }
> 2014-02-24 15:02:03,197 DEBUG [agent.transport.Request] 
> (catalina-exec-21:null) Seq 48-1831426618: Received:  { Ans: , MgmtId: 
> 690716573693, via: 48, Ver: v1, Flags: 10, { Answer } }
> 2014-02-24 15:02:03,197 DEBUG [agent.manager.AgentManagerImpl] 
> (catalina-exec-21:null) Details from executing class 
> com.cloud.agent.api.DeleteStoragePoolCommand: DeleteStoragePoolCommand 
> XenAPIException:Can not see storage pool: 
> c5b6f16e-acee-3a60-8764-5adcad839fba from on 
> host:b26cd46a-3dad-466c-a010-cd4aacf4670f 
> host:b26cd46a-3dad-466c-a010-cd4aacf4670f pool: 
> 192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5
> 2014-02-24 15:02:03,197 WARN  [cloud.storage.StorageManagerImpl] 
> (catalina-exec-21:null) Failed to Delete storage pool id: 214
> 2014-02-24 15:02:03,202 DEBUG [cloud.alert.AlertManagerImpl] 
> (catalina-exec-21:null) Have already sent: 1 emails for alert type '20' -- 
> skipping send email
> 2014-02-24 15:02:03,204 WARN  [cloud.api.ApiDispatcher] 
> (catalina-exec-21:null) class com.cloud.api.ServerApiException : Failed to 
> delete storage pool
> 2014-02-24 15:02:03,204 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null) 
> ===END===  192.168.1.232 -- GET  
> command=deleteStoragePool&id=c5b6f16e-acee-3a60-8764-5adcad839fba&forced=true&response=json&sessionkey=ApA%2F0TJnBexiE5xYrvLm6MUAdLY%3D&_=1393225318515
>  
> 2014-02-24 15:02:03,039 DEBUG [agent.transport.Request] 
> (DirectAgent-269:null) Seq 45-1845385316: Processing:  { Ans: , MgmtId: 
> 690716573693, via: 45, Ver: v1, Flags: 10, 
> [{"Answer":{"result":false,"details":"DeleteStoragePoolCommand 
> XenAPIException:Can not see storage pool: 
> c5b6f16e-acee-3a60-8764-5adcad839fba from on 
> host:ea339c35-2574-4813-b873-35c24f47e5e1 
> host:ea339c35-2574-4813-b873-35c24f47e5e1 pool: 
> 192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5","wait":0}}] }
> 2014-02-24 15:02:03,039 DEBUG [agent.transport.Request] 
> (catalina-exec-21:null) Seq 45-1845385316: Received:  { Ans: , MgmtId: 
> 690716573693, via: 45, Ver: v1, Flags: 10, { Answer } }
> 2014-02-24 15:02:03,040 DEBUG [agent.manager.AgentManagerImpl] 
> (catalina-exec-21:null) Details from executing class 
> com.cloud.agent.api.DeleteStoragePoolCommand: DeleteStoragePoolCommand 
> XenAPIException

删除iscsi存储出错

2014-02-24 文章
HI ALL 

 平台删除ISCSI存储,提示fail to delete storage存储, 求教各位这个要怎么处理
解决,(iqn.2014-01.net.xsz:iscsi.disk0/5实际已不存在了)

 

 

 

2014-02-24 15:02:03,197 DEBUG [agent.transport.Request]
(DirectAgent-137:null) Seq 48-1831426618: Processing:  { Ans: , MgmtId:
690716573693, via: 48, Ver: v1, Flags: 10,
[{"Answer":{"result":false,"details":"DeleteStoragePoolCommand
XenAPIException:Can not see storage pool:
c5b6f16e-acee-3a60-8764-5adcad839fba from on
host:b26cd46a-3dad-466c-a010-cd4aacf4670f
host:b26cd46a-3dad-466c-a010-cd4aacf4670f pool:
192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5","wait":0}}] }
2014-02-24 15:02:03,197 DEBUG [agent.transport.Request]
(catalina-exec-21:null) Seq 48-1831426618: Received:  { Ans: , MgmtId:
690716573693, via: 48, Ver: v1, Flags: 10, { Answer } }
2014-02-24 15:02:03,197 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-21:null) Details from executing class
com.cloud.agent.api.DeleteStoragePoolCommand: DeleteStoragePoolCommand
XenAPIException:Can not see storage pool:
c5b6f16e-acee-3a60-8764-5adcad839fba from on
host:b26cd46a-3dad-466c-a010-cd4aacf4670f
host:b26cd46a-3dad-466c-a010-cd4aacf4670f pool:
192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5
2014-02-24 15:02:03,197 WARN  [cloud.storage.StorageManagerImpl]
(catalina-exec-21:null) Failed to Delete storage pool id: 214
2014-02-24 15:02:03,202 DEBUG [cloud.alert.AlertManagerImpl]
(catalina-exec-21:null) Have already sent: 1 emails for alert type '20' --
skipping send email
2014-02-24 15:02:03,204 WARN  [cloud.api.ApiDispatcher]
(catalina-exec-21:null) class com.cloud.api.ServerApiException : Failed to
delete storage pool
2014-02-24 15:02:03,204 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===END===  192.168.1.232 -- GET
command=deleteStoragePool&id=c5b6f16e-acee-3a60-8764-5adcad839fba&forced=tru
e&response=json&sessionkey=ApA%2F0TJnBexiE5xYrvLm6MUAdLY%3D&_=1393225318515
 
2014-02-24 15:02:03,039 DEBUG [agent.transport.Request]
(DirectAgent-269:null) Seq 45-1845385316: Processing:  { Ans: , MgmtId:
690716573693, via: 45, Ver: v1, Flags: 10,
[{"Answer":{"result":false,"details":"DeleteStoragePoolCommand
XenAPIException:Can not see storage pool:
c5b6f16e-acee-3a60-8764-5adcad839fba from on
host:ea339c35-2574-4813-b873-35c24f47e5e1
host:ea339c35-2574-4813-b873-35c24f47e5e1 pool:
192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5","wait":0}}] }
2014-02-24 15:02:03,039 DEBUG [agent.transport.Request]
(catalina-exec-21:null) Seq 45-1845385316: Received:  { Ans: , MgmtId:
690716573693, via: 45, Ver: v1, Flags: 10, { Answer } }
2014-02-24 15:02:03,040 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-21:null) Details from executing class
com.cloud.agent.api.DeleteStoragePoolCommand: DeleteStoragePoolCommand
XenAPIException:Can not see storage pool:
c5b6f16e-acee-3a60-8764-5adcad839fba from on
host:ea339c35-2574-4813-b873-35c24f47e5e1
host:ea339c35-2574-4813-b873-35c24f47e5e1 pool:
192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5
2014-02-24 15:02:03,043 DEBUG [agent.transport.Request]
(catalina-exec-21:null) Seq 48-1831426618: Sending  { Cmd , MgmtId:
690716573693, via: 48, Ver: v1, Flags: 100011,
[{"DeleteStoragePoolCommand":{"pool":{"id":214,"uuid":"c5b6f16e-acee-3a60-87
64-5adcad839fba","host":"192.168.18.13","path":"/iqn.2014-01.net.xsz:iscsi.d
isk0/5","port":3260,"type":"IscsiLUN"},"localPath":"/mnt//c5b6f16e-acee-3a60
-8764-5adcad839fba","wait":0}}] }
2014-02-24 15:02:03,043 DEBUG [agent.transport.Request]
(catalina-exec-21:null) Seq 48-1831426618: Executing:  { Cmd , MgmtId:
690716573693, via: 48, Ver: v1, Flags: 100011,
[{"DeleteStoragePoolCommand":{"pool":{"id":214,"uuid":"c5b6f16e-acee-3a60-87
64-5adcad839fba","host":"192.168.18.13","path":"/iqn.2014-01.net.xsz:iscsi.d
isk0/5","port":3260,"type":"IscsiLUN"},"localPath":"/mnt//c5b6f16e-acee-3a60
-8764-5adcad839fba","wait":0}}] }
2014-02-24 15:02:03,044 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-137:null) Seq 48-1831426618: Executing request
2014-02-24 15:02:03,196 WARN  [xen.resource.CitrixResourceBase]
(DirectAgent-137:null) DeleteStoragePoolCommand XenAPIException:Can not see
storage pool: c5b6f16e-acee-3a60-8764-5adcad839fba from on
host:b26cd46a-3dad-466c-a010-cd4aacf4670f
host:b26cd46a-3dad-466c-a010-cd4aacf4670f pool:
192.168.18.13/iqn.2014-01.net.xsz:iscsi.disk0/5
com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool:
c5b6f16e-acee-3a60-8764-5adcad839fba from on
host:b26cd46a-3dad-466c-a010-cd4aacf4670f 

 

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



改了linux CS主机ROOT密码后,平台登陆不了问题

2014-01-13 文章
 

HI ALL,碰到一个问题,

改了linux CS主机ROOT密码后,平台登陆不了,日志显示以下,改ROOT密码 ,依然登
陆不了。应如何解决。

 

2014-01-14 12:53:29,114 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-20:null) Attempting to log in user: admin in domain 1

2014-01-14 12:53:29,114 DEBUG [server.auth.MD5UserAuthenticator]
(catalina-exec-20:null) Retrieving user: admin

2014-01-14 12:53:29,115 DEBUG [server.auth.MD5UserAuthenticator]
(catalina-exec-20:null) Password does not match

2014-01-14 12:53:29,116 DEBUG [server.auth.LDAPUserAuthenticator]
(catalina-exec-20:null) Retrieving user: admin

2014-01-14 12:53:29,117 DEBUG [server.auth.LDAPUserAuthenticator]
(catalina-exec-20:null) LDAP authenticator is not configured.

2014-01-14 12:53:29,117 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-20:null) Unable to authenticate user with username admin in
domain 1

2014-01-14 12:53:29,118 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-20:null) User: admin in domain 1 has failed to log in

2014-01-14 12:53:35,510 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-5:null) Attempting to log in user: admin in domain 1

2014-01-14 12:53:35,510 DEBUG [server.auth.MD5UserAuthenticator]
(catalina-exec-5:null) Retrieving user: admin

2014-01-14 12:53:35,511 DEBUG [server.auth.MD5UserAuthenticator]
(catalina-exec-5:null) Password does not match

2014-01-14 12:53:35,511 DEBUG [server.auth.LDAPUserAuthenticator]
(catalina-exec-5:null) Retrieving user: admin

2014-01-14 12:53:35,512 DEBUG [server.auth.LDAPUserAuthenticator]
(catalina-exec-5:null) LDAP authenticator is not configured.

2014-01-14 12:53:35,512 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-5:null) Unable to authenticate user with username admin in
domain 1

2014-01-14 12:53:35,513 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-5:null) User: admin in domain 1 has failed to log in

2014-01-14 12:53:40,660 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-438:null) Ping from 48

 

 

 

 



NFS挂死,平台虚拟机无法通信

2014-01-06 文章
HI ALL 

 最近 发现平台虚拟机很容易出现异常,查看日志,出现NFS nfs会挂死 ,然后节点
XEN全部断开掉,这种情况最近碰到好多次,

 要如何修复这种问题。。谢谢了。

 

Jan  6 16:56:43 manager kernel: rpc-srv/tcp: nfsd: got error -32 when
sending 140 bytes - shutting down socket
Jan  6 16:56:43 manager kernel: rpc-srv/tcp: nfsd: got error -32 when
sending 140 bytes - shutting down socket



 

 

 

 

 



系统一直重复下载模板问题

2014-01-03 文章
HI ALL

 

 下载模板后,发现系统一直是重复这几行,这是什么原因造成的,分析 看看。

 

 

2014-01-03 21:55:46,938 DEBUG [agent.transport.Request] (Timer-5:null) Seq
64-1673662578: Sending  { Cmd , MgmtId: 690716576832, via: 64, Ver: v1,
Flags: 100011,
[{"storage.DownloadProgressCommand":{"jobId":"9e6fbd08-34f0-4d18-bafb-511ed4
e1d9ab","request":"GET_STATUS","hvm":false,"description":"CentOS 5.6(64-bit)
no GUI
(XenServer)","checksum":"905cec879afd9c9d22ecc8036131a180","maxDownloadSizeI
nBytes":53687091200,"id":5,"resourceType":"TEMPLATE","url":"http://download.
cloud.com/templates/builtin/centos56-x86_64.vhd.bz2","format":"VHD","account
Id":1,"name":"centos56-x86_64-xen","secUrl":"nfs://172.16.0.130/home/share/s
econdary","wait":0}}] }

2014-01-03 21:55:46,979 DEBUG [agent.transport.Request]
(AgentManager-Handler-14:null) Seq 64-1673662578: Processing:  { Ans: ,
MgmtId: 690716576832, via: 64, Ver: v1, Flags: 10,
[{"storage.DownloadAnswer":{"jobId":"9e6fbd08-34f0-4d18-bafb-511ed4e1d9ab","
downloadPct":0,"errorString":"
","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/80
fdf34c-905c-309e-90b2-10cdd56ec0bf/template/tmpl/1/5/dnld7615886404746095909
tmp_","templateSize":0,"templatePhySicalSize":0,"checkSum":"905cec879afd9c9d
22ecc8036131a180","result":false,"details":" ","wait":0}}] }

2014-01-03 21:55:47,048 DEBUG [agent.transport.Request] (Timer-8:null) Seq
64-1673662579: Sending  { Cmd , MgmtId: 690716576832, via: 64, Ver: v1,
Flags: 100011,
[{"storage.DownloadProgressCommand":{"jobId":"9d4e73f1-98b3-425f-8ae7-0b16f9
f23435","request":"GET_STATUS","hvm":true,"description":"?..
瀹..","maxDownloadSizeInBytes":53687091200,"id":225,"resourceType":"TEMPLATE
","url":"http://192.168.0.194/distro/CentOS-5.8-20131023.iso","format":"ISO";
,"accountId":2,"name":"225-2-8de5a02f-cb91-3a37-9798-b7079551f9f1","secUrl":
"nfs://172.16.0.130/home/secondary","wait":0}}] }

2014-01-03 21:55:47,048 DEBUG [agent.transport.Request] (Timer-9:null) Seq
64-1673662580: Sending  { Cmd , MgmtId: 690716576832, via: 64, Ver: v1,
Flags: 100011,
[{"storage.DownloadProgressCommand":{"jobId":"a5430757-772c-45dd-bcba-feaa0a
d6243d","request":"GET_STATUS","hvm":false,"description":"CentOS 5.6(64-bit)
no GUI
(XenServer)","checksum":"905cec879afd9c9d22ecc8036131a180","maxDownloadSizeI
nBytes":53687091200,"id":5,"resourceType":"TEMPLATE","url":"http://download.
cloud.com/templates/builtin/centos56-x86_64.vhd.bz2","format":"VHD","account
Id":1,"name":"centos56-x86_64-xen","secUrl":"nfs://172.16.0.130/home/seconda
ry","wait":0}}] }

2014-01-03 21:55:47,090 DEBUG [agent.transport.Request]
(AgentManager-Handler-2:null) Seq 64-1673662579: Processing:  { Ans: ,
MgmtId: 690716576832, via: 64, Ver: v1, Flags: 10,
[{"storage.DownloadAnswer":{"jobId":"9d4e73f1-98b3-425f-8ae7-0b16f9f23435","
downloadPct":2,"errorString":"
","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/0e
8b35d0-5e11-3c1b-87d1-47e6bdac64a8/template/tmpl/2/225/dnld42243161601838522
91tmp_","templateSize":0,"templatePhySicalSize":0,"result":false,"details":"
","wait":0}}] }

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



答复: 二级存储删除不掉

2014-01-02 文章
/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt-m 
/home/user/ -f /root/acton-systemvm-02062012.vhd.bz2 -h xenserver -F

用这个命令下载二级存储


许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: users-cn-return-2885-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-2885-xusz=chinanetcenter@cloudstack.apache.org] 代表 
evanitsharp
发送时间: 2014年1月3日星期五 14:40
收件人: CloudStack社区
主题: Re: 二级存储删除不掉

二级存储下载?什么意思?






evanitsharp

发件人: 许叁征
发送时间: 2014-01-03 14:24
收件人: users-cn@cloudstack.apache.org
主题: 二级存储删除不掉
HI ALL 

 通过恢复之前的数据库,发现二级存储无法删除,下载了模板,也不能创建,帮忙看看是什么原因,




014-01-03 14:20:16,955 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-5:job-412) Executing com.cloud.api.commands.RebootSystemVmCmd for 
job-412
2014-01-03 14:20:17,108 DEBUG [agent.manager.AgentManagerImpl] 
(Job-Executor-5:job-412) Host with id 20 doesn't exist
2014-01-03 14:20:17,108 DEBUG [storage.secondary.SecondaryStorageManagerImpl] 
(Job-Executor-5:job-412) Rebooting Secondary Storage VM failed - s-56797-VM
2014-01-03 14:20:17,252 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-5:job-412) Complete async job-412, jobStatus: 1, resultCode: 0, 
result: com.cloud.api.response.SystemVmResponse@12cf66f
2014-01-03 14:20:17,386 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-5:job-412) Done executing 
com.cloud.api.commands.RebootSystemVmCmd for job-412
2014-01-03 14:20:18,328 DEBUG [storage.secondary.SecondaryStorageManagerImpl] 
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2014-01-03 14:20:18,434 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] 
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2014-01-03 14:20:19,551 DEBUG 
[network.router.VirtualNetworkApplianceManagerImpl] 
(RouterStatusMonitor-1:null) Found 0 routers. 
2014-01-03 14:20:21,987 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-18:null) Async job-412 completed
2014-01-03 14:20:22,544 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) HostStatsCollector is running...
2014-01-03 14:20:22,554 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-79:null) Seq 8-1694367831: Executing request
2014-01-03 14:20:22,803 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-79:null) Seq 8-1694367831: Response Received: 
2014-01-03 14:20:22,803 DEBUG [agent.transport.Request] (StatsCollector-1:null) 
Seq 8-1694367831: Received:  { Ans: , MgmtId: 690716576832, via: 8, Ver: v1, 
Flags: 10, { GetHostStatsAnswer } }
2014-01-03 14:20:22,808 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-148:null) Seq 25-1091043355: Executing request
2014-01-03 14:20:23,187 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-148:null) Seq 25-1091043355: Response Received: 
2014-01-03 14:20:23,187 DEBUG [agent.transport.Request] (StatsCollector-1:null) 
Seq 25-1091043355: Received:  { Ans: , MgmtId: 690716576832, via: 25, Ver: v1, 
Flags: 10, { GetHostStatsAnswer } }
2014-01-03 14:20:23,193 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-239:null) Seq 26-1719468059: Executing request
2014-01-03 14:20:23,550 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-239:null) Seq 26-1719468059: Response Received: 
2014-01-03 14:20:23,550 DEBUG [agent.transport.Request] (StatsCollector-1:null) 
Seq 26-1719468059: Received:  { Ans: , MgmtId: 690716576832, via: 26, Ver: v1, 
Flags: 10, { GetHostStatsAnswer } }
2014-01-03 14:20:41,423 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-11:null) submit async job-413, details: AsyncJobVO {id:413, 
userId: 2, accountId: 2, sessionKey: null, instanceType: SystemVm, instanceId: 
56797, cmd: com.cloud.api.commands.DestroySystemVmCmd, cmdOriginator: null, 
cmdInfo: 
{"id":"efcfa696-25dc-40b2-b42b-37d943e27576","response":"json","sessionkey":"Mbs1v/60bg2RYcevxiHDfXTt8r8\u003d","ctxUserId":"2","_":"1388730057187","ctxAccountId":"2","ctxStartEventId":"3043"},
 cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
processStatus: 0, resultCode: 0, result: null, initMsid: 690716576832, 
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-01-03 14:20:41,424 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-6:job-413) Executing com.cloud.api.commands.DestroySystemVmCmd 
for job-413
2014-01-03 14:20:41,731 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-6:job-413) VM state transitted from :Running to Stopping with 
event: StopRequestedvm's original host id: 20 new host id: 20 host id before 
state transition: 20
2014-01-03 14:20:41,733 WARN  [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-6:job-413) Unable to stop vm VM[SecondaryStorageVm|s-56797-VM]
2014-01-03 14:20:41,856 DEBUG [cloud.capac

二级存储删除不掉

2014-01-02 文章
econdaryStorageVm|s-56797-VM]
2014-01-03 14:20:41,856 INFO  [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-6:job-413) Did not expunge VM[SecondaryStorageVm|s-56797-VM]
2014-01-03 14:20:41,974 WARN  [cloud.api.ApiDispatcher] 
(Job-Executor-6:job-413) class com.cloud.api.ServerApiException : Fail to 
destroy system vm
2014-01-03 14:20:41,976 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-6:job-413) Complete async job-413, jobStatus: 2, resultCode: 530, 
result: Error Code: 530 Error text: Fail to destroy system vm
2014-01-03 14:20:46,454 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-7:null) Async job-413 completed
2014-01-03 14:20:48,328 DEBUG [storage.secondary.SecondaryStorageManagerImpl] 
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2014-01-03 14:20:48,437 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] 
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2014-01-03 14:20:48,982 DEBUG [storage.snapshot.SnapshotSchedulerImpl] 
(SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2014-01-03 
06:20:48 GMT
2014-01-03 14:20:48,984 DEBUG [storage.snapshot.SnapshotSchedulerImpl] 
(SnapshotPollTask:null) Got 0 snapshots to be executed at 2014-01-03 06:20:48 
GMT
2014-01-03 14:20:49,495 DEBUG 
[cloud.network.ExternalLoadBalancerUsageManagerImpl] 
(ExternalNetworkMonitor-1:null) External load balancer devices stats collector 
is running...
2014-01-03 14:20:49,549 DEBUG 
[network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:null) 
Found 0 running routers. 
2014-01-03 14:20:49,551 DEBUG 
[network.router.VirtualNetworkApplianceManagerImpl] 
(RouterStatusMonitor-1:null) Found 0 routers. 
2014-01-03 14:20:57,436 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-41:null) Ping from 8
2014-01-03 14:20:58,070 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-47:null) Ping from 25
2014-01-03 14:20:58,650 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-40:null) Seq 8-1694367746: Executing request
2014-01-03 14:20:59,072 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-148:null) Ping from 26
2014-01-03 14:20:59,080 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-47:null) Seq 25-1091043330: Executing request
2014-01-03 14:20:59,204 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-40:null) Seq 8-1694367746: Response Received: 
2014-01-03 14:20:59,204 DEBUG [agent.transport.Request] (DirectAgent-40:null) 
Seq 8-1694367746: Processing:  { Ans: , MgmtId: 690716576832, via: 8, Ver: v1, 
Flags: 10, 
[{"ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
 }
2014-01-03 14:20:59,263 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-47:null) Seq 25-1091043330: Response Received: 
2014-01-03 14:20:59,263 DEBUG [agent.transport.Request] (DirectAgent-47:null) 
Seq 25-1091043330: Processing:  { Ans: , MgmtId: 690716576832, via: 25, Ver: 
v1, Flags: 10, [{"Answer":{"result":true,"wait":0}}] }
2014-01-03 14:20:59,807 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-155:null) Seq 26-1719468034: Executing request
2014-01-03 14:20:59,996 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-155:null) Seq 26-1719468034: Response Received: 
2014-01-03 14:20:59,996 DEBUG [agent.transport.Request] (DirectAgent-155:null) 
Seq 26-1719468034: Processing:  { Ans: , MgmtId: 690716576832, via: 26, Ver: 
v1, Flags: 10, [{"Answer":{"result":true,"wait":0}}] }




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: users-cn-return-2879-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-2879-xusz=chinanetcenter@cloudstack.apache.org] 代表 
许叁征
发送时间: 2014年1月3日星期五 10:35
收件人: users-cn@cloudstack.apache.org
主题: 系统找不到二级存储

HI ALL 

 二级存储下载出现故障,Can't find a template to start Unexpected exception
Insufficient capacity exception

com.cloud.utils.exception.CloudRuntimeException: Insufficient capacity
exception

 系统是cs4.02+XENserver .删除了二级存储,重建的导入模板。再建立 二级存储,仍
然不行,看有没有人遇到,或是帮忙分析一下 

 

 

2014-01-03 10:31:57,734 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Assign
secondary storage vm from a newly started instance for request from data
center : 1

2014-01-03 10:31:57,836 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy

2014-01-03 10:31:57,857 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Found existing network configuration for offering
[Network Offering [6-Guest-DefaultSharedNetworkOfferingWithSGService]:
Ntwk[204|Guest|6]

2014-01-03 10:31:57,857 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Releasing lock for Acct[1-system]

2014-01-03 10:31:57,860 DEBUG [cloud.network.Netw

答复: 系统找不到二级存储

2014-01-02 文章

这些都是正常的,想问下,如果我删除了host表中的3个系统模板,这会导致模板下次无法下载吗?




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 


-邮件原件-
发件人: users-cn-return-2880-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-2880-xusz=chinanetcenter@cloudstack.apache.org] 代表 
guang wu
发送时间: 2014年1月3日星期五 11:20
收件人: users-cn@cloudstack.apache.org
主题: Re: 系统找不到二级存储

2014-01-03 10:31:57,875 DEBUG
[storage.secondary.
SecondaryStorageManagerImpl] (secstorage-1:null) Can't
find a template to start

从日志里不难发现,应该是你的模板没有下载到主存储上,新建虚拟机的时候没有模板所以创建失败。(注:添加二级存储时,2级存储里面一定要包含系统模板,好好检查下吧,如果没有,肯定有问题,如果已经有了,查看一下cloud数据库,template_spool_ref表中的download_state状态,如果是DOWNLOADED,将其改为NOT_DOWNLOADED,并把download_pct字段的值改为0),保存后,重启managment服务


系统找不到二级存储

2014-01-02 文章
HI ALL 

 二级存储下载出现故障,Can't find a template to start Unexpected exception
Insufficient capacity exception

com.cloud.utils.exception.CloudRuntimeException: Insufficient capacity
exception

 系统是cs4.02+XENserver .删除了二级存储,重建的导入模板。再建立 二级存储,仍
然不行,看有没有人遇到,或是帮忙分析一下 

 

 

2014-01-03 10:31:57,734 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Assign
secondary storage vm from a newly started instance for request from data
center : 1

2014-01-03 10:31:57,836 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy

2014-01-03 10:31:57,857 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Found existing network configuration for offering
[Network Offering [6-Guest-DefaultSharedNetworkOfferingWithSGService]:
Ntwk[204|Guest|6]

2014-01-03 10:31:57,857 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Releasing lock for Acct[1-system]

2014-01-03 10:31:57,860 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Found existing network configuration for offering
[Network Offering [3-Control-System-Control-Network]: Ntwk[202|Control|3]

2014-01-03 10:31:57,860 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Releasing lock for Acct[1-system]

2014-01-03 10:31:57,863 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Found existing network configuration for offering
[Network Offering [2-Management-System-Management-Network]:
Ntwk[201|Management|2]

2014-01-03 10:31:57,863 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Releasing lock for Acct[1-system]

2014-01-03 10:31:57,867 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Found existing network configuration for offering
[Network Offering [4-Storage-System-Storage-Network]: Ntwk[203|Storage|4]

2014-01-03 10:31:57,867 DEBUG [cloud.network.NetworkManagerImpl]
(secstorage-1:null) Releasing lock for Acct[1-system]

2014-01-03 10:31:57,875 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Can't
find a template to start

2014-01-03 10:31:57,875 WARN  [cloud.vm.SystemVmLoadScanner]
(secstorage-1:null) Unexpected exception Insufficient capacity exception

com.cloud.utils.exception.CloudRuntimeException: Insufficient capacity
exception

at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStorageVmIn
stance(SecondaryStorageManagerImpl.java:570)

at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(SecondarySt
orageManagerImpl.java:492)

at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(Second
aryStorageManagerImpl.java:661)

at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(Secondary
StorageManagerImpl.java:1310)

at
com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSeco
ndaryStorageManagerImpl.java:119)

at
com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSeco
ndaryStorageManagerImpl.java:50)

at
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:106)

at
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:34)

at
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:83)

at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:73)

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(ScheduledThreadPoolExecutor.java:267)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1146)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
15)

at java.lang.Thread.run(Thread.java:679)

2014-01-03 10:31:58,862 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers. 

2014-01-03 10:32:05,532 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-145:null) Ping from 30

2014-01-03 10:32:06,053 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-173:null) Ping from 29

2014-01-03 10:32:06,507 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-87:null) Seq 30-2067922946: Executing request

2014-01-03 10:32:06,666 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-87:null) Seq 30-2067922946: Response Received: 

2014-01-03 10:32:06,666 DEBUG [agent.transport.Request]
(DirectAgent-87:null) Seq 30-2067922946: Processing:  { Ans: , MgmtId:
690716576832, via: 30, Ver: v1, Flags: 10,
[{"Answer":{"result":true,"wait":0}}] }

2014-01-03 10:32:06,724 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-155:null) Seq 29-553648130: Executing request

2014-01-03 10:32:07,091 DEBUG [agent.manager.DirectAgen

答复: 按照一般节奏该有新版本出来了吧

2013-12-24 文章

4.2.1 会有一些什么改进,能支持CS主机两台同时负载均衡吗




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 


-邮件原件-
发件人: users-cn-return-2854-xusz=chinanetcenter@cloudstack.apache.org 
[mailto:users-cn-return-2854-xusz=chinanetcenter@cloudstack.apache.org] 代表 
Wei ZHOU
发送时间: 2013年12月24日星期二 15:53
收件人: users-cn@cloudstack.apache.org
主题: Re: 按照一般节奏该有新版本出来了吧

就这几天4.2.1会出来


在 2013年12月24日 上午8:19,陈珂 写道:

> 统计了一下历史版本的发布节奏,今年基本是2个月一个发布,是不是又要有新版本出来了
>
> 2013-12-24
>
>
>
> 陈珂
>


答复: 虚拟机无法关机

2013-12-23 文章



哦这样,我后面重启了,可以了, 经常发现虚拟机用了几天就会出现磁盘损失,然后
开机出现ctrl -D 这个是什么原因造成的


-邮件原件-
发件人: users-cn-return-2847-xusz=chinanetcenter@cloudstack.apache.org
[mailto:users-cn-return-2847-xusz=chinanetcenter@cloudstack.apache.org]
代表 Hongtu Zang
发送时间: 2013年12月23日星期一 16:50
收件人: users-cn@cloudstack.apache.org
主题: Re: 虚拟机无法关机

看上去是某一台主机挂掉或者网络断了


2013/12/23 许叁征 

>
>
> Hi ALL
>
> CS环境使用xenserver架构,现在关机虚拟机,机器久久未响应关机,出现以下错误
是什么意思 ,应该要怎么修复。先谢谢了!
>
>
>
>
>
> 2013-12-23 12:49:23,426 WARN  [agent.manager.DirectAgentAttache]
> (DirectAgent-399:null) Seq 12-956694530: Exception Caught while executing
> command
>
> com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
> slave 172.16.0.122 to 172.16.0.129 due to
> com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
> slave 172.16.0.122 to 172.16.0.129after 30 retry
>
>at
>
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyReset
Master(XenServerConnectionPool.java:443)
>
>at
>
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerC
onnectionPool.java:655)
>
>at
>
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixRes
ourceBase.java:5337)
>
>at
>
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceB
ase.java:7087)
>
>at
>
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixRe
sourceBase.java:535)
>
>at
>
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServ
er56Resource.java:73)
>
>at
>
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:
191)
>
>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
46)
>
>at
>
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
15)
>
>at java.lang.Thread.run(Thread.java:679)
>
> 2013-12-23 12:49:23,428 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-399:null) Seq 12-956694530: Response Received:
>
> 2013-12-23 12:49:23,428 DEBUG [agent.transport.Request]
> (DirectAgent-399:null) Seq 12-956694530: Processing:  { Ans: , MgmtId:
> 690716576832, via: 12, Ver: v1, Flags: 10,
>
[{"Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntime
Exception:
> Unable to reset master of slave 172.16.0.122 to 172.16.0.129 due to
> com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
> slave 172.16.0.122 to 172.16.0.129after 30 retry","wait":0}}] }
>
>
>
>
>
>
>
>
>
> 许叁征
>
> 网宿科技股份有限公司  厦门分公司 运营技术支持部
>
> [image: line1]
>
> Tel: <021-64871177>13860125907
>
> E-mail:x...@chinanetcenter.com
> http://www.chinanetcenter.com
>
> [image: cid:__1@Foxmail.net]
>
> 分公司:北京-上海-广州-深圳
>
> 免费咨询热线:800-820-0001
>
> 网宿科技 --卓越的互联网业务平台提供商
>
>
>  --
>
>
>




虚拟机无法关机

2013-12-22 文章
 

Hi ALL

CS环境使用xenserver架构,现在关机虚拟机,机器久久未响应关机,出现以下错误是
什么意思 ,应该要怎么修复。先谢谢了!

 

 

2013-12-23 12:49:23,426 WARN  [agent.manager.DirectAgentAttache]
(DirectAgent-399:null) Seq 12-956694530: Exception Caught while executing
command

com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 172.16.0.122 to 172.16.0.129 due to
com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 172.16.0.122 to 172.16.0.129after 30 retry

   at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyReset
Master(XenServerConnectionPool.java:443)

   at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerC
onnectionPool.java:655)

   at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixRes
ourceBase.java:5337)

   at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceB
ase.java:7087)

   at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixRe
sourceBase.java:535)

   at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServ
er56Resource.java:73)

   at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:
191)

   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
46)

   at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
15)

   at java.lang.Thread.run(Thread.java:679)

2013-12-23 12:49:23,428 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-399:null) Seq 12-956694530: Response Received: 

2013-12-23 12:49:23,428 DEBUG [agent.transport.Request]
(DirectAgent-399:null) Seq 12-956694530: Processing:  { Ans: , MgmtId:
690716576832, via: 12, Ver: v1, Flags: 10,
[{"Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntime
Exception: Unable to reset master of slave 172.16.0.122 to 172.16.0.129 due
to com.cloud.utils.exception.CloudRuntimeException: Unable to reset master
of slave 172.16.0.122 to 172.16.0.129after 30 retry","wait":0}}] }

 

 

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



答复: cloudstack如何应付网络环境 改变,

2013-11-28 文章

改DB里面的哪个表,可以详细一下吗




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 


-邮件原件-
发件人: Wei ZHOU [mailto:ustcweiz...@gmail.com] 
发送时间: 2013年11月28日星期四 17:26
收件人: users-cn@cloudstack.apache.org
主题: Re: cloudstack如何应付网络环境 改变,

改数据库,重启所有的systemvm 和virtual router


在 2013年11月28日上午10:22,许叁征 写道:

> HI ALL
> 碰上一个难题
>
> 公司的网络环境要改掉,网段要从172.16.0.*要改为172.16.151.*
> 使用的是xen+cs 4
> 基本网络 ,
> 有什么办法 可以让虚拟机迁移到新的网段上运行?
>
> 谢谢了
>


cloudstack如何应付网络环境 改变,

2013-11-28 文章
HI ALL
碰上一个难题 

公司的网络环境要改掉,网段要从172.16.0.*要改为172.16.151.*
使用的是xen+cs 4
基本网络 ,
有什么办法 可以让虚拟机迁移到新的网段上运行?

谢谢了


答复: 建立实例失败,是不是资源不够了

2013-11-28 文章

HI各位大神好:

公司的网络环境要改掉,网段要从172.16.0.*要改为172.16.151.* 有什么办法可以让虚拟机迁移到新的网段上运行?

谢谢
 





虚拟机无法启动

2013-10-29 文章
大家好,
请教一下生产环境 中,一个节点无法启动虚拟机,提示以下错误,
这个问题是什么意思,谢谢了
 2013-10-29 16:44:11,143 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] 
(consoleproxy-1:null) Zone host is ready, but console proxy template: 1 is not 
ready on secondary storage: 27
2013-10-29 16:44:41,047 DEBUG [storage.secondary.SecondaryStorageManagerImpl] 
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-10-29 16:44:50,422 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) There is no secondary storage VM for secondary storage 
host nfs://192.168.3.38/home/share/secondary
2013-10-29 16:44:50,424 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) There is no secondary storage VM for secondary storage 
host nfs://192.168.3.38/home/secondary
2013-10-29 16:44:50,425 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) There is no secondary storage VM for secondary storage 
host nfs://192.168.0.38/home/secondary
2013-10-29 16:44:50,426 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) There is no secondary storage VM for secondary storage 
host nfs://192.168.0.38/home/share/secondary
2013-10-29 16:45:11,047 DEBUG [storage.secondary.SecondaryStorageManagerImpl] 
(secstorage-1:null) Zone host is ready, but secondary storage vm template: 1 is 
not ready on secondary storage: 27
2013-10-29 16:45:11,047 DEBUG [storage.secondary.SecondaryStorageManagerImpl] 
(secstorage-1:null) Zone 1 is not ready to launch secondary storage VM yet
2013-10-29 16:45:11,141 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] 
(consoleproxy-1:null) Zone host is ready, but console proxy template: 1 is not 
ready on secondary storage: 27



答复: Fail to register iso template

2013-10-28 文章
 
HI ALL
添加一节点提示以下出错,这是什么原因。


Cannot transit agent status with event AgentDisconnected for host 23,
mangement server id is 110480925280,Unable to transition to a new state from
Creating via AgentDisconnected



 



答复: 回复: Re: 在windows下编译cloudstack4.1.1

2013-09-23 文章
Hi all
生产环境中,物理节点xenserver 1重启了 ,通过xen-client控制终端可以连接上。 但是平台显示为down ,强制连接机器command 
failed due to internal server error
这是怎么回事,请教各位大神!
  



-邮件原件-
发件人: Jijun [mailto:jiju...@gmail.com] 
发送时间: 2013年9月23日星期一 8:42
收件人: users-cn@cloudstack.apache.org
主题: Re: 回复: Re: 在windows下编译cloudstack4.1.1

On 09/22/2013 12:29 PM, toudsf wrote:
> 请问怎么解决的。我也出现这个问题了。谢谢!
>
> 2013-09-22
缺少python2的setuptools
https://pypi.python.org/pypi/setuptools


>
>
> toudsf
>
>
>
> 发件人:qin wu 
> 发送时间:2013-09-22 12:28
> 主题:Re: 在windows下编译cloudstack4.1.1
> 收件人:"users-cn"
> 抄送:
>
> 解决了
>
>
> 2013/9/22 toudsf <18600601...@163.com>
>
>> 您这个问题解决了吗?
>>
>> 2013-09-22
>>
>>
>>
>> toudsf
>>
>>
>>
>> 发件人:qin wu 
>> 发送时间:2013-08-12 20:41
>> 主题:在windows下编译cloudstack4.1.1
>> 收件人:"cloudstack-users...@incubator.apache.org"<
>> cloudstack-users...@incubator.apache.org>
>> 抄送:
>>
>> 我按照《1 cloudstack开发环境设置-windows篇》进行了配置,尝试编译4.1.1。命令: mvn  clean install -P
>> systemvm ,developer但出现一下问题
>> main:
>> [delete] Deleting directory
>> C:\workspace\cloudstack\tools\marvin\marvin\cloudstackAPI
>> [INFO] Executed tasks
>> [INFO]
>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile) @ cloud-marvin ---
>> [INFO]
>> [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
>> cloud-marvin ---
>> [INFO]
>> [INFO] --- exec-maven-plugin:1.2.1:exec (package) @ cloud-marvin ---
>> Traceback (most recent call last):
>>File "setup.py", line 19, in 
>>  from setuptools import setup
>> ImportError: No module named setuptools
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache CloudStack . SUCCESS [9.312s]
>> [INFO] Apache CloudStack Utils ... SUCCESS
>> [36.469s]
>> [INFO] Apache CloudStack API . SUCCESS
>> [56.156s]
>> [INFO] Apache CloudStack Core  SUCCESS
>> [18.157s]
>> [INFO] Apache CloudStack Agents .. SUCCESS
>> [32.765s]
>> [INFO] Apache CloudStack SystemVM Patches  SUCCESS [4.094s]
>> [INFO] Apache CloudStack Console Proxy ... SUCCESS
>> [35.031s]
>> [INFO] Apache CloudStack Framework ... SUCCESS [0.250s]
>> [INFO] Apache CloudStack Framework - IPC . SUCCESS
>> [13.313s]
>> [INFO] Apache CloudStack Framework - REST  SUCCESS
>> [10.765s]
>> [INFO] Apache CloudStack Cloud Engine  SUCCESS [0.219s]
>> [INFO] Apache CloudStack Cloud Engine API  SUCCESS
>> [11.391s]
>> [INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [4.265s]
>> [INFO] Apache CloudStack Server .. SUCCESS
>> [1:50.313s]
>> [INFO] Apache CloudStack Usage Server  SUCCESS
>> [38.531s]
>> [INFO] Apache XenSource XAPI . SUCCESS
>> [15.750s]
>> [INFO] Apache CloudStack Plugin POM .. SUCCESS [0.953s]
>> [INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS
>> [13.625s]
>> [INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [8.891s]
>> [INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [4.875s]
>> [INFO] Apache CloudStack Plugin - User Concentrated Pod Deployment Planner
>>   SUCCESS [4.484s]
>> [INFO] Apache CloudStack Plugin - User Dispersing Deployment Planner
>>   SUCCESS [4.828s]
>> [INFO] Apache CloudStack Plugin - Host Allocator Random .. SUCCESS [4.407s]
>> [INFO] Apache CloudStack Plugin - Hypervisor OracleVM  SUCCESS [7.000s]
>> [INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS
>> [4.531s]
>> [INFO] Apache CloudStack Engine Storage Component  SUCCESS
>> [14.953s]
>> [INFO] Apache CloudStack Plugin - Open vSwitch ... SUCCESS [7.656s]
>> [INFO] Apache CloudStack Plugin - Hypervisor Xen . SUCCESS
>> [10.406s]
>> [INFO] Apache CloudStack Plugin - Hypervisor KVM . SUCCESS
>> [30.282s]
>> [INFO] Apache CloudStack Plugin - RabbitMQ Event Bus . SUCCESS [7.297s]
>> [INFO] Apache CloudStack Plugin - Hypervisor Simulator ... SUCCESS
>> [11.765s]
>> [INFO] Apache CloudStack Plugin - Network Elastic Load Balancer  SUCCESS
>> [5.578s]
>> [INFO] Apache CloudStack Plugin - Network Nicira NVP . SUCCESS
>> [16.438s]
>> [INFO] Apache CloudStack Plugin - BigSwitch Virtual Network Segment
>>   SUCCESS [9.062s]
>> [INFO] Apache CloudStack Plugin - Storage Allocator Random  SUCCESS
>> [3.719s]
>> [INFO] Apache CloudStack Plugin - User Authenticator LDAP  SUCCESS [3.719s]
>> [INFO] Apache CloudStack Plugin - User Authenticator MD5 . SUCCESS [3.906s]
>> [INFO] Apache CloudStack Plugin - User Authenticator Plain Text  SUCCESS
>> [4.078s]
>> [INFO] Apache CloudStack Plugin - User Authenticator SHA256 Salted  SUCCESS
>> [6.344s]
>> [INFO] Apache CloudStack Plugin - Dns Notifier Example ... SUCCESS [3.687s]
>> [INFO] Apache CloudStack Engine Storage Im

群集中的虚拟机启动问题

2013-09-13 文章
 HI ALL

 

 每台虚拟机都安装xen―tools 并设置了虚拟机启动为自动轮训任意选择节点启动

现有四台节点xenserver ,其中一台物理节点 设置维护模式后,并关机了,上面运行的
虚拟机i-3-5-VM在CS平台上发现也相停止,观察数分钟后,机器扔然不会在其它的节点
上实现启动

如何解决?实现节点一台关机后,能自动在另一台节点上启动起来

 

 

 

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



答复: xenserver虚拟机迁移

2013-09-13 文章
新的架构网络:172.16.11.* 节点有四台XENSEVER

原来的是192.168.3.* 虚拟机也是192.168.3.*  机器,
两个网络互不不通。

如何实现能导入新的架构平台上,然后原的CS主机能管理到原来的虚拟机。

 



-邮件原件-
发件人: Gavin Lee [mailto:gavin@gmail.com] 
发送时间: 2013年9月12日星期四 9:43
收件人: users-cn@cloudstack.apache.org
主题: Re: xenserver虚拟机迁移

你这问题没法回答,172.11.11段的IP是VM的还是XenServer管理网的?虚拟机原来所在
的管理网是什么?
如果两个IP都是VM的,你直接改IP然后路由不就得了?



2013/9/5 许叁征 

>  大家好,
>
> 请教 下,现在有xenserver 虚拟机192.68.3.34 的虚拟 机有数台想迁移到不同网段
的172.11.11.上去,目标也是xenserver
> 
>
>  如何操作。
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> 许叁征
>
> 网宿科技股份有限公司  厦门分公司 运营技术支持部
>
> [image: line1]
>
> Tel: <021-64871177>13860125907  
>
> E-mail:x...@chinanetcenter.com
> http://www.chinanetcenter.com
>
> [image: cid:__1@Foxmail.net]
>
> 分公司:北京-上海-广州-深圳   
>
> 免费咨询热线:800-820-0001
>
> 网宿科技 --卓越的互联网业务平台提供商
>
>  
>  --
>
> ** **
>



-- 
Gavin


答复: CloudStack技术沙龙19期北京站

2013-09-13 文章
HI ALL


 如何让群集的xenserver 虚拟机 ,在一台节点宕机的情况下,虚拟机从另一台可用的
的节点上自动启动


 


xenserver虚拟机迁移

2013-09-05 文章
大家好,

请教 下,现在有xenserver 虚拟机192.68.3.34 的虚拟 机有数台想迁移到不同网段的
172.11.11.上去,目标也是xenserver 

 如何操作。

 

 

 

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



安装cloudstack问题

2013-08-27 文章
HI

各位大神 安装 cloudstack4.0.1的按下U提示出现以下错误,这个要如何解决。

 

 

 

 

   U) Upgrade the CloudStack packages installed on this computer

R) Stop any running CloudStack services and remove the CloudStack
packages from this computer

Q) Quit

 

> U

Updating the CloudStack and its dependencies...

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

 * base: centos.ustc.edu.cn

 * extras: centos.ustc.edu.cn

 * updates: centos.ustc.edu.cn

base
| 3.7 kB 00:00 

file:///root/CloudStack-non-OSS-13/repodata/repomd.xml: [Errno 14] Could not
open/read file:///root/CloudStack-non-OSS-13/repodata/repomd.xml

Trying other mirror.

Error: Cannot retrieve repository metadata (repomd.xml) for repository:
cloud-temp. Please verify its path and try again

Done

 

 

 



cs重启后就无法登陆,进程挂死

2013-08-21 文章
 Hi ALL
 CS重启后,发现系统无法登陆,进程 挂死,这个要如何处理

[root@manager ~]# service cloud-management restart
Stopping cloud-management: [确定]
Starting cloud-management: [确定]
[root@manager ~]# rm /var/lock/subsys/cloud-management
rm: remove regular empty file `/var/lock/subsys/cloud-management'? y
[root@manager ~]# service cloud-management status
cloud-management 已死,但 pid 文件仍存
The pid file locates at /var/run/cloud-management.pid and lock file at 
/var/lock/subsys/cloud-management.
Starting cloud-management will take care of them or you can manually 
clean up.
[root@manager ~]# rm /var/run/cloud-management.pid 
rm: remove regular file `/var/run/cloud-management.pid'? y
[root@manager ~]# service cloud-management start
Starting cloud-management: [确定]
[root@manager ~]# netstat -an |grep 8080
[root@manager ~]# netstat -an 
Active Internet connections (servers and established)



许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: zanghongtu2006 [mailto:zanghongtu2...@gmail.com] 
发送时间: 2013年8月21日星期三 16:51
收件人: users-cn
主题: Re: 答复: 资源不足,无法创建虚拟机

搜一下overprovision
大概相关的超配比例都在那




zanghongtu2006

发件人: 许叁征
发送时间: 2013-08-21 16:39
收件人: users-cn@cloudstack.apache.org
主题: 答复: 资源不足,无法创建虚拟机

修改全局变量的的资源超配比例

是哪个参数 ,




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商



-邮件原件-
发件人: 陈珂 [mailto:che...@ourfuture.cn] 
发送时间: 2013年8月19日星期一 19:23
收件人: users-cn
主题: Re: 资源不足,无法创建虚拟机

修改全局变量的的资源超配比例。


2013-08-19 



陈珂 



发件人: 许叁征 
发送时间: 2013-08-19  19:19:28 
收件人: users-cn@cloudstack.apache.org 
抄送: 
主题: 资源不足,无法创建虚拟机 


Hi all
发现CS系统机器还有资源,可是却无法再创建虚拟机了,
当删除了一台机器后,再创建一台机器,就可以。
请问,在哪边可以修改配置,让系统接着创建虚拟机。
如希望内存达到28GB的时候无法再创建。







许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商


答复: 答复: 资源不足,无法创建虚拟机

2013-08-21 文章
 
cluster.memory.allocated.capacity.disablethreshold

Percentage (as a value between 0 and 1) of memory utilization above 
which allocators will disable using the cluster for low memory available. Keep 
the corresponding notification threshold lower than this to be notified 
beforehand. 
 如果后面的值设为0.95 这样是不是说  Cluster内存资源使用达到95%时 就无法再创建虚拟机了吧
如果用的值比较高,这样对物理机有什么影响 ?
会不会导致 整个系统XENserver挂掉?
一般建议设置保留多少合理。



许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: Jijun [mailto:jiju...@gmail.com] 
发送时间: 2013年8月21日星期三 16:49
收件人: users-cn@cloudstack.apache.org
主题: Re: 答复: 资源不足,无法创建虚拟机

On 08/21/2013 04:39 PM, 许叁征 wrote:
> 如希望内存达到28GB的时候无法再创建。
默认情况下,如果Cluster内存资源使用达到85%时,CPU资源使用达到85%就会禁止 
创建VM,
可以通过修改全局参数:
cluster.cpu.allocated.capacity.disablethreshold
cluster.memory.allocated.capacity.disablethreshold
继续创建VM。

-- 
Thanks,
Jijun


答复: 答复: 资源不足,无法创建虚拟机

2013-08-21 文章
cpu.overprovisioning.factor Used for CPU overprovisioning calculation; 
available CPU will be (actualCpuCapacity * cpu.overprovisioning.factor)  1  
 

mem.overprovisioning.factor Used for memory overprovisioning calculation
1   

storage.overprovisioning.factor Used for storage overprovisioning calculation; 
available storage will be (actualStorageSize * storage.overprovisioning.factor) 
  2 

这些要怎么改啊





许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: zanghongtu2006 [mailto:zanghongtu2...@gmail.com] 
发送时间: 2013年8月21日星期三 16:51
收件人: users-cn
主题: Re: 答复: 资源不足,无法创建虚拟机

搜一下overprovision
大概相关的超配比例都在那




zanghongtu2006

发件人: 许叁征
发送时间: 2013-08-21 16:39
收件人: users-cn@cloudstack.apache.org
主题: 答复: 资源不足,无法创建虚拟机

修改全局变量的的资源超配比例

是哪个参数 ,




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商



-邮件原件-
发件人: 陈珂 [mailto:che...@ourfuture.cn] 
发送时间: 2013年8月19日星期一 19:23
收件人: users-cn
主题: Re: 资源不足,无法创建虚拟机

修改全局变量的的资源超配比例。


2013-08-19 



陈珂 



发件人: 许叁征 
发送时间: 2013-08-19  19:19:28 
收件人: users-cn@cloudstack.apache.org 
抄送: 
主题: 资源不足,无法创建虚拟机 


Hi all
发现CS系统机器还有资源,可是却无法再创建虚拟机了,
当删除了一台机器后,再创建一台机器,就可以。
请问,在哪边可以修改配置,让系统接着创建虚拟机。
如希望内存达到28GB的时候无法再创建。







许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商


答复: 资源不足,无法创建虚拟机

2013-08-21 文章

修改全局变量的的资源超配比例

是哪个参数 ,




许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 


-邮件原件-
发件人: 陈珂 [mailto:che...@ourfuture.cn] 
发送时间: 2013年8月19日星期一 19:23
收件人: users-cn
主题: Re: 资源不足,无法创建虚拟机

修改全局变量的的资源超配比例。


2013-08-19 



陈珂 



发件人: 许叁征 
发送时间: 2013-08-19  19:19:28 
收件人: users-cn@cloudstack.apache.org 
抄送: 
主题: 资源不足,无法创建虚拟机 
 
 
Hi all
发现CS系统机器还有资源,可是却无法再创建虚拟机了,
当删除了一台机器后,再创建一台机器,就可以。
请问,在哪边可以修改配置,让系统接着创建虚拟机。
如希望内存达到28GB的时候无法再创建。
 
 
 

 
 
 
许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商

 



 


资源不足,无法创建虚拟机

2013-08-19 文章
 

Hi all

发现CS系统机器还有资源,可是却无法再创建虚拟机了,

当删除了一台机器后,再创建一台机器,就可以。

请问,在哪边可以修改配置,让系统接着创建虚拟机。

如希望内存达到28GB的时候无法再创建。

 

 

 



 

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



答复: Cloudstack源代码阅读问题+更改问题

2013-07-17 文章


请问如何退订本邮件了,谢谢



许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: Yongchuan Dai [mailto:dyc...@gmail.com] 
发送时间: 2013年7月13日星期六 21:14
收件人: users-cn
主题: Cloudstack源代码阅读问题+更改问题

各位大牛,我已经建立起cloudstack的平台,已经测试过了。我现在想对其中的一些功能进行修改和添加。首先是阅读其源代码的问题,望大牛给出点指导性意见


答复: 求助:如何让CS创建的虚拟机禁止访问外网

2013-06-04 文章
那上面可以设置什么 规则吗,我是使用基本网络的,原来有很多虚拟机在使用中,要是再建的话,可能工作量比较大,
原来的默认规则中,可以添加端口,但是里面怎么没有禁止或是允许的策略





许叁征
网宿科技股份有限公司  厦门分公司 运营技术支持部

Tel:13860125907  
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com

分公司:北京-上海-广州-深圳   
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
 



-邮件原件-
发件人: Fan Lei [mailto:leifan8...@gmail.com] 
发送时间: 2013年6月5日星期三 13:51
收件人: users-cn@cloudstack.apache.org
主题: Re: 求助:如何让CS创建的虚拟机禁止访问外网

从物理网络设备上设置
或者  建一个不用source nat的网络方案叫AA,再建一个用这个网络方案AA的的网络,建vm的时候选这个网络


在 2013年6月5日下午1:41,许叁征 写道:

>  HI 大家
>
> 公司有需求量让虚拟机不访问外网,
>
> 求助,如何让CS创建的虚拟机禁止访问外网?
>
> 如果是在r—route中配置 ,是如何添加例子,
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> 许叁征
>
> 网宿科技股份有限公司  厦门分公司 运营技术支持部
>
> [image: line1]
>
> Tel: <021-64871177>13860125907  
>
> E-mail:x...@chinanetcenter.com
> http://www.chinanetcenter.com
>
> [image: cid:__1@Foxmail.net]
>
> 分公司:北京-上海-广州-深圳   
>
> 免费咨询热线:800-820-0001
>
> 网宿科技 --卓越的互联网业务平台提供商
>
>  
>  --
>
> ** **
>


求助:如何让CS创建的虚拟机禁止访问外网

2013-06-04 文章
HI 大家

公司有需求量让虚拟机不访问外网,

求助,如何让CS创建的虚拟机禁止访问外网?

如果是在r―route中配置 ,是如何添加例子,

 

 

 

 

许叁征

网宿科技股份有限公司  厦门分公司 运营技术支持部


line1


  Tel:13860125907  

E-mail:x...@chinanetcenter.com
 <http://www.chinanetcenter.com/> http://www.chinanetcenter.com

cid:__1@Foxmail.net

分公司:北京-上海-广州-深圳   

免费咨询热线:800-820-0001

网宿科技 --卓越的互联网业务平台提供商

 

  _  

 



答复: 请问怎么退出这个群组

2013-05-17 文章

我也想推出,申请

  


-邮件原件-
发件人: 李伏琼 [mailto:li_fuqi...@venustech.com.cn] 
发送时间: 2013年5月16日星期四 18:03
收件人: users-cn
主题: 请问怎么退出这个群组

请问怎么退出这个群组?




李伏琼

北京启明星辰信息安全技术有限公司 泰合中心TSOC应用研发部
地址:北京市海淀区东北旺西路8号中关村软件园21号启明星辰大厦
邮编:100193
网站:www.venustech.com.cn
手机:13810108173