Ask Your Question
1

How to solve "Address already in use" error on nova-api controller node

asked 2013-06-28 06:01:22 -0500

deependra singh chouhan gravatar image

updated 2013-07-03 09:00:31 -0500

smaffulli gravatar image

I get nova error: [Errno 98] Address already in use when running nova-api. What should I do?

$ nova-api --debug |& tee /var/log/nova/nova-api.log
2013-06-28 12:27:17.570 11030 DEBUG nova.wsgi [-] Loading app ec2 from /etc/nova/api-paste.ini load_app /usr/lib/python2.7/dist-packages/nova/wsgi.py:481
2013-06-28 12:27:17.634 11030 INFO nova.manager [-] Skipping periodic task _periodic_update_dns because its interval is negative
2013-06-28 12:27:17.697 11030 DEBUG nova.servicegroup.api [-] ServiceGroup driver defined as an instance of db __new__ /usr/lib/python2.7/dist-packages/nova/servicegroup/api.py:61
2013-06-28 12:27:17.707 11030 CRITICAL nova [-] [Errno 98] Address already in use
2013-06-28 12:27:17.707 11030 TRACE nova Traceback (most recent call last):
2013-06-28 12:27:17.707 11030 TRACE nova   File "/usr/bin/nova-api", line 59, in <module>
2013-06-28 12:27:17.707 11030 TRACE nova     max_url_len=16384)
2013-06-28 12:27:17.707 11030 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/service.py", line 608, in __init__
2013-06-28 12:27:17.707 11030 TRACE nova     max_url_len=max_url_len)
2013-06-28 12:27:17.707 11030 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/wsgi.py", line 120, in __init__
2013-06-28 12:27:17.707 11030 TRACE nova     self._socket = eventlet.listen(bind_addr, family, backlog=backlog)
2013-06-28 12:27:17.707 11030 TRACE nova   File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in listen
2013-06-28 12:27:17.707 11030 TRACE nova     sock.bind(addr)
2013-06-28 12:27:17.707 11030 TRACE nova   File "/usr/lib/python2.7/socket.py", line 224, in meth
2013-06-28 12:27:17.707 11030 TRACE nova     return getattr(self._sock,name)(*args)
2013-06-28 12:27:17.707 11030 TRACE nova error: [Errno 98] Address already in use
2013-06-28 12:27:17.707 11030 TRACE nova
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
2

answered 2013-06-28 06:08:13 -0500

Jobin gravatar image

updated 2013-06-28 06:17:50 -0500

You can safely ignore this error, if doing a ps aux | grep nova-api tells that nova-api is running. If not, this is probably because someone else is already using the port(8777, by default) and nova-api is not able to grab it. To make nova-api run, kill the other process(if not needed using kill <pid>), ensure that the port is listening(using netstat -ntlp | grep <port_no>) and then doing a sudo service nova-api start.

edit flag offensive delete link more
0

answered 2015-08-12 12:58:40 -0500

tiagocruz gravatar image

The services "openstack-nova-metadata-api" and "openstack-nova-api" uses the same port.

So, to start "openstack-nova-api" you need to stop "openstack-nova-metadata-api". To prevent this fail after the reboot:

# chkconfig openstack-nova-metadata-api off
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

Stats

Asked: 2013-06-28 06:01:22 -0500

Seen: 6,510 times

Last updated: Aug 12 '15