Ask Your Question
0

Nova services are dead on CentOS

asked 2014-02-25 22:20:55 -0500

Dheeraj gravatar image

updated 2014-02-25 23:25:55 -0500

Anand TS gravatar image

hi, i install openstack havana via packstack. It shows installation was successfully completed; but when I run the openstack-status commanad it shows nova components are dead.

root@geforce ~(keystone_admin)]# openstack-status

== Nova services ==

openstack-nova-api:                     dead

openstack-nova-cert:                    dead

openstack-nova-compute:                 dead

openstack-nova-network:                 dead

openstack-nova-scheduler:               dead

openstack-nova-conductor:               dead

== Glance services ==

openstack-glance-api:                   active

openstack-glance-registry:              active

== Keystone service ==

openstack-keystone:                     active

== Horizon service ==

openstack-dashboard:                    active

== neutron services ==

neutron-server:                         active

neutron-dhcp-agent:                     active

neutron-l3-agent:                       active

neutron-metadata-agent:                 active

neutron-lbaas-agent:                    active

neutron-openvswitch-agent:              active

== Swift services ==

openstack-swift-proxy:                  active

openstack-swift-account:                active

openstack-swift-container:              active

openstack-swift-object:                 active

== Cinder services ==

openstack-cinder-api:                   active

openstack-cinder-scheduler:             active

openstack-cinder-volume:                active

== Ceilometer services ==

openstack-ceilometer-api:               active

openstack-ceilometer-central:           active

openstack-ceilometer-compute:           active

openstack-ceilometer-collector:         active

openstack-ceilometer-alarm-notifier:    active

openstack-ceilometer-alarm-evaluator:   active

== Heat services ==

openstack-heat-api:                     active

openstack-heat-api-cfn:                 active

openstack-heat-api-cloudwatch:          active

openstack-heat-engine:                  active

== Support services ==

mysqld:                                 active

libvirtd:                               active

openvswitch:                            active

messagebus:                             active

tgtd:                                   active

qpidd:                                  active

memcached:                              active

And, I am also atteching my packstack answer file :

[general]

# Path to a Public key to install on servers. If a usable key has not
# been installed on the remote servers the user will be prompted for a
# password and this key will be installed so the password will not be
# required again
CONFIG_SSH_KEY=/root/.ssh/id_rsa.pub

# Set to 'y' if you would like Packstack to install MySQL
CONFIG_MYSQL_INSTALL=y

# Set to 'y' if you would like Packstack to install OpenStack Image
# Service (Glance)
CONFIG_GLANCE_INSTALL=y

# Set to 'y' if you would like Packstack to install OpenStack Block
# Storage (Cinder)
CONFIG_CINDER_INSTALL=y

# Set to 'y' if you would like Packstack to install OpenStack Compute
# (Nova)
CONFIG_NOVA_INSTALL=y

# Set to 'y' if you would like Packstack to install OpenStack
# Networking (Neutron)
CONFIG_NEUTRON_INSTALL=y

# Set to 'y' if you would like Packstack to install OpenStack
# Dashboard (Horizon)
CONFIG_HORIZON_INSTALL=y

# Set to 'y' if you would like Packstack to install OpenStack Object
# Storage (Swift)
CONFIG_SWIFT_INSTALL=y

# Set to 'y' if you would like Packstack to install OpenStack
# Metering (Ceilometer)
CONFIG_CEILOMETER_INSTALL=y

# Set to 'y' if you would like Packstack to install OpenStack
# Orchestration (Heat)
CONFIG_HEAT_INSTALL=y

# Set to 'y' if you would like Packstack to install the OpenStack
# Client packages. An admin "rc" file will also be installed
CONFIG_CLIENT_INSTALL=y

# Comma separated list of NTP servers. Leave plain if Packstack
# should not install ntpd on instances.
CONFIG_NTP_SERVERS=

# Set to 'y' if you would like Packstack to install Nagios to monitor
# OpenStack hosts
CONFIG_NAGIOS_INSTALL=y

# Comma separated list of servers to be excluded from installation in
# case you are running Packstack the second time with the same answer
# file and don't want Packstack to touch these servers. Leave plain if
# you don't need to exclude any server.
EXCLUDE_SERVERS=

# The IP address of the server on which to install MySQL
CONFIG_MYSQL_HOST=172.17.15.23

# Username for the MySQL admin user
CONFIG_MYSQL_USER=root

# Password for the MySQL admin user
CONFIG_MYSQL_PW=xxxxxxxxxxxxx

# The IP address of the server on which to install the QPID service
CONFIG_QPID_HOST=172.17.15.23

# Enable SSL for the QPID service
CONFIG_QPID_ENABLE_SSL=y

# Enable Authentication for the QPID service
CONFIG_QPID_ENABLE_AUTH=n

# The password for the NSS certificate database ...
(more)
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
1

answered 2014-02-25 23:30:27 -0500

Anand TS gravatar image

Hi Dheeraj,

What you get if you restart all the openstack services?

did the packstack run successfully?

Regards, Anand

edit flag offensive delete link more

Comments

Hi, Anand when i am going to restart the service it's show like this: [root@geforce ~(keystone_admin)]# service nova-api restart nova-api: unrecognized service [root@geforce ~(keystone_admin)]# service nova-cert restart nova-cert: unrecognized service [root@geforce ~(keystone_admin)]# service nova-network restart nova-network: unrecognized service [root@geforce ~(keystone_admin)]# service nova-compute restart nova-compute: unrecognized service [root@geforce ~(keystone_admin)]# service nova-scheduler restart nova-scheduler: unrecognized service [root@geforce ~(keystone_admin)]# service nova-conductor restart nova-conductor: unrecognized service [root@geforce ~(keystone_admin)]#

Dheeraj gravatar imageDheeraj ( 2014-02-26 00:55:14 -0500 )edit

On Centos 6.X : # chkconfig --list | grep openstack-nova On Fedora :- # systemctl list-units | grep openstack-nova

dbaxps gravatar imagedbaxps ( 2014-02-26 01:36:47 -0500 )edit

hi Anand, i try this commend chkconfig --list | grep openstack-nova it showed something like this [root@geforce ~]# chkconfig --list | grep openstack-nova openstack-nova-api 0:off 1:off 2:on 3:on 4:on 5:on 6:off openstack-nova-cert 0:off 1:off 2:on 3:on 4:on 5:on 6:off openstack-nova-compute 0:off 1:off 2:on 3:on 4:on 5:on 6:off openstack-nova-conductor 0:off 1:off 2:on 3:on 4:on 5:on 6:off openstack-nova-console 0:off 1:off 2:off 3:off 4:off 5:off 6:off openstack-nova-consoleauth 0:off 1:off 2:on 3:on 4:on 5:on 6:off openstack-nova-metadata-api 0:off 1:off 2:on 3:on 4:on 5:on 6:off openstack-nova-network 0:off 1:off 2:on 3:on 4:on 5:on 6:off openstack-nova-novncproxy 0:off 1:off 2:on 3:on ...(more)

Dheeraj gravatar imageDheeraj ( 2014-02-26 22:16:47 -0500 )edit
0

answered 2014-02-26 07:51:13 -0500

Can you look at the nova logs. Anything informative in /var/log/nova/api.log for example?

edit flag offensive delete link more

Comments

hi RDO, the api.log file is too big and how can i find where is error.

Dheeraj gravatar imageDheeraj ( 2014-02-26 22:19:59 -0500 )edit
1

Hi Dheeraj, The command you gave to restart openstack service is wrong, instead of service nova-compute restart you have to give eg. #service openstack-nova-compute restart

Anand TS gravatar imageAnand TS ( 2014-02-26 23:26:30 -0500 )edit

Hi, Anand TS when i run this command service openstack-nova-compute restart it starts but again the nova components are dead. [root@geforce ~(keystone_admin)]# service openstack-nova-compute restart Stopping openstack-nova-compute: [FAILED] Starting openstack-nova-compute: [ OK ] [root@geforce ~(keystone_admin)]# openstack-status == Nova services == openstack-nova-api: dead openstack-nova-cert: dead openstack-nova-compute: dead openstack-nova-network: dead openstack-nova-scheduler: dead openstack-nova-conductor: dead == Nova managed services == ERROR: <attribute 'message'="" of="" 'exceptions.baseexception'="" objects=""> (HTTP 504) == Nova networks == ERROR: <attribute 'message'="" of="" 'exceptions.baseexception'="" objects=""> (HTTP 504) == Nova instance flavors == ERROR: <attribute 'message'="" of="" 'exceptions.baseexception'="" objects=""> (HTTP 504)

Dheeraj gravatar imageDheeraj ( 2014-02-28 00:46:49 -0500 )edit

Hi Dheeraj, Pls contact me at anandts124@gmail.com so that we can do further troubleshooting. I'm not getting much information to proceed from what you said.

Anand TS gravatar imageAnand TS ( 2014-02-28 05:59:08 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2014-02-25 22:20:55 -0500

Seen: 2,331 times

Last updated: Feb 26 '14