openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #16546
Re: After expanding fixed ip range instances no longer have network
Thanks Vish,
Your directions were correct & would have saved me a few hours of
floundering had I just started a little later :)
particularly the `killall dnsmasq`
-Jon
On Fri, Sep 07, 2012 at 09:12:52AM -0700, Vishvananda Ishaya wrote:
:If you are sure this is the issue:
:
:killall dnsmasq
:restart nova-network
:
:Vish
:
:On Sep 7, 2012, at 8:59 AM, Jonathan Proulx <jon@xxxxxxxxxxxxx> wrote:
:
:> On Fri, Sep 7, 2012 at 11:33 AM, Jonathan Proulx <jon@xxxxxxxxxxxxx> wrote:
:>
:>> Can any one tell me what I've looked?
:>
:> I assumed stopping and restarting nova-network would restart dnsmasq
:> since dnsmasq doesn't have it's own init script, but this seems not to
:> be the case.
:>
:> dnsmasq is listening on an IP the system nolonger has, I'm sure I'll
:> find the answer ot this on my own soon enough but how does one
:> properly restart openstack's dnsmasq (on ubuntu)? It clearly gets
:> started with lots of command line args from nova.conf....
:>
:> -Jon
:>
:> _______________________________________________
:> Mailing list: https://launchpad.net/~openstack
:> Post to : openstack@xxxxxxxxxxxxxxxxxxx
:> Unsubscribe : https://launchpad.net/~openstack
:> More help : https://help.launchpad.net/ListHelp
:
References