Ask Your Question
0

Ubuntu 12.04 nova-api fails to start and no error logging

asked 2012-05-11 11:20:28 -0500

david-butler gravatar image

Question 11/5/2012

Nova-api is not starting on Ubuntu 12.04 or logging errors?

I have been working my way through the Openstack Install and Deploy Manual ( http://docs.openstack.org/trunk/openstack-compute/install/content/ (http://docs.openstack.org/trunk/opens...) ) on a fresh install (10/05/2012) of Ubuntu 12.04, my 3rd or 4th attempt.

$ lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 12.04 LTS Release: 12.04 Codename: precise

$ uname -a Linux PoC5 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I have setup endpoint for the services as using the %(tenant-id) method, e.g.

$ keystone --token 012345SECRET99TOKEN012345 --endpoint http://192.168.206.130:35357/v2.0/ service-create --name=nova --type=compute --description="Nova Compute Service" +-------------+----------------------------------+ | Property | Value | +-------------+----------------------------------+ | description | Nova Compute Service | | id | e592904ff83147d18b823eecae62aaaa | | name | nova | | type | compute | +-------------+----------------------------------+

$ keystone --token 012345SECRET99TOKEN012345 --endpoint http://192.168.206.130:35357/v2.0/ endpoint-create --region RegionOne --service_id=e592904ff83147d18b823eecae62aaaa --publicurl='http://192.168.206.130:8774/v2/%(tenant_id)s' --internalurl='http://192.168.206.130:8774/v2/%(tenant_id)s' --adminurl='http://192.168.206.130:8774/v2/%(tenant_id)s' +-------------+---------------------------------------------+ | Property | Value | +-------------+---------------------------------------------+ | adminurl | http://192.168.206.130:8774/v2/%25(tenant_id)s (http://192.168.206.130:8774/v2/%(tena...) | | id | 7d7d93cde2de4849814f4042197bc2aa | | internalurl | http://192.168.206.130:8774/v2/%25(tenant_id)s (http://192.168.206.130:8774/v2/%(tena...) | | publicurl | http://192.168.206.130:8774/v2/%25(tenant_id)s (http://192.168.206.130:8774/v2/%(tena...) | | region | RegionOne | | service_id | e592904ff83147d18b823eecae62aaaa | +-------------+---------------------------------------------+

I can list the tenant id and endpoints for the service as follows:

$ keystone --token 012345SECRET99TOKEN012345 --endpoint http://192.168.206.130:35357/v2.0 tenant-list +----------------------------------+---------------+---------+ | id | name | enabled | +----------------------------------+---------------+---------+ | dd5a5ed306ff4ae2be0460e6968f80c5 | openstackDemo | True | | ee0c4334c48e491a8a14defbe66ab7fe | service | True | +----------------------------------+---------------+---------+

$ curl -d '{"auth": {"tenantName": "openstackDemo", "passwordCredentials":{"username": "adminUser", "password": "password"}}}' -H "Content-type: application/json" http://192.168.206.130:35357/v2.0/tokens | python -mjson.tool % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2289 0 2174 100 115 16150 854 --:--:-- --:--:-- --:--:-- 16223 { "access": { "serviceCatalog": [ { "endpoints": [ { "adminURL": "http://192.168.206.130:8774/v2/dd5a5ed306ff4ae2be0460e6968f80c5", "internalURL": "http://192.168.206.130:8774/v2/dd5a5ed306ff4ae2be0460e6968f80c5", "publicURL": "http://192.168.206.130:8774/v2/dd5a5ed306ff4ae2be0460e6968f80c5", "region": "RegionOne" } ], "endpoints_links": [], "name": "nova", "type": "compute" }, ......

curl -d '{"auth": {"tenantName": "service", "passwordCredentials":{"username": "nova", "password": "nova"}}}' -H "Content-type: application/json" http://192.168.206.130:35357/v2.0/tokens | python -mjson.tool % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2257 0 2158 100 99 7826 359 --:--:-- --:--:-- --:--:-- 7847 { "access": { "serviceCatalog": [ { "endpoints": [ { "adminURL": "http://192.168.206.130:8774/v2/ee0c4334c48e491a8a14defbe66ab7fe", "internalURL": "http://192.168.206.130:8774/v2/ee0c4334c48e491a8a14defbe66ab7fe", "publicURL": "http://192.168.206.130:8774/v2/ee0c4334c48e491a8a14defbe66ab7fe", "region": "RegionOne" } ], "endpoints_links": [], "name": "nova", "type": "compute" }, .....

For both the service and openstackDemo tenants, the teant ids matche the url endpoints.

Using the api-paste.ini from the manual ( http://docs.openstack.org/trunk/openstack-compute/install/content/api-paste-ini-file.html (http://docs.openstack.org/trunk/opens ... (more)

edit retag flag offensive close merge delete

7 answers

Sort by ยป oldest newest most voted
0

answered 2012-05-11 16:56:12 -0500

armando-migliaccio gravatar image

try to use use_syslog=True or run nova-api in foreground.

Check that your rabbitmq is correct, as the default one is 'guest'

HTH

edit flag offensive delete link more
0

answered 2012-05-16 14:25:04 -0500

Using upstart on Ubuntu ("service nova-api start") to run nova services, output is logged under /var/log/upstart/nova-____.log . Took me a bit to find that myself.

edit flag offensive delete link more
0

answered 2012-05-17 13:36:39 -0500

david-butler gravatar image

Cheers for the info.

My main problem was taht I followed the nova install procdure from the Openstack Install and Deploy Manual ( http://docs.openstack.org/trunk/openstack-compute/install/content/ (http://docs.openstack.org/trunk/opens...) ).

The nova install procdure for ubuntu uses some some different nova componets.

When I followed the OpenStack Compute Starter Guide ( http://docs.openstack.org/essex/openstack-compute/starter/content/ (http://docs.openstack.org/essex/opens...) ), the nova components start OK and nova-manage shows working nova components.

Note:

1)

edit flag offensive delete link more
0

answered 2012-05-17 13:39:11 -0500

david-butler gravatar image

Thanks Armando Migliaccio, that solved my question.

edit flag offensive delete link more
0

answered 2012-05-17 13:41:34 -0500

david-butler gravatar image

Note:

The nova setup in OpenStack Compute Starter Guide ( http://docs.openstack.org/essex/openstack-compute/starter/content/ (http://docs.openstack.org/essex/opens...) ) uses the original nova.conf format (--version etc) and different passwords for all the services.

edit flag offensive delete link more
0

answered 2012-05-17 16:45:29 -0500

armando-migliaccio gravatar image

Hi David,

I am glad you got it sorted. Maybe it's worth raising a bug against the docs, so that other people won't stumble on this again.

Cheers, Armando

edit flag offensive delete link more
0

answered 2012-06-06 19:12:47 -0500

lorinh gravatar image

As it turns out, The OpenStack Compute Starter Guide is not maintained by the docs team, it's maintained by CSS Corp. You can report bugs against the starter guide at https://bugs.launchpad.net/openstackbook

You can report bugs to the docs team at https://bugs.launchpad.net/openstack-manuals (https://bugs.launchpad.net/openstack-...)

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-05-11 11:20:28 -0500

Seen: 162 times

Last updated: Jun 06 '12