[Openstack] Cannot start nova-api service
Hi, I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node. Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? Any help is appreciated. From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server.* *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server.* I also post my nova-api.log file and nova.conf file at pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.com wrote: Hi, I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node. Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? Any help is appreciated. From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server.* *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server.* I also post my nova-api.log file and nova.conf file at pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
Mind sharing your nova.conf with us. You have a misconfiguration of which api's should be exposed which is causing 2 to use the same port. -Philip From: Openstack [mailto:openstack-bounces+philip.schwartz=lexisnexis@lists.launchpad.net] On Behalf Of Aaron Rosen Sent: Wednesday, May 15, 2013 1:33 PM To: Sam Su Cc: openstack Subject: Re: [Openstack] Cannot start nova-api service Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.commailto:susltd...@gmail.com wrote: Hi, I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node. Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? Any help is appreciated. From /etc/log/nova/nova-api.log 2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net' 2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/ 2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address 2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last): 2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module 2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl) 2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__ 2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len) 2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__ 2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog) 2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr) 2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args) 2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address 2013-05-15 09:53:53.928 7233 TRACE nova 2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting 2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting 2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server. 2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server. I also post my nova-api.log file and nova.conf file at pastebin.comhttp://pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
Thank you for your response. I just checked the port 8774, it is available. *root@cctrl-01:/var/log/nova# lsof -i :8774* *root@cctrl-01:/var/log/nova# netstat -anp | grep 8774* *root@cctrl-01:/var/log/nova# service nova-api status* *nova-api stop/waiting* *root@cctrl-01:/var/log/nova# * If need check more things, please let me know. Thanks, Sam On Wed, May 15, 2013 at 10:32 AM, Aaron Rosen aro...@nicira.com wrote: Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.com wrote: Hi, I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node. Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? Any help is appreciated. From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__ * *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server.* *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server.* I also post my nova-api.log file and nova.conf file at pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
Sure, here are my nova-api.log file and nova.conf file: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam On Wed, May 15, 2013 at 10:39 AM, Schwartz, Philip Marc (RIS-BCT) philip.schwa...@lexisnexis.com wrote: Mind sharing your nova.conf with us. You have a misconfiguration of which api’s should be exposed which is causing 2 to use the same port. ** ** **-**Philip ** ** *From:* Openstack [mailto:openstack-bounces+philip.schwartz= lexisnexis@lists.launchpad.net] *On Behalf Of *Aaron Rosen *Sent:* Wednesday, May 15, 2013 1:33 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] Cannot start nova-api service ** ** Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api ** ** On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.com wrote: Hi, ** ** I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node.** ** Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql ** ** All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? ** ** Any help is appreciated. ** ** ** ** From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__* *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__ * *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server. * *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server. * ** ** I also post my nova-api.log file and nova.conf file at pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga ** ** Thanks, Sam ** ** ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ** ** ___ Mailing list: https://launchpad.net/~openstack Post
Re: [Openstack] Cannot start nova-api service
Weird looks fine to me. What happens if you do: sudo service nova-api stop; and then run nova-api in the foreground. $ nova-api Aaron On Wed, May 15, 2013 at 10:58 AM, Sam Su susltd...@gmail.com wrote: Sure, here are my nova-api.log file and nova.conf file: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam On Wed, May 15, 2013 at 10:39 AM, Schwartz, Philip Marc (RIS-BCT) philip.schwa...@lexisnexis.com wrote: Mind sharing your nova.conf with us. You have a misconfiguration of which api’s should be exposed which is causing 2 to use the same port.*** * ** ** **-**Philip ** ** *From:* Openstack [mailto:openstack-bounces+philip.schwartz= lexisnexis@lists.launchpad.net] *On Behalf Of *Aaron Rosen *Sent:* Wednesday, May 15, 2013 1:33 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] Cannot start nova-api service ** ** Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api ** ** On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.com wrote: Hi, ** ** I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node.* *** Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql ** ** All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? ** ** Any help is appreciated. ** ** ** ** From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__ * *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len) * *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__*** ** *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server.*** ** *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server.*** ** ** ** I also post my nova-api.log file and nova.conf file at pastebin.com, here are the links: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga ** ** Thanks, Sam ** ** ___ Mailing list: https://launchpad.net/~openstack Post to : openstack
Re: [Openstack] Cannot start nova-api service
Nova-api service can start now. I replace the line enabled_apis=ec2,osapi_compute,metadata with enabled_apis=ec2,osapi_compute at the file nova.conf, the service nova-api can be started. Thanks for all you guys help. Sam On Wed, May 15, 2013 at 1:19 PM, Aaron Rosen aro...@nicira.com wrote: Weird looks fine to me. What happens if you do: sudo service nova-api stop; and then run nova-api in the foreground. $ nova-api Aaron On Wed, May 15, 2013 at 10:58 AM, Sam Su susltd...@gmail.com wrote: Sure, here are my nova-api.log file and nova.conf file: nova-api.loghttp://pastebin.com/24a7ucy1 nova.conf http://pastebin.com/wnZAr0Ga Thanks, Sam On Wed, May 15, 2013 at 10:39 AM, Schwartz, Philip Marc (RIS-BCT) philip.schwa...@lexisnexis.com wrote: Mind sharing your nova.conf with us. You have a misconfiguration of which api’s should be exposed which is causing 2 to use the same port.** ** ** ** **-**Philip ** ** *From:* Openstack [mailto:openstack-bounces+philip.schwartz= lexisnexis@lists.launchpad.net] *On Behalf Of *Aaron Rosen *Sent:* Wednesday, May 15, 2013 1:33 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] Cannot start nova-api service ** ** Looks like something is already binding on 8774 (probably nova-api :) ) What does lsof -i :8774 say? Then see what process is running. For example: arosen@arosen-desktop:~$ lsof -i :8774 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 13936 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13945 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) python 13946 arosen6u IPv4 32808940 0t0 TCP *:8774 (LISTEN) arosen@arosen-desktop:~$ ps -eaf | grep 13936 arosen4822 14986 0 10:27 pts/62 00:00:00 grep --color=auto 13936 arosen 13936 13797 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13944 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13945 13936 0 May14 pts/68 00:00:00 python bin/nova-api arosen 13946 13936 0 May14 pts/68 00:00:00 python bin/nova-api ** ** On Wed, May 15, 2013 at 10:24 AM, Sam Su susltd...@gmail.com wrote:*** * Hi, ** ** I installed an Openstack Grizzly cluster based on Ubuntu 12.04, there are 1 control node, 1 database node, 1 quantum network node and 1 compute node, I list all installed services at the control node and the database node. Control node: nova-api, nova-scheduler, nova-consoleauth, nova-novncproxy, nova-conductor, rabbitmq, quantum-server, keystone, horizon, glance Database node: mysql ** ** All of the nova services are running, however, nova-api is not running. When I manually start nova-api service, I will get an error as below. Can someone give me some advises? ** ** Any help is appreciated. ** ** ** ** From /etc/log/nova/nova-api.log *2013-05-15 09:53:53.920 7233 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'* *2013-05-15 09:53:53.922 7239 INFO nova.osapi_compute.wsgi.server [-] (7239) wsgi starting up on http://0.0.0.0:8774/* *2013-05-15 09:53:53.928 7233 CRITICAL nova [-] [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova Traceback (most recent call last):* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/bin/nova-api, line 61, in module* *2013-05-15 09:53:53.928 7233 TRACE nova server = service.WSGIService(api, use_ssl=should_use_ssl)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 608, in __init__ * *2013-05-15 09:53:53.928 7233 TRACE nova max_url_len=max_url_len)*** ** *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 120, in __init__** *** *2013-05-15 09:53:53.928 7233 TRACE nova self._socket = eventlet.listen(bind_addr, family, backlog=backlog)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen* *2013-05-15 09:53:53.928 7233 TRACE nova sock.bind(addr)* *2013-05-15 09:53:53.928 7233 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth* *2013-05-15 09:53:53.928 7233 TRACE nova return getattr(self._sock,name)(*args)* *2013-05-15 09:53:53.928 7233 TRACE nova error: [Errno 99] Cannot assign requested address* *2013-05-15 09:53:53.928 7233 TRACE nova * *2013-05-15 09:53:54.023 7239 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.023 7238 INFO nova.service [-] Parent process has died unexpectedly, exiting* *2013-05-15 09:53:54.024 7238 INFO nova.wsgi [-] Stopping WSGI server.** *** *2013-05-15 09:53:54.024 7239 INFO nova.wsgi [-] Stopping WSGI server.** *** ** ** I also post my nova-api.log file and nova.conf file at pastebin.com
Re: [Openstack] 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 ah...@coraid.commailto:ah...@coraid.com Date: Friday, November 9, 2012 12:45 AM To: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service From: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Date: Thursday, November 8, 2012 8:18 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com 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 ?S16: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 ?S16:01 1:12 /usr/bin/python /usr/bin/nova-cert --config-file=/etc/nova/nova.conf nova 1249 0.2 0.6 122992 51252 ?S16: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 ?S16:01
Re: [Openstack] Cannot start nova-api service
By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- Ahmed Al-Mehdi ah...@coraid.com To Sent by: Vishvananda Ishaya openstack-bounces vishvana...@gmail.com, +gengjh=cn.ibm.co cc m@lists.launchpad openstack@lists.launchpad.net .net openstack@lists.launchpad.net Subject Re: [Openstack] Cannot start 11/13/2012 09:32 nova-api service AM 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 ah...@coraid.com Date: Friday, November 9, 2012 12:45 AM To: Vishvananda Ishaya vishvana...@gmail.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service From: Vishvananda Ishaya vishvana...@gmail.com Date: Thursday, November 8, 2012 8:18 PM To: Ahmed Al-Mehdi ah...@coraid.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.com 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
Re: [Openstack] Cannot start nova-api service
On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng gen...@cn.ibm.com wrote: By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- [image: Inactive hide details for Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.com]Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.com *Ahmed Al-Mehdi ah...@coraid.com* Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.net 11/13/2012 09:32 AM To Vishvananda Ishaya vishvana...@gmail.com, cc openstack@lists.launchpad.net openstack@lists.launchpad.net Subject Re: [Openstack] 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 *ah...@coraid.com* ah...@coraid.com* Date: *Friday, November 9, 2012 12:45 AM* To: *Vishvananda Ishaya *vishvana...@gmail.com* vishvana...@gmail.com* Cc: **openstack@lists.launchpad.net* openstack@lists.launchpad.net * openstack@lists.launchpad.net* openstack@lists.launchpad.net* Subject: *Re: [Openstack] Cannot start nova-api service *From: *Vishvananda Ishaya *vishvana...@gmail.com*vishvana...@gmail.com * Date: *Thursday, November 8, 2012 8:18 PM* To: *Ahmed Al-Mehdi *ah...@coraid.com* ah...@coraid.com* Cc: **openstack@lists.launchpad.net* openstack@lists.launchpad.net *openstack@lists.launchpad.net* openstack@lists.launchpad.net* Subject: *Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi *ah...@coraid.com*ah...@coraid.com 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
Re: [Openstack] Cannot start nova-api service
From: John Griffith john.griff...@solidfire.commailto:john.griff...@solidfire.com Date: Monday, November 12, 2012 7:17 PM To: Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com Cc: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com, openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com wrote: By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- [cid:1__=c7bbf026df9980448f9e8a93df...@cn.ibm.com]Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:cn.ibm@lists.launchpad.net 11/13/2012 09:32 AM To Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com, cc openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject Re: [Openstack] 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 ah...@coraid.commailto:ah...@coraid.com Date: Friday, November 9, 2012 12:45 AM To: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service From: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Date: Thursday, November 8, 2012 8:18 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Vish, I am running cinder-api. The following two lines
Re: [Openstack] Cannot start nova-api service
On Mon, Nov 12, 2012 at 7:34 PM, Ahmed Al-Mehdi ah...@coraid.com wrote: From: John Griffith john.griff...@solidfire.com Date: Monday, November 12, 2012 7:17 PM To: Jian Hua Geng gen...@cn.ibm.com Cc: Ahmed Al-Mehdi ah...@coraid.com, openstack-bounces+gengjh=cn.ibm@lists.launchpad.net openstack-bounces+gengjh=cn.ibm@lists.launchpad.net, openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng gen...@cn.ibm.com wrote: By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- [image: Inactive hide details for Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.com]Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.com *Ahmed Al-Mehdi ah...@coraid.com* Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.net 11/13/2012 09:32 AM To Vishvananda Ishaya vishvana...@gmail.com, cc openstack@lists.launchpad.net openstack@lists.launchpad.net Subject Re: [Openstack] 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 *ah...@coraid.com* ah...@coraid.com* Date: *Friday, November 9, 2012 12:45 AM* To: *Vishvananda Ishaya *vishvana...@gmail.com* vishvana...@gmail.com * Cc: **openstack@lists.launchpad.net* openstack@lists.launchpad.net * openstack@lists.launchpad.net* openstack@lists.launchpad.net* Subject: *Re: [Openstack] Cannot start nova-api service *From: *Vishvananda Ishaya *vishvana...@gmail.com*vishvana...@gmail.com * Date: *Thursday, November 8, 2012 8:18 PM* To: *Ahmed Al-Mehdi *ah...@coraid.com* ah...@coraid.com* Cc: **openstack@lists.launchpad.net* openstack@lists.launchpad.net *openstack@lists.launchpad.net* openstack@lists.launchpad.net* Subject: *Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi *ah...@coraid.com*ah...@coraid.com 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
Re: [Openstack] Cannot start nova-api service
From: John Griffith john.griff...@solidfire.commailto:john.griff...@solidfire.com Date: Monday, November 12, 2012 7:47 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com, openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Mon, Nov 12, 2012 at 7:34 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: From: John Griffith john.griff...@solidfire.commailto:john.griff...@solidfire.com Date: Monday, November 12, 2012 7:17 PM To: Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com Cc: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com, openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com wrote: By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- [cid:1__=c7bbf026df9980448f9e8a93df...@cn.ibm.com]Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:cn.ibm@lists.launchpad.net 11/13/2012 09:32 AM To Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com, cc openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject Re: [Openstack] 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 ah...@coraid.commailto:ah...@coraid.com Date: Friday, November 9, 2012 12:45 AM
[Openstack] Cannot start nova-api service
Hello, I installed the nova-* services per the instruction at http://docs.openstack.org/trunk/openstack-compute/install/apt/content/installing-the-cloud-controller.html All of the nova services are running, however, nova-api is not running. When I manually start nova-api, I am getting an error. Can some one please help me understand why. I need nova-api to work before I move forward with my setup, as per my understanding. From /var/log/nova/nova-api.log: …… (Lost of messages from nova.api.openstack.extenstions) 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extended resource: extensions from (pid=2348) _setup_ext_routes /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:135 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extended resource: extra_specs from (pid=2348) _setup_ext_routes /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:135 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension AdminActions extending resource: volumes from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension AdminActions extending resource: snapshots from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension TypesManage extending resource: types from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension VolumeActions extending resource: volumes from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-08 16:05:08 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-08 16:05:08 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-08 16:05:08 TRACE nova Traceback (most recent call last): 2012-11-08 16:05:08 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-08 16:05:08 TRACE nova server = service.WSGIService(api) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-08 16:05:08 TRACE nova port=self.port) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-08 16:05:08 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-08 16:05:08 TRACE nova sock.bind(addr) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-08 16:05:08 TRACE nova return getattr(self._sock,name)(*args) 2012-11-08 16:05:08 TRACE nova error: [Errno 98] Address already in use 2012-11-08 16:05:08 TRACE nova 2012-11-08 16:05:08 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-08 16:05:08 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-08 16:05:08 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-08 16:05:08 INFO nova.wsgi [-] Stopping WSGI server. Thank you, Ahmed. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
Are you running cinder-api? If so you have to disable the nova-volume api: http://wiki.openstack.org/MigrateToCinder Vish On Nov 8, 2012, at 4:12 PM, Ahmed Al-Mehdi ah...@coraid.com wrote: Hello, I installed the nova-* services per the instruction at http://docs.openstack.org/trunk/openstack-compute/install/apt/content/installing-the-cloud-controller.html All of the nova services are running, however, nova-api is not running. When I manually start nova-api, I am getting an error. Can some one please help me understand why. I need nova-api to work before I move forward with my setup, as per my understanding. From /var/log/nova/nova-api.log: …… (Lost of messages from nova.api.openstack.extenstions) 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extended resource: extensions from (pid=2348) _setup_ext_routes /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:135 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extended resource: extra_specs from (pid=2348) _setup_ext_routes /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:135 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension AdminActions extending resource: volumes from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension AdminActions extending resource: snapshots from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension TypesManage extending resource: types from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension VolumeActions extending resource: volumes from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-08 16:05:08 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-08 16:05:08 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-08 16:05:08 TRACE nova Traceback (most recent call last): 2012-11-08 16:05:08 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-08 16:05:08 TRACE nova server = service.WSGIService(api) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-08 16:05:08 TRACE nova port=self.port) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-08 16:05:08 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-08 16:05:08 TRACE nova sock.bind(addr) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-08 16:05:08 TRACE nova return getattr(self._sock,name)(*args) 2012-11-08 16:05:08 TRACE nova error: [Errno 98] Address already in use 2012-11-08 16:05:08 TRACE nova 2012-11-08 16:05:08 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-08 16:05:08 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-08 16:05:08 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-08 16:05:08 INFO nova.wsgi [-] Stopping WSGI server. Thank you, Ahmed. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
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? Thank you, Ahmed. From: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Date: Thursday, November 8, 2012 6:34 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service Are you running cinder-api? If so you have to disable the nova-volume api: http://wiki.openstack.org/MigrateToCinder Vish On Nov 8, 2012, at 4:12 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hello, I installed the nova-* services per the instruction at http://docs.openstack.org/trunk/openstack-compute/install/apt/content/installing-the-cloud-controller.html All of the nova services are running, however, nova-api is not running. When I manually start nova-api, I am getting an error. Can some one please help me understand why. I need nova-api to work before I move forward with my setup, as per my understanding. From /var/log/nova/nova-api.log: …… (Lost of messages from nova.api.openstack.extenstions) 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extended resource: extensions from (pid=2348) _setup_ext_routes /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:135 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extended resource: extra_specs from (pid=2348) _setup_ext_routes /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:135 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension AdminActions extending resource: volumes from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension AdminActions extending resource: snapshots from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension TypesManage extending resource: types from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 DEBUG nova.api.openstack [-] Extension VolumeActions extending resource: volumes from (pid=2348) _setup_extensions /usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py:171 2012-11-08 16:05:08 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-08 16:05:08 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-08 16:05:08 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-08 16:05:08 TRACE nova Traceback (most recent call last): 2012-11-08 16:05:08 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-08 16:05:08 TRACE nova server = service.WSGIService(api) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-08 16:05:08 TRACE nova port=self.port) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-08 16:05:08 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-08 16:05:08 TRACE nova sock.bind(addr) 2012-11-08 16:05:08 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-08 16:05:08 TRACE nova return getattr(self._sock,name)(*args) 2012-11-08 16:05:08 TRACE nova error: [Errno 98] Address already in use 2012-11-08 16:05:08 TRACE nova 2012-11-08 16:05:08 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-08 16:05:08 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-08 16:05:08 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-08 16:05:08 INFO nova.wsgi [-] Stopping WSGI server. Thank you, Ahmed. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.com 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
From: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Date: Thursday, November 8, 2012 8:18 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com 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 ?S16: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 ?S16:01 1:12 /usr/bin/python /usr/bin/nova-cert --config-file=/etc/nova/nova.conf nova 1249 0.2 0.6 122992 51252 ?S16: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 ?S16:01 1:16 /usr/bin/python /usr/bin/nova-network --config-file=/etc/nova/nova.conf nova 1260 0.3 0.7 151856 59068 ?S16: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/3S+ 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. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot start nova-api service
From: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Date: Thursday, November 8, 2012 8:18 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com 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 By any chance, could the issue be related to the duplicate entries for nova-volume and cinder in keystone: root@bodega:~# keystone endpoint-list +--+---+-+-++ |id| region |publicurl | internalurl | adminurl | +--+---+-+-++ | 1753b8533e474cf0934cd2eb1d23be45 | RegionOne | http://10.176.20.158:/v1/AUTH_%(tenant_id)s | http://10.176.20.158:/v1/AUTH_%(tenant_id)s | http://10.176.20.158:/v1| | 35c19563fce34c04a20cc82952b096b5 | RegionOne | http://10.176.20.158:8773/services/Cloud| http://10.176.20.158:8773/services/Cloud| http://10.176.20.158:8773/services/Admin | | 36f5a5c3021a485db6b900aee9d7520c | RegionOne | http://10.176.20.158:9292/v1 | http://10.176.20.158:9292/v1 |http://10.176.20.158:9292/v1| | 7fdf2e50d29a454897f3c5d395a8326f | RegionOne | http://10.176.20.158:8774/v2/%(tenant_id)s | http://10.176.20.158:8774/v2/%(tenant_id)s | http://10.176.20.158:8774/v2/%(tenant_id)s | | 9b1ade95c694401cb61362daf281713b | RegionOne | http://10.176.20.158:5000/v2.0 | http://10.176.20.158:5000/v2.0 | http://10.176.20.158:35357/v2.0 | | d728f31d9745467aaf53eeeba633ffe4 | RegionOne | http://10.176.20.158:8776/v1/%(tenant_id)s | http://10.176.20.158:8776/v1/%(tenant_id)s | http://10.176.20.158:8776/v1/%(tenant_id)s | | e298efba7f0148819c400a26e7f6f448 | RegionOne | http://10.176.20.158:8776/v1/%(tenant_id)s | http://10.176.20.158:8776/v1/%(tenant_id)s | http://10.176.20.158:8776/v1/%(tenant_id)s | +--+---+-+-++ root@bodega:~# keystone service-list +--+--+--+---+ |id| name | type | description| +--+--+--+---+ | 083662fed26d490b88172a3aa638107a | volume |volume|Nova Volume Service| | 3224949d951a4fb3b45adb5778caebfe | cinder |volume| Cinder Volume Service | | 55f097212ab948e5a2bf13e47ac1be9c | ec2| ec2 | EC2 Compatibility Layer | | 611a8d8380de4671863c2cd59a4d5bd8 | glance |image |Glance Image Service | | 90eedca2364b4a5bba477be31738c052 | keystone | identity | Keystone Identity Service | | a6552ffaa4904ec09ef399d71dd5e18f | swift | object-store | Object Storage Service | | f0f5c38f832f4584b93c562d1d756fa3 | nova | compute|Nova Compute Service | +--+--+--+---+ root@bodega:~# Thank you, Ahmed. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
