cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Practical XenServer <practicalxenser...@gmail.com>
Subject Re: Unable to start agent: Failed to get private nic name
Date Wed, 03 Jun 2020 22:43:54 GMT
FYI: There are three different interfaces configured/enabled/functioning on
this host:

1 active-passive bonded interface [172.16.0.1/24] consisting of two slaves
(p1p3 & p1p4).
2 physical interfaces (p1p1 [172.16.1.3/25] & p1p2 [172.16.1.131/25]).

During the /usr/bin/cloudstack-setup process, *when prompted "Please choose
which network used to create VM:[bond0]*, it doesn't seem to make any
difference what answer I provide - bond0, p1p1, 172.16.1.3, p1p2, or
172.16.1.131. The CloudStack agent fails to start.

Ideas? Suggestions?

TIA,
Eric P.

On Wed, Jun 3, 2020 at 2:40 PM Practical XenServer <
practicalxenserver@gmail.com> wrote:

> Thanks, Fariborz.
>
> But you're pointing me to the same page that I referenced in my original
> message i.e.,
>
> /en/latest/installguide/hypervisor/kvm.html = /en/4.6/hypervisor/kvm.html
>
> Do you have any *new* information to share?
>
> TIA,
> Eric P.
>
> On Wed, Jun 3, 2020 at 2:27 PM Fariborz Navidan <mdvlinquest@gmail.com>
> wrote:
>
>> Hello,
>>
>> This happens when bridges are not configured on the host and there is no
>> private ip assigned to your nic. Please check your bridge config as
>> mentions in installation documentation here:
>>
>> http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.6/hypervisor/kvm.html
>>
>> On Thu, Jun 4, 2020 at 1:51 AM Practical XenServer <
>> practicalxenserver@gmail.com> wrote:
>>
>> > Hello!
>> >
>> > I've been following the installation instructions for installing the
>> > CloudStack agent on a CentOS-7 KVM host
>> > <
>> >
>> http://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html#install-and-configure-the-agent
>> > >:
>> > But I can't get the cloudstack-agent to start. e.g., From the end of
>> > /var/log/cloudstack/agent/agent.log:
>> >
>> > > Jun  3 17:06:48 vmh-1 systemd: cloudstack-agent.service: main process
>> > exited, code=exited, status=66/n/a
>> > > Jun  3 17:06:48 vmh-1 systemd: Unit cloudstack-agent.service entered
>> > failed state.
>> > > Jun  3 17:06:48 vmh-1 systemd: cloudstack-agent.service failed.
>> >
>> > I've collected all of the evidence that seems relevant
>> > <https://pastebin.com/eRvTEQX0> (e.g., interface configuration &
>> status;
>> > the configuration & status of libvirtd; etc) and put it in Pastebin.
>> >
>> > Would somebody please help me fix my installation of cloudstack-agent?
>> >
>> > TIA,
>> > Eric Pretorious
>> > Portland, Oregon
>> >
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message