cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tanthalas <tanthalas...@hotmail.com>
Subject Re: Re:Re:_Re:_Re:_Re:_Re:_请教添加存储错误
Date Wed, 19 Mar 2014 05:51:28 GMT

就是因为你重命名了,所以log里显示的很清楚找不到管理网络的端口组。你最后说的这句话才是问题的原因。
Uanble to find management port group Management Network
想改名是支持的但是需要在CloudStack里进行配置,指定CS去找你改过名字的端口组及vSwitch

刘宇超



发件人: 上海-SF 
发送时间: 2014-03-18  09:34:57 
收件人: users-cn 
抄送: 
主题: Re:Re:_Re:_Re:_Re:_Re:_请教添加存储错误 
 
我在VCENTER中删除了该主机、集群、数据中心,全部重建,把cloudstack数据库等也清空了重建还是报同样的错误,主机仍旧添加不进去,该台主机我配置了多个vswitch,并且把所有的端口(包括管理流量端口)都进行了重命名,不知道这样是不是有什么影响?
在 2014-03-17 16:51:54,"Bo Wang" <brito.wang@gmail.com> 写道:
>你添加的主机有问题,建议你把集群删掉(反正你现在的vmware集群也是空的),去v-center里把主机环境顺便清空一下(这时候这个主机应该是在v-center里的一个集群里的),重新添加这个vmware集群,添加完以后你会发现这个主机也就被添加进去了。
>
>
>在 2014年3月17日 下午4:32,上海-SF <xuanbcx@163.com>写道:
>
>> 基础架构中ZONE,POD,cluster,二级存储都有内容,主机显示为0,我手动添加ESXI主机IP地址进去,点击添加后提示失败,下面为日志,数据库host表显示为empty
>> set ,没有数据。
>>
>> 2014-03-17 09:45:13,650 DEBUG [cloud.api.ApiServlet]
>> (catalina-exec-22:null) ===START===  172.19.102.99 -- POST
>>  command=addHost&response=json&sessionkey=MUnt%2BRPKWg3OynJo7kW%2F8uixomY%3D
>> 2014-03-17 09:45:13,684 INFO  [cloud.resource.ResourceManagerImpl]
>> (catalina-exec-22:null) Trying to add a new host at
>> http://172.19.116.42/zhongxin/ji/172.19.116.40 in data center 1
>> 2014-03-17 09:45:13,684 INFO  [hypervisor.vmware.VmwareServerDiscoverer]
>> (catalina-exec-22:null) Discover host. dc: 1, pod: 1, cluster: 1, uri host:
>> 172.19.116.42
>> 2014-03-17 09:45:13,786 DEBUG [vmware.resource.VmwareContextFactory]
>> (catalina-exec-22:null) initialize VmwareContext. url:
>> https://172.19.116.42/sdk/vimService, username: administrator, password:
>> h************
>> 2014-03-17 09:45:13,972 INFO  [vmware.util.VmwareContext]
>> (catalina-exec-22:null) New VmwareContext object, current outstanding
>> count: 4
>> 2014-03-17 09:45:14,066 INFO  [vmware.manager.VmwareManagerImpl]
>> (catalina-exec-22:null) Preparing network on host
>> com.cloud.hypervisor.vmware.util.VmwareContext@70184e5d for vSwitch0
>> 2014-03-17 09:45:14,183 INFO  [vmware.mo.HypervisorHostHelper]
>> (catalina-exec-22:null) Network cloud.private.untagged.0.1-vSwitch0 is
>> ready on vSwitch vSwitch0
>> 2014-03-17 09:45:14,260 DEBUG [vmware.resource.VmwareContextFactory]
>> (catalina-exec-22:null) initialize VmwareContext. url:
>> https://172.19.116.42/sdk/vimService, username: administrator, password:
>> h************
>> 2014-03-17 09:45:14,396 INFO  [vmware.util.VmwareContext]
>> (catalina-exec-22:null) New VmwareContext object, current outstanding
>> count: 5
>> 2014-03-17 09:45:14,486 INFO  [vmware.resource.VmwareResource]
>> (catalina-exec-22:null) VmwareResource network configuration info. private
>> traffic over vSwitch: null, public traffic over vmwaresvs : vSwitch0, guest
>> traffic over vmwaresvs : vSwitch0
>> 2014-03-17 09:45:15,239 INFO  [vmware.resource.VmwareResource]
>> (catalina-exec-22:null) Startup report on host hardware info.
>> {"memoryBytes":12874137600,"cpuCount":16,"cpuSpeed":2800}
>> 2014-03-17 09:45:15,365 ERROR [vmware.resource.VmwareResource]
>> (catalina-exec-22:null) querying host network info failed due to Exception:
>> java.lang.Exception
>> Message: Uanble to find management port group Management Network
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 在 2014-03-17 15:51:40,"Bo Wang" <brito.wang@gmail.com> 写道:
>> >我的意思是你在cloudstack
>>
>> >UI里的基础架构里查一下HOST的状态是不是Up,如果可以的话顺便去数据库检查一下主机(host表)的type是不是Routing.总之就是检查你的环境。你的log显示出来,cloudstack不能找到合适的主机去挂载这个主存储。
>> >
>> >
>> >在 2014年3月17日 下午3:41,上海-SF <xuanbcx@163.com>写道:
>> >
>> >> VCENTER上能挂上主存储,CLOUDSTACK上怎么检查啊,我查了cloudstack-management服务是running的
>> >>
>> >>
>> >>
>> >>
>> >> 在 2014-03-17 13:57:08,"Bo Wang" <brito.wang@gmail.com> 写道:
>> >> >你手动在v-center给Host上挂一下你的那个主存储
>> >> >看看是否挂的上,如果挂的上就是你的cloudstack的问题了,在cloudstack上检查一下你的主机有什么问题没,看状态是不是up.
>> >> >
>> >> >
>> >> >在 2014年3月15日 上午1:44,上海-SF <xuanbcx@163.com>写道:
>> >> >
>> >> >>
>> >> >>
>> >>
>> 日志如下显示,我计划的是一级二级存储都是挂载管理机本地磁盘,第一次初始化配置的时候执行到一级存储这里就报错退出,我在“基础架构”中手动添加同样失败,手动添加二级存储是成功的,二级存储添加后主机也没有不正常的表现,服务都正常运行,我的环境一共3台物理机,一台管理机CENTOS6.5的,CS4.2.1版本,一台计算节点,装的ESXI5.1,上面没有跑虚机,另外一台机器上跑VCENTER5.1
>> >> >>
>> >> >> 2014-03-15 01:34:21,993 DEBUG [cloud.api.ApiServlet]
>> >> >> (catalina-exec-10:null) ===START===  172.19.102.99 -- GET
>> >> >>
>> >>
>>  command=createStoragePool&scope=cluster&zoneid=440d9142-71ea-4969-b5d1-c8cd50060189&podid=4e1f02c3-98e9-4030-ae98-bba68c92ca1a&clusterid=1f47b676-c486-4578-8a2f-523fa7ede378&name=pri&url=nfs%3A%2F%2F172.19.102.188%2Fexport%2Fprimary&response=json&sessionkey=XD4TO47Hf%2FJ4z%2BJx3sYEaNkZP2A%3D&_=1394818461790
>> >> >> 2014-03-15 01:34:22,011 DEBUG
>> >> >> [datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
>> >> >> (catalina-exec-10:null) createPool Params @ scheme - nfs storageHost
>> -
>> >> >> 172.19.102.188 hostPath - /export/primary port - -1
>> >> >> 2014-03-15 01:34:22,172 DEBUG [cloud.storage.StorageManagerImpl]
>> >> >> (catalina-exec-10:null) Failed to add data store
>> >> >> com.cloud.utils.exception.CloudRuntimeException: No host up to
>> >> associate a
>> >> >> storage pool with in cluster 1
>> >> >>         at
>> >> >>
>> >>
>> org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.attachCluster(CloudStackPrimaryDataStoreLifeCycleImpl.java:371)
>> >> >>         at
>> >> >>
>> >>
>> com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:759)
>> >> >>         at
>> >> >>
>> >>
>> com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:179)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:168)
>> >> >>         at
>> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
>> >> >>         at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
>> >> >>         at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
>> >> >>         at
>> com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
>> >> >>         at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
>> >> >>         at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>> >> >>         at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
>> >> >>         at
>> >> >>
>> >>
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
>> >> >>         at
>> >> >>
>> >>
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>> >> >>         at
>> >> >>
>> >>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> >> >>         at java.lang.Thread.run(Thread.java:701)
>> >> >> 2014-03-15 01:34:22,175 INFO  [cloud.api.ApiServer]
>> >> >> (catalina-exec-10:null) Failed to add data store
>> >> >> 2014-03-15 01:34:22,176 DEBUG [cloud.api.ApiServlet]
>> >> >> (catalina-exec-10:null) ===END===  172.19.102.99 -- GET
>> >> >>
>> >>
>>  command=createStoragePool&scope=cluster&zoneid=440d9142-71ea-4969-b5d1-c8cd50060189&podid=4e1f02c3-98e9-4030-ae98-bba68c92ca1a&clusterid=1f47b676-c486-4578-8a2f-523fa7ede378&name=pri&url=nfs%3A%2F%2F172.19.102.188%2Fexport%2Fprimary&response=json&sessionkey=XD4TO47Hf%2FJ4z%2BJx3sYEaNkZP2A%3D&_=1394818461790
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> 在 2014-03-14 10:00:17,"Bo Wang" <brito.wang@gmail.com>
写道:
>> >> >> >一个错误的关键信息应该在Exception前面的那些log,后面的at
com.xxx什么的其实没什么用
>> >> >> >你应该把前面的那些信息发出来
>> >> >> >
>> >> >>
>> >> >>
>> >>
>> >看提示是在该集群中找不到up状态,resource_state为enbale的主机,你查看一下主机的状态是不是在挂载完二级存储以后主机就down掉了。
>> >> >> >
>> >> >> >
>> >> >> >在 2014年3月12日 下午4:23,上海-SF <xuanbcx@163.com>写道:
>> >> >> >
>> >> >> >> 一个计算节点,ESXI底层,上面装有VCENTER虚拟机,这个是全新安装完,在第一次配置基础架构的时候报的错误
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> 在 2014-03-12 16:07:12,"linuxbqj@gmail.com" <linuxbqj@gmail.com>
>> 写道:
>> >> >> >> >Resource [Pod:1] is unreachable: No host up to associate
a
>> storage
>> >> >> >> >pool with in cluster 1
>> >> >> >> >
>> >> >> >> >你有几个计算节点?是刚安装完的初始化出错的吗?
>> >> >> >> >
>> >> >> >> >2014-03-12 15:30 GMT+08:00 上海-SF <xuanbcx@163.com>:
>> >> >> >> >>  centos
>> >> >> >>
>> >> 6.5,CS版本4.0.2,就在本地系统中建了两个目录,用于挂载主辅存储,现在辅存储能挂载上,主存储挂载报错,报错信息如下,请教一下是什么问题:
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:1268)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:215)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> com.cloud.api.commands.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:120)
>> >> >> >> >>         at
>> >> >> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
>> >> >> >> >>         at
>> >> com.cloud.api.ApiServer.queueCommand(ApiServer.java:544)
>> >> >> >> >>         at
>> >> com.cloud.api.ApiServer.handleRequest(ApiServer.java:423)
>> >> >> >> >>         at
>> >> >> com.cloud.api.ApiServlet.processRequest(ApiServlet.java:312)
>> >> >> >> >>         at com.cloud.api.ApiServlet.doGet(ApiServlet.java:64)
>> >> >> >> >>         at
>> >> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>> >> >> >> >>         at
>> >> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>> >> >> >> >>         at
>> >> >> >>
>> >> >>
>> >>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> >> >> >> >>         at java.lang.Thread.run(Thread.java:701)
>> >> >> >> >> WARN  [cloud.api.ApiDispatcher] (catalina-exec-2:)
class
>> >> >> >> com.cloud.api.ServerApiException : Resource [Pod:1] is
>> unreachable:
>> >> No
>> >> >> host
>> >> >> >> up to associate a storage pool with in cluster 1
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >--
>> >> >> >> >白清杰 (Born Bai)
>> >> >> >> >
>> >> >> >> >北京开源愿景信息技术有限公司
>> >> >> >> >
>> >> >> >> >Mail: linuxbqj@gmail.com
>> >> >> >>
>> >> >>
>> >>
>>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message