[Openstack-operators] [Nova] Question about starting nova as service versus directly
So I can start Nova on Ubuntu/Icehouse via *$ sudo python /usr/bin/nova-compute* and it runs fine and stays online but it does not run/stay online if I use *$ sudo service nova-compute start/restart*. I guessed it might have been related to rootwrap but I ran out of time to troubleshoot so I reverted the image to a previously-known good state. Does anyone have an idea why this happens and how to correct? I checked and /etc/nova/rootwrap.conf file looked correct and /etc/nova/nova.conf as well via the root_helper parameter. //adam *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly
Hi Adam, I've seen this happen due to permission issues. Regardless of running with sudo, upstart is dropping to the "nova" user. I usually debug this by setting a shell on the nova user, sudoing/su'ing to nova, then running nova-compute from there. It should die with an error message of the cause. Hope that helps, Joe On Nov 19, 2015 3:35 PM, "Adam Lawson" wrote: > So I can start Nova on Ubuntu/Icehouse via *$ sudo python > /usr/bin/nova-compute* and it runs fine and stays online but it does not > run/stay online if I use *$ sudo service nova-compute start/restart*. > > I guessed it might have been related to rootwrap but I ran out of time to > troubleshoot so I reverted the image to a previously-known good state. > > Does anyone have an idea why this happens and how to correct? I checked > and /etc/nova/rootwrap.conf file looked correct and /etc/nova/nova.conf as > well via the root_helper parameter. > > //adam > > *Adam Lawson* > > AQORN, Inc. > 427 North Tatnall Street > Ste. 58461 > Wilmington, Delaware 19801-2230 > Toll-free: (844) 4-AQORN-NOW ext. 101 > International: +1 302-387-4660 > Direct: +1 916-246-2072 > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly
On Thu, 19 Nov 2015 18:37:30 -0700 Joe Topjian wrote: > Hi Adam, > > I've seen this happen due to permission issues. Regardless of running > with sudo, upstart is dropping to the "nova" user. > > I usually debug this by setting a shell on the nova user, > sudoing/su'ing to nova, then running nova-compute from there. It > should die with an error message of the cause. Yes, most likely is related to permissions. Another good source of information for troubleshooting is /var/log/upstart/nova-compute.log -- Felipe Reyes (GPG:0x9B1FFF39) http://tty.cl lp:~freyes | freyes@freenode | freyes@github ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly
> Yes, most likely is related to permissions. Another good source of > information for troubleshooting is /var/log/upstart/nova-compute.log > Ah yes! Much easier. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly
Upstart is the startup system used by Ubuntu. It's been phased out "in favor" of systemd. ___ Kris Lindgren Senior Linux Systems Engineer GoDaddy From: Adam Lawson mailto:alaw...@aqorn.com>> Date: Friday, November 20, 2015 at 11:16 AM To: Joe Topjian mailto:j...@topjian.net>> Cc: "openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>" mailto:openstack-operators@lists.openstack.org>> Subject: Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly Thanks I will remember this! Unfortunately the image is long gone but very good info to keep handy. What exactly does upstart do by the way (as I check the log on a known working image)? //adam Adam Lawson AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 [http://www.aqorn.com/images/logo.png] On Fri, Nov 20, 2015 at 8:27 AM, Joe Topjian mailto:j...@topjian.net>> wrote: Yes, most likely is related to permissions. Another good source of information for troubleshooting is /var/log/upstart/nova-compute.log Ah yes! Much easier. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly
Thanks I will remember this! Unfortunately the image is long gone but very good info to keep handy. What exactly does upstart do by the way (as I check the log on a known working image)? //adam *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 On Fri, Nov 20, 2015 at 8:27 AM, Joe Topjian wrote: > > Yes, most likely is related to permissions. Another good source of >> information for troubleshooting is /var/log/upstart/nova-compute.log >> > > Ah yes! Much easier. > > > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators