← Back to team overview

openstack team mailing list archive

Re: Cannot start "nova-api" service

 

Hello,

Can someone please help me with a nova-api issue.  After install all the nova services, all seem to be running fine, except for nova-api.  I even reboot my controller node, no luck.  After reboot all services are running, except nova-api.  When I manually start nova-api, nova-api crashes with the following error "error: [Errno 98] Address already in use".  I installed nova-volume earlier during the install process, but later on installed cinder, and made the necessary modifications (as far as I can tell) to nova-api.conf to use cinder for block storage.  Should I uninstall nova-volume?

2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware
2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate
2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use
2012-11-12 14:46:24 TRACE nova Traceback (most recent call last):
2012-11-12 14:46:24 TRACE nova   File "/usr/bin/nova-api", line 50, in <module>
2012-11-12 14:46:24 TRACE nova     server = service.WSGIService(api)
2012-11-12 14:46:24 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/service.py", line 584, in __init__
2012-11-12 14:46:24 TRACE nova     port=self.port)
2012-11-12 14:46:24 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/wsgi.py", line 72, in __init__
2012-11-12 14:46:24 TRACE nova     self._socket = eventlet.listen((host, port), backlog=backlog)
2012-11-12 14:46:24 TRACE nova   File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in listen
2012-11-12 14:46:24 TRACE nova     sock.bind(addr)
2012-11-12 14:46:24 TRACE nova   File "/usr/lib/python2.7/socket.py", line 224, in meth
2012-11-12 14:46:24 TRACE nova     return getattr(self._sock,name)(*args)
2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use
2012-11-12 14:46:24 TRACE nova
2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting
2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting
2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server.
2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server.

Would highly appreciate any pointers to understanding or resolving the issue.

Regards,
Ahmed.


From: Ahmed Al-Mehdi <ahmed@xxxxxxxxxx<mailto:ahmed@xxxxxxxxxx>>
Date: Friday, November 9, 2012 12:45 AM
To: Vishvananda Ishaya <vishvananda@xxxxxxxxx<mailto:vishvananda@xxxxxxxxx>>
Cc: "openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>" <openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>>
Subject: Re: [Openstack] Cannot start "nova-api" service



From: Vishvananda Ishaya <vishvananda@xxxxxxxxx<mailto:vishvananda@xxxxxxxxx>>
Date: Thursday, November 8, 2012 8:18 PM
To: Ahmed Al-Mehdi <ahmed@xxxxxxxxxx<mailto:ahmed@xxxxxxxxxx>>
Cc: "openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>" <openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>>
Subject: Re: [Openstack] Cannot start "nova-api" service


On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi <ahmed@xxxxxxxxxx<mailto:ahmed@xxxxxxxxxx>> wrote:

Vish,

I am running cinder-api.   The following two lines are present in nova.conf.

volume_api_class=nova.volume.cinder.API
enabled_apis=ec2,osapi_compute,metadata

Do I need to re-sync the db, or add any additional lines to nova.conf?

No that is it. Are you sure a) you don't have another nova-api or nova-metadata or nova-api-os-compute process running? and b) that your nova.conf is being read properly?

Vish

As far as I can tell, no other nova-api, nova-metadata, nova-api-os-compute is running.   If there another way to confirm besides running "ps aux".  And how can I tell if nova.conf is being read properly?

root@bodega:~# ps aux | grep nova
nova       914  0.0  0.0  37952  1312 ?        Ss   16:01   0:00 su -s /bin/sh -c exec nova-novncproxy --config-file=/etc/nova/nova.conf nova
nova       916  0.0  0.2 122976 24108 ?        S    16:01   0:01 /usr/bin/python /usr/bin/nova-novncproxy --config-file=/etc/nova/nova.conf
nova      1235  0.0  0.0  37952  1312 ?        Ss   16:01   0:00 su -s /bin/sh -c exec nova-cert --config-file=/etc/nova/nova.conf nova
nova      1243  0.0  0.0  37952  1308 ?        Ss   16:01   0:00 su -s /bin/sh -c exec nova-consoleauth --config-file=/etc/nova/nova.conf nova
nova      1244  0.2  0.6 122996 51232 ?        S    16:01   1:12 /usr/bin/python /usr/bin/nova-cert --config-file=/etc/nova/nova.conf
nova      1249  0.2  0.6 122992 51252 ?        S    16:01   1:13 /usr/bin/python /usr/bin/nova-consoleauth --config-file=/etc/nova/nova.conf
nova      1252  0.0  0.0  37952  1312 ?        Ss   16:01   0:00 su -s /bin/sh -c exec nova-network --config-file=/etc/nova/nova.conf nova
nova      1255  0.0  0.0  37952  1308 ?        Ss   16:01   0:00 su -s /bin/sh -c exec nova-scheduler --config-file=/etc/nova/nova.conf nova
nova      1259  0.3  0.6 124964 53100 ?        S    16:01   1:16 /usr/bin/python /usr/bin/nova-network --config-file=/etc/nova/nova.conf
nova      1260  0.3  0.7 151856 59068 ?        S    16:01   1:16 /usr/bin/python /usr/bin/nova-scheduler --config-file=/etc/nova/nova.conf
root      3509  0.0  0.0   9388   920 pts/3    S+   22:55   0:00 grep --color=auto nova
root@bodega:~#
root@bodega:~#
root@bodega:~# ls -l /etc/nova/
total 32
-rw-r----- 1 nova nova 3588 Sep 25 17:48 api-paste.ini
-rw-r-xr-x 1 nova nova 1329 Oct 20 19:16 logging.conf
-rw-r----- 1 nova nova 2203 Nov  8 18:34 nova.conf
-rw-r----- 1 root root  434 Nov  5 10:44 nova.conf.orig.ahmed
-rw-r----- 1 nova nova 5181 Sep 25 17:48 policy.json
-rw-r--r-- 1 root root  304 Sep 25 17:48 rootwrap.conf
drwxr-xr-x 2 root root 4096 Nov  5 10:36 rootwrap.d
root@bodega:~#


Can you help me understand the following error message in the file:

2012-11-08 23:31:27 CRITICAL nova [-] [Errno 98] Address already in use

By address, are we talking about tcp port number? If so, what is the port number?

Thank you,
Ahmed.




Follow ups

References