How to restart the openstack service
This article mainly introduces how to restart the openstack service, the article is very detailed, has a certain reference value, interested friends must read it!
The actual production environment is the juno version. Refer to the document "openstack-ops-manual" on the official website, which says "servcie stop first, then start". It is troublesome to restart directly. The restart command after arrangement is as follows:
one
Service rabbitmq-server restart
Supplement: rabbitmq service status view command: rabbitmqctl status
OpenStack Identity:
one
Service openstack-keystone restart
OpenStack Image Service:
one
two
Service openstack-glance-api restart
Service openstack-glance-registry restart
OpenStack Compute:
one
two
three
four
five
six
# service openstack-nova-api restart
# service openstack-nova-scheduler restart
# service openstack-nova-conductor restart
# service openstack-nova-cert restart
# service openstack-nova-consoleauth restart
# service openstack-nova-novncproxy restart
OpenStack Block Storage:
one
two
# service openstack-cinder-api restart
# service openstack-cinder-scheduler restart
Restart compute services:
one
two
three
# service openstack-nova-compute restart
# service openstack-nova-network restart
# service openstack-nova-metadata-api restart
Restart ceilometer services:
one
# service ceilometer-api restart
The neutron section refers to the service name listed below:
[root@node-9 ~] # chkconfig-- list | grep neutron
Neutron-dhcp-agent0:off1:off2:on3:on4:on5:on6:off
Neutron-l3-agent0:off1:off2:on3:on4:on5:on6:off
Neutron-lbaas-agent0:off1:off2:off3:off4:off5:off6:off
Neutron-metadata-agent0:off1:off2:on3:on4:on5:on6:off
Neutron-openvswitch-agent0:off1:off2:on3:on4:on5:on6:off
Neutron-ovs-cleanup0:off1:off2:on3:on4:on5:on6:off
Neutron-server 0:off1:off2:on3:on4:on5:on6:off
The specific command is service + above the service name + restart, which will not be repeated here.
Finally, you can use the following command to check whether there are missing services that have not been restarted. Generally speaking, the above restart command should be sufficient. Some processes are not critical and can not be restarted, depending on your needs.
[root@node-9 ~] # chkconfig-- list | grep openstack
Openstack-cinder-api0:off1:off2:on3:on4:on5:on6:off
Openstack-cinder-backup0:off1:off2:off3:off4:off5:off6:off
Openstack-cinder-scheduler0:off1:off2:on3:on4:on5:on6:off
Openstack-cinder-volume0:off1:off2:off3:off4:off5:off6:off
Openstack-glance-api0:off1:off2:on3:on4:on5:on6:off
Openstack-glance-registry0:off1:off2:on3:on4:on5:on6:off
Openstack-glance-scrubber0:off1:off2:off3:off4:off5:off6:off
Openstack-heat-api0:off1:off2:on3:on4:on5:on6:off
Openstack-heat-api-cfn0:off1:off2:on3:on4:on5:on6:off
Openstack-heat-api-cloudwatch0:off1:off2:on3:on4:on5:on6:off
Openstack-heat-engine0:off1:off2:on3:on4:on5:on6:off
Openstack-keystone0:off1:off2:on3:on4:on5:on6:off
Openstack-nova-api0:off1:off2:on3:on4:on5:on6:off
Openstack-nova-cert0:off1:off2:on3:on4:on5:on6:off
Openstack-nova-conductor0:off1:off2:on3:on4:on5:on6:off
Openstack-nova-console0:off1:off2:off3:off4:off5:off6:off
Openstack-nova-consoleauth0:off1:off2:on3:on4:on5:on6:off
Openstack-nova-metadata-api0:off1:off2:off3:off4:off5:off6:off
Openstack-nova-novncproxy0:off1:off2:on3:on4:on5:on6:off
Openstack-nova-objectstore0:off1:off2:on3:on4:on5:on6:off
Openstack-nova-scheduler0:off1:off2:on3:on4:on5:on6:off
Openstack-nova-xvpvncproxy0:off1:off2:off3:off4:off5:off6:off
The above is all the contents of the article "how to restart openstack Services". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!
