Ask Your Question
0

openstack-nova-api is dead & not able to access dashboard after reboot

asked 2013-10-17 02:57:54 -0500

sngirame gravatar image

After controller node reboot openstack-nova-api is dead & that probably causing dashboard inaccessible.

Here is an error

CRITICAL nova [-] [Errno 98] Address already in use 2013-10-16 20:33:57.845 3526 TRACE nova Traceback (most recent call last): 2013-10-16 20:33:57.845 3526 TRACE nova File "/usr/bin/nova-api", line 61, in <module> 2013-10-16 20:33:57.845 3526 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl) 2013-10-16 20:33:57.845 3526 TRACE nova File "/usr/lib/python2.6/site-packages/nova/service.py", line 608, in __init__ 2013-10-16 20:33:57.845 3526 TRACE nova max_url_len=max_url_len) 2013-10-16 20:33:57.845 3526 TRACE nova File "/usr/lib/python2.6/site-packages/nova/wsgi.py", line 120, in __init__ 2013-10-16 20:33:57.845 3526 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog) 2013-10-16 20:33:57.845 3526 TRACE nova File "/usr/lib/python2.6/site-packages/eventlet/convenience.py", line 38, in listen 2013-10-16 20:33:57.845 3526 TRACE nova sock.bind(addr) 2013-10-16 20:33:57.845 3526 TRACE nova File "<string> ", line 1, in bind 2013-10-16 20:33:57.845 3526 TRACE nova error: [Errno 98] Address already in use 2013-10-16 20:33:57.845 3526 TRACE nova 2013-10-16 20:33:57.855 3604 INFO nova.osapi_compute.wsgi.server [-] (3604) wsgi starting up on http://0.0.0.0:8774/</string></module>

2013-10-16 20:33:58.025 3604 INFO nova.service [-] Parent process has died unexpectedly, exiting 2013-10-16 20:33:58.025 3559 INFO nova.service [-] Parent process has died unexpectedly, exiting 2013-10-16 20:33:58.025 3559 INFO nova.wsgi [-] Stopping WSGI server. 2013-10-16 20:33:58.025 3604 INFO nova.wsgi [-] Stopping WSGI server.

Verified that there is nothing listening on 8774 according to netstat.

Here is an output of openstack-status == Nova services == openstack-nova-api: dead openstack-nova-cert: active openstack-nova-compute: active openstack-nova-network: active openstack-nova-scheduler: active openstack-nova-volume: dead (disabled on boot) openstack-nova-conductor: active == Glance services == openstack-glance-api: active openstack-glance-registry: active == Keystone service == openstack-keystone: active == Horizon service == openstack-dashboard: active == Cinder services == openstack-cinder-api: active openstack-cinder-scheduler: active openstack-cinder-volume: active == Support services == mysqld: active libvirtd: active messagebus: active tgtd: active qpidd: active memcached: active == Keystone users == +----------------------------------+--------+---------+---------------+ | id | name | enabled | email | +----------------------------------+--------+---------+---------------+ | 048abc1d9c934ee793b0e3ec02be1b8a | admin | True | | | a97421c3f3b149d8ad64a5cbf7f3d9ec | cinder | True | cinder@op.com | | 4d85f18b6e2a423bb3b70dca61b68d72 | ec2 | True | | | e761087e32884f52b71d5a259692084f | glance | True | | | 094638859f864120b91c113121f28eb9 | nova | True | | | 8239ac75d91f4885ba6796b3deac3664 | swift | True | | +----------------------------------+--------+---------+---------------+ == Glance images == +--------------------------------------+--------------+-------------+------------------+-----------+--------+ | ID | Name | Disk Format | Container Format | Size | Status | +--------------------------------------+--------------+-------------+------------------+-----------+--------+ | 814e4450-5b73-4595-822b-f41519af6b97 | CirrOS 0.3.1 | qcow2 | bare | 13147648 | active | | 2600ffa8-648d-4d5d-9147-089721baa4c8 | Fedora_19 | qcow2 | bare | 237371392 | active | +--------------------------------------+--------------+-------------+------------------+-----------+--------+ == Nova instance flavors == ERROR: [Errno 111] Connection refused == Nova instances == ERROR: [Errno 111] Connection refused

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2013-10-17 08:24:05 -0500

sngirame gravatar image

I was able to resolve the issue by adding following line in nova.conf [DEFAULT] & restarting nova services.

enabled_apis=ec2,osapi_compute

edit flag offensive delete link more

Comments

I have done this but its still not working. Please give another answer

smcas gravatar imagesmcas ( 2015-08-06 01:18:38 -0500 )edit
0

answered 2018-05-16 13:45:34 -0500

woltjert gravatar image

Did you ever figure this out? having the same problem.

edit flag offensive delete link more

Comments

A lot of things have changed since 2013, in our Ocata and Pike enabled_apis is set to:

enabled_apis = osapi_compute,metadata

There seems to be another service listening on that port, try to figure out who that is. OS API uses port 8774, nova metadata use port 8775.

eblock gravatar imageeblock ( 2018-05-17 03:17:30 -0500 )edit

Additionally, I have configured this in the nova.conf on controller node:

osapi_compute_listen = $my_ip
metadata_listen = $my_ip

to prevent that nova uses all interfaces, but this is just a tip. Try lsof -i -P | grep 8774 or netstat -le | grep 8774 to find who wants to use that port.

eblock gravatar imageeblock ( 2018-05-17 03:23:08 -0500 )edit

netstat -le | grep 8774 returns nothing, even though the nova-api service is running. openstack server list returns an error, because nova-api is not listening on 8774, despite the service running and the setting osapi_compute_listen_port = 8774

woltjert gravatar imagewoltjert ( 2018-05-17 08:07:47 -0500 )edit

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: 2013-10-17 02:57:54 -0500

Seen: 394 times

Last updated: May 16