You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "SuichII, Christopher" <Ch...@netapp.com> on 2014/01/14 23:03:14 UTC

Unable to start Virtual Router

I created a fresh, clean install earlier today and everything worked up until trying to deploy a VM. When the virtual router attempts to start, it quickly shuts down after spewing out:

‘[…] Stopping web server: apache2apache2: Could not reliably determine the server’s fully qualified domain name, using <ip address> for ServerName.

I’m setting up this environment the same way I have for months (as best as I can remember). Can anyone think of why the router would fail to start like this?

Thanks,
Chris
-- 
Chris Suich
chris.suich@netapp.com
NetApp Software Engineer
Data Center Platforms – Cloud Solutions
Citrix, Cisco & Red Hat

Re: Unable to start Virtual Router

Posted by Mike Tutkowski <mi...@solidfire.com>.
OK, interesting...I'm running on 4.3 at the moment with XenServer and it
works for me.


On Tue, Jan 14, 2014 at 3:15 PM, SuichII, Christopher <
Chris.Suich@netapp.com> wrote:

> Ah, no. I'm on 4.3.
> ________________________________________
> From: Mike Tutkowski [mike.tutkowski@solidfire.com]
> Sent: Tuesday, January 14, 2014 5:06 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Unable to start Virtual Router
>
> Are you using master, Chris?
>
> I've been having trouble with it...the agents' states of my VMs don't ever
> seem to get into the Up state.
>
> Maybe you're having similar trouble and it's impacting your virtual router?
>
>
> On Tue, Jan 14, 2014 at 3:03 PM, SuichII, Christopher <
> Chris.Suich@netapp.com> wrote:
>
> > I created a fresh, clean install earlier today and everything worked up
> > until trying to deploy a VM. When the virtual router attempts to start,
> it
> > quickly shuts down after spewing out:
> >
> > ‘[…] Stopping web server: apache2apache2: Could not reliably determine
> the
> > server’s fully qualified domain name, using <ip address> for ServerName.
> >
> > I’m setting up this environment the same way I have for months (as best
> as
> > I can remember). Can anyone think of why the router would fail to start
> > like this?
> >
> > Thanks,
> > Chris
> > --
> > Chris Suich
> > chris.suich@netapp.com
> > NetApp Software Engineer
> > Data Center Platforms – Cloud Solutions
> > Citrix, Cisco & Red Hat
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

RE: Unable to start Virtual Router

Posted by "SuichII, Christopher" <Ch...@netapp.com>.
Ah, no. I'm on 4.3.
________________________________________
From: Mike Tutkowski [mike.tutkowski@solidfire.com]
Sent: Tuesday, January 14, 2014 5:06 PM
To: dev@cloudstack.apache.org
Subject: Re: Unable to start Virtual Router

Are you using master, Chris?

I've been having trouble with it...the agents' states of my VMs don't ever
seem to get into the Up state.

Maybe you're having similar trouble and it's impacting your virtual router?


On Tue, Jan 14, 2014 at 3:03 PM, SuichII, Christopher <
Chris.Suich@netapp.com> wrote:

> I created a fresh, clean install earlier today and everything worked up
> until trying to deploy a VM. When the virtual router attempts to start, it
> quickly shuts down after spewing out:
>
> ‘[…] Stopping web server: apache2apache2: Could not reliably determine the
> server’s fully qualified domain name, using <ip address> for ServerName.
>
> I’m setting up this environment the same way I have for months (as best as
> I can remember). Can anyone think of why the router would fail to start
> like this?
>
> Thanks,
> Chris
> --
> Chris Suich
> chris.suich@netapp.com
> NetApp Software Engineer
> Data Center Platforms – Cloud Solutions
> Citrix, Cisco & Red Hat
>
>


--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

Re: Unable to start Virtual Router

Posted by Mike Tutkowski <mi...@solidfire.com>.
Are you using master, Chris?

I've been having trouble with it...the agents' states of my VMs don't ever
seem to get into the Up state.

Maybe you're having similar trouble and it's impacting your virtual router?


On Tue, Jan 14, 2014 at 3:03 PM, SuichII, Christopher <
Chris.Suich@netapp.com> wrote:

> I created a fresh, clean install earlier today and everything worked up
> until trying to deploy a VM. When the virtual router attempts to start, it
> quickly shuts down after spewing out:
>
> ‘[…] Stopping web server: apache2apache2: Could not reliably determine the
> server’s fully qualified domain name, using <ip address> for ServerName.
>
> I’m setting up this environment the same way I have for months (as best as
> I can remember). Can anyone think of why the router would fail to start
> like this?
>
> Thanks,
> Chris
> --
> Chris Suich
> chris.suich@netapp.com
> NetApp Software Engineer
> Data Center Platforms – Cloud Solutions
> Citrix, Cisco & Red Hat
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*