openstack - nova ERROR: [Errno 111] Connection refused -


i'm using centos 6.5 x86_64 setup openstack havana , services work well. when i've rebooted operating system, i've founded nova service not work properly, following error triggered:

nova flavor-list error: [errno 111] connection refused 

reviewing log files in / var / log / nova gives following error:

2014-03-24 12:24:04.293 6275 info nova.osapi_compute.wsgi.server [-] (6275) wsgi starting   2014-03-24 12:24:04.297 6267 critical nova [-] [errno 98] address in use  2014-03-24 12:24:04.412 6275 info nova.openstack.common.service [-] parent process has died unexpectedly, exiting  2014-03-24 12:24:04.412 6274 info nova.openstack.common.service [-] parent process has died unexpectedly, exiting  2014-03-24 12:24:04.412 6275 info nova.wsgi [-] stopping wsgi server.  2014-03-24 12:24:04.412 6274 info nova.wsgi [-] stopping wsgi server. 

the state of openstack server

nova-manage service list  binary           host                                 zone             status     state updated_at nova-cert        controller                           internal         enabled    :-)   2014-03-24 14:28:03 nova-consoleauth controller                           internal         enabled    :-)   2014-03-24 14:28:01 nova-scheduler   controller                           internal         enabled    :-)   2014-03-24 14:28:00 nova-conductor   controller                           internal         enabled    :-)   2014-03-24 14:27:59 nova-compute     controller                           nova             enabled    :-)   2014-03-24 14:28:06 nova-network     controller                           internal         enabled    :-)   2014-03-24 14:27:58  keystone service-list  +----------------------------------+----------+----------+---------------------------+ |                id                |   name   |   type   |        description        | +----------------------------------+----------+----------+---------------------------+ | 7ce108d652ee48d7897127045a371795 |  cinder  |  volume  |   cinder volume service   | | 9452b875328f4763b7766eb533bd75c4 | cinderv2 | volumev2 |  cinder volume service v2 | | e9607d1a308140298f8364fd2a0e62a8 |  glance  |  image   |    glance image service   | | b7ac07f69e2e41f684d6470c69db4781 | keystone | identity | keystone identity service | | cbdfa73329094d7d94c7464b9bf0ef7d |   nova   | compute  |    nova compute service   | +----------------------------------+----------+----------+---------------------------+  ps -ef | grep "nova-api"  nova      2522     1  0 11:22 ?        00:00:00 /usr/bin/python /usr/bin/nova-api-metadata --logfile /var/log/nova/metadata-api.log root     11909  6217  0 15:11 pts/1    00:00:01 gedit nova-api.log root     12644  3832  0 15:31 pts/0    00:00:00 grep nova-api   netstat -napo | grep 877  tcp        0      0 0.0.0.0:8775                0.0.0.0:*                   listen      2522/python         off (0.00/0/0) 

any pointers extremely helpful.

thanks

firstly, recommend find or ask answer on ask.openstack.org

then described, may caused by: you've enabled nova-api-metadata , nova-api service in same time.

from default configuration know that: ['ec2', 'osapi_compute', 'metadata'] enabled, see https://github.com/openstack/nova/blob/stable/havana/nova/service.py#l55

so start each service 1 one when nova-api service called, see https://github.com/openstack/nova/blob/stable/havana/nova/cmd/api.py#l45

since nova-api-metadata service running, cause 8775 port used, 1 service launched nova-api die , since exception not caught, other 2 die too, see in log

if i've assumed right, please cancel nova-api-metadata service , use nova-api service only, means 'chkconfig openstack-nova-api-metadata off; chkconfig openstack-nova-api on', i'm not sure specific service name on system, should that, correct if i'm wrong


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -