openstack team mailing list archive

[Dan Wendlandt <dan@xxxxxxxxxx>]

Hi Joe,

I'm sure there are more elaborate approaches, but I have a simple "kill.sh"
script that looks something like:

sudo killall dnsmasq
sudo killall qemu
sudo rm -f /etc/libvirt/qemu/instance-*.xml
sudo killall screen
screen -wipe

This is of course specific to my use of qemu.

After running kill.sh, I just rerun stack.sh

Dan


On Thu, Jan 26, 2012 at 11:30 AM, Joe Smithian <joe.smithian@xxxxxxxxx>wrote:

> localadmin@k:~$ sudo screen -x
> There is no screen to be attached.
>
> localadmin@k:~$ killall screen
> screen: no process found
>
> Should I re-run stack.sh?
>
>
>
>
>
> On Thu, Jan 26, 2012 at 2:24 PM, Dean Troyer <dtroyer@xxxxxxxxx> wrote:
> > On Thu, Jan 26, 2012 at 1:02 PM, Joe Smithian <joe.smithian@xxxxxxxxx>
> wrote:
> >> The devstack document doesn't explain how to start/stop services,
> >> maybe it's obvious for the devstack developers but not for a new user
> >> like me!  I can't use  commands like "restart nova-api" because they
> >> are not installed.
> >
> > Devstack starts the OpenStack services running in the foreground in a
> > screen session.  Type 'screen -x' to attach to the session, there will
> > be a window for each service plus one shell window.  Stop the each
> > service with a Ctrl-C.  Press up-arrow to see the command stack.sh
> > used to start it and execute that to restart the service.
> >
> >> I installed OpenStack using devsatck stack.sh script
> >> (http://devstack.org/) on Ubuntu 11.10. Installation was successful
> >> and I was able to login to Dahsboard; but it doesn't work anymore, I
> >> think after I changed the IP address of the machine and moved it to
> >> another network.
> >> Apache2 is running but the nova and keystone services are not running.
> >
> > If you had already stated an instance, Nova probably moved your IP
> > from eth0 to br100.  You would need to manually update the br100
> > configuration.  You might also need to update some other configuration
> > bits (floating IPs, etc) if you changed networks and want to access
> > the instances from off the host.
> >
> > Your best bet here may be to just bite the bullet and 'killall screen'
> > re-run stack.sh.  Of course this will re-initialize all of the
> > databases and kill running instances.
> >
> > dt
> >
> > --
> >
> > Dean Troyer
> > dtroyer@xxxxxxxxx
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira Networks: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~