Blog
Search…
Hacking
OpenStack
Docker and DevOps
OpenStack nova API start error
Could not bind to 0.0.0.0 address all ready in use
OpenStack-nova-api doesn't start, this error is from the services boot priority in many times.
1
$ service openstack-nova-api start
2
3
2015-03-03 15:05:06.402 3313 ERROR nova.wsgi [-] Could not bind to 0.0.0.0:8775
4
2015-03-03 15:05:06.402 3313 CRITICAL nova [-] error: [Errno 98] Address already in use
5
6
$ service openstack-nova-api status
7
8
openstack-nova-api dead but pid file exists\*
Copied!
This Error happens because openstack-nova-api and openstack-nova-metadata-api use the same ports. You can start nova-api stopping metadata-api service and starting nova-api before, then start again metadata-api service.
1
$ service openstack-nova-metadata-api stop
2
$ service openstack-nova-api start
3
$ service openstack-nova-metadata-api
Copied!
This should fix your issue. After this you can set up boot order to this processes
1
update-rc.d openstack-nova-api defaults [order]
Copied!
Example:
If openstack-nova-metadata-api got an order boot of S90 openstack-nova-metadata-api, you should use update-rc to set nova-api start before nova-metadata-api
1
update-rc.d openstack-nova-api defaults 90
Copied!
This will set the priority of nova-api with the priority of nova-metadata-api, wich means that nova-api will run before metadata-api.
Last modified 1yr ago
Copy link