cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hongtu Zang <zanghongtu2...@gmail.com>
Subject Re: 我是新手,新装cs 4.4。2无法添加kvm主机至cs中 "Unable to add the host"
Date Thu, 07 May 2015 04:46:05 GMT
1、management Server需要执行cloud-setup-management,kvm需要执行cloud-setup-agent
2、8250没连上,可能是management Server的防火墙原因,把防火墙先关掉试试看


2015-04-25 13:01 GMT+08:00 惠宾 <huibin@qq.com>:

> client装了吗?------------------ 原始邮件 ------------------
> 发件人: "韩登"<handeng@126.com>
> 发送时间: 2015年4月25日(星期六) 中午12:06
> 收件人: "users-cn@cloudstack.apache.org"<users-cn@cloudstack.apache.org>;
> 主题: Re: 我是新手,新装cs 4.4。2无法添加kvm主机至cs中 "Unable to add
the host"
>
>
> 检查一下个各主机的host文件是否都完整正确
> On 04/25/2015 12:01, 冷雨 wrote:
>    打扰了,我最近在进行服务器虚拟化集中管理平台选型,现安装了cs
4.4.2版,主机为kvm(基于CentOS 6.5
> x86_x64)。现在部署过程中碰到一些问题,想请帮我一下:
> 现在cs与kvm主机均已装好,但通过http://<cloudstack-server-IP>:8080/client登录后添加主机时总是报“Unable
> to add the host”,尝试数次均如此。期间做了如下尝试:
> 1、将cs与kvm 主机分开安装(本来是合在一起的)
> 2、重装cs与kvm主机
>
> 我根据网上搜索到的资料看了一些后台日志,但没看出问题。
>
> 疑问:从哪里入口查这个问题,看日志好像是一个好注意,但不知应关注哪些日志。如何来解读这些日志。
>
> agent.log如下:(日志最后部分)
>
> 2015-04-25 11:33:54,740{GMT} INFO  [utils.nio.NioClient] (Agent-Selector:)
> Connecting to 192.168.1.173 :8250
> 2015-04-25 11:34:04,761{GMT} ERROR [utils.nio.NioConnection]
> (Agent-Selector:) Unable to initialize the threads due to unknown exception.
> java.nio.channels.UnresolvedAddressException
>        at sun.nio.ch.Net.checkAddress(Net.java:127)
>        at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:644)
>        at com.cloud.utils.nio.NioClient.init(NioClient.java:67)
>        at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111)
>        at java.lang.Thread.run(Thread.java:745)
>
> management-server.log如下:(日志最后部分)
>
> 2015-04-25 11:33:56,584 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-2:ctx-f1deaf2c) AutoScaling Monitor is running...
> 2015-04-25 11:33:57,049 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-1:ctx-1ce8d0a6) VmStatsCollector is running...
> 2015-04-25 11:33:58,390 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-dfcd1954) Skip capacity scan due to there is no Primary
> Storage UPintenance mode
> 2015-04-25 11:33:58,638 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-4:ctx-56e5aeb3) StorageCollector is running...
> 2015-04-25 11:33:58,990 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-3:ctx-19cad887) HostStatsCollector is running...
> 2015-04-25 11:34:09,194 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-c3b9f19a) Found 0 routers to update status.
> 2015-04-25 11:34:09,197 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-c3b9f19a) Found 0 networks to update RvR status.
> 2015-04-25 11:34:14,483 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-ed6c8947) Resetting hosts suitable for reconnect
> 2015-04-25 11:34:14,485 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-ed6c8947) Completed resetting hosts suitable for reconnect
> 2015-04-25 11:34:14,485 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-ed6c8947) Acquiring hosts for clusters already owned by this
> management server
> 2015-04-25 11:34:14,485 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-ed6c8947) Completed acquiring hosts for clusters already owned by
> this management server
> 2015-04-25 11:34:14,485 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-ed6c8947) Acquiring hosts for clusters not owned by any
> management server
> 2015-04-25 11:34:14,486 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-ed6c8947) Completed acquiring hosts for clusters not owned by any
> management server
> 2015-04-25 11:34:28,390 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-194c8d9e) Skip capacity scan due to there is no Primary
> Storage UPintenance mode
> 2015-04-25 11:34:39,194 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-f8310767) Found 0 routers to update status.
> 2015-04-25 11:34:39,197 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-f8310767) Found 0 networks to update RvR status.
>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message