Ask Your Question

Ironic API: Address already in use?

asked 2017-09-06 10:53:06 -0500

zerorobben gravatar image

updated 2017-09-06 11:19:42 -0500


I'm just starting to install Ironic on my existing OpenStack (Ocata, Ubuntu 16) environment. I am presently (trying to integrate my compute and baremetal resources), but the Ironic API service is shutting down as soon as it starts. The compute service is still functional and my virtual machines are still running, so I believe this is relevant to the Ironic setup.

The same error message is repeated many thousands of times in /var/log/ironic/ironic-api.log:

ERROR oslo.service.wsgi [-] Could not bind to
CRITICAL ironic [-] error: [Errno 98] Address already in use
ERROR ironic Traceback (most recent call last):
ERROR ironic   File "/usr/bin/ironic-api", line 10, in <module>
ERROR ironic     sys.exit(main())
ERROR ironic   File "/usr/lib/python2.7/dist-packages/ironic/cmd/", line 42, in main
ERROR ironic     server = wsgi_service.WSGIService('ironic_api', CONF.api.enable_ssl_api)
ERROR ironic   File "/usr/lib/python2.7/dist-packages/ironic/common/", line 48, in __init__
ERROR ironic     use_ssl=use_ssl)
ERROR ironic   File "/usr/lib/python2.7/dist-packages/oslo_service/", line 115, in __init__
ERROR ironic     self.socket = self._get_socket(host, port, backlog)
ERROR ironic   File "/usr/lib/python2.7/dist-packages/oslo_service/", line 143, in _get_socket
ERROR ironic     sock = eventlet.listen(bind_addr, family, backlog=backlog)
ERROR ironic   File "/usr/lib/python2.7/dist-packages/eventlet/", line 44, in listen
ERROR ironic     sock.listen(backlog)
ERROR ironic   File "/usr/lib/python2.7/", line 228, in meth
ERROR ironic     return getattr(self._sock,name)(*args)
ERROR ironic error: [Errno 98] Address already in use

I don't see the port 6385 repeated multiple times in any of my configuration files, so I'm not sure what could be causing this issue. Perhaps it is the IP address? I'm not sure what the convention is. The only other mention of this (with the same port and message) is in a (2015 issue with Kolla) that is said to have been patched around that time (so I don't think it's related to my issue).

Perhaps it is related to the Apache server, as the openstack baremetal node create command returns "Forbidden (HTTP 403)." It is also visible multiple times with the lsof command:

# lsof -i | grep 6385
apache2    6699            root    8u  IPv6     65122      0t0  TCP *:6385 (LISTEN)
apache2   18825        www-data    8u  IPv6     65122      0t0  TCP *:6385 (LISTEN)
apache2   18835        www-data    8u  IPv6     65122      0t0  TCP *:6385 (LISTEN)

Ironic is the only OpenStack service configured to use this port:

cat /etc/apache2/sites-enabled/* | grep 6385
Listen 6385
<VirtualHost *:6385>

Has anyone encountered a similar error? Is there anything that can be checked? I must admit, I'm not familiar with Ironic, so some of my configurations might not be entirely correct.

I'd be happy to provide more information if it's needed. Please let me know if there's anything that ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2017-09-07 10:53:39 -0500

zerorobben gravatar image

I was able to resolve this. I disabled and stopped ironic-api, but Ironic had spawned a server listening on port 6385. This is a python process and is not killed when Ironic is. As a result, stopping Ironic, reconfiguring Apache, and restarting the apache2 service does not work because Apache attempts to listen on the (now blocked) port 6385 when it is first started and fails immediately.

This was as simple as running netstat -anop | grep 6385 and killing the rogue process with kill <pid> before restarting apache2.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-09-06 10:53:06 -0500

Seen: 972 times

Last updated: Sep 07 '17