Re: 回复：在kvm机器上启动cloudstack-agent失败，提示 Failed to get private nic name

Sat, 13 Jul 2013 21:27:04 -0700 

需要网桥确实没错，但不一定是2个，可以是1个。
从你ifconfig的信息来看，一个网桥也没建起来。
你需要先学着手动吧网桥建立完了。
再去手动在配置文件里指定网桥。

2013-07-14 
刘宇超  Richard Liu




发件人： WXR 
发送时间： 2013-07-13  16:05:45 
收件人： users-cn 
抄送： 
主题： 回复：在kvm机器上启动cloudstack-agent失败，提示 Failed to get private nic name 
 
cloudstack4.1的agent在启动时，默认要有cloudbr0和cloudbr1两个网桥。
如果想修改成其他名字可以在配置文件里面修改
/etc/cloudstack/agent/agent.properties
修改下面两个参数
private.network.device
public.network.devic
------------------ 原始邮件 ------------------
发件人: "helloqiner"<[email protected]>;
发送时间: 2013年7月12日(星期五) 中午1:30
收件人: "users-cn"<[email protected]>; 
主题: 在kvm机器上启动cloudstack-agent失败，提示 Failed to get private nic name
各位：
我在一台有两块网卡的服务器上安装了CentOS6.4 + kvm + cloudstack-agent,但装好后 cloudstack-agent 
一直无法启动，查看日志显示：
2013-07-12 12:51:45,350{GMT} INFO  [cloud.agent.AgentShell] (main:) Agent 
started
2013-07-12 12:51:45,351{GMT} INFO  [cloud.agent.AgentShell] (main:) 
Implementation Version is 4.1.0
2013-07-12 12:51:45,352{GMT} INFO  [cloud.agent.AgentShell] (main:) 
agent.properties found at /etc/cloudstack/agent/agent.properties
2013-07-12 12:51:45,354{GMT} INFO  [cloud.agent.AgentShell] (main:) Defaulting 
to using properties file for storage
2013-07-12 12:51:45,355{GMT} INFO  [cloud.agent.AgentShell] (main:) Defaulting 
to the constant time backoff algorithm
2013-07-12 12:51:45,422{GMT} INFO  [cloud.agent.Agent] (main:) id is 
2013-07-12 12:51:45,434{GMT} ERROR [cloud.resource.ServerResourceBase] (main:) 
Nics are not configured!
2013-07-12 12:51:45,440{GMT} INFO  [cloud.resource.ServerResourceBase] (main:) 
Designating private to be nic eth1
2013-07-12 12:51:45,449{GMT} INFO  
[resource.virtualnetwork.VirtualRoutingResource] (main:) VirtualRoutingResource 
_scriptDir to use: scripts/network/domr/kvm
2013-07-12 12:51:45,703{GMT} ERROR [cloud.agent.AgentShell] (main:) Unable to 
start agent: Failed to get private nic name
Unable to start agent: Failed to get private nic name
这个是哪里配置的不对吗？
附，网卡信息： 
eth0      Link encap:Ethernet  HWaddr 00:30:48:90:46:1E  
          inet addr:10.0.1.21  Bcast:10.0.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18 Memory:d8020000-d8040000 
eth1      Link encap:Ethernet  HWaddr 00:30:48:90:46:1F  
          inet addr:192.168.1.21  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1125 errors:0 dropped:0 overruns:0 frame:0
          TX packets:557 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:86671 (84.6 KiB)  TX bytes:32004 (31.2 KiB)
          Interrupt:19 Memory:d8060000-d8080000 
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
virbr0    Link encap:Ethernet  HWaddr 52:54:00:4A:45:34  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
helloqiner

回复