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-f
vember 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
> 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.o
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 no
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 caus
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 rever
