Which is the best order to restart Openstack controller services?

asked 2019-08-27 13:35:52 -0600

renanb02 gravatar image

updated 2019-08-27 13:44:09 -0600

Every time I reboot my controller, services return errors and some of them fail and not start (like etcd and mariadb, but also happens with others at times). After restarting those that fail, the errors remain and I have to restart all other services sort of guessing the best order. Is there any recommendation about the services order startup?

For reference, these are the main Openstack-related services running on the controller:

etcd httpd neutron-dhcp-agent neutron-l3-agent neutron-linuxbridge-agent neutron-metadata-agent neutron-server openstack-glance-api openstack-glance-registry openstack-nova-api openstack-nova-conductor openstack-nova-consoleauth openstack-nova-novncproxy openstack-nova-scheduler mariadb rabbitmq-server
edit retag flag offensive close merge delete



I don't think that there is a specific order. If you start the fundamental services like DB, AMQP and etcd first, you will avoid a few OpenStack log messages at startup, but those messages are benign.

If MariaDB doesn't start at all, you need to find out what's wrong with your DB configuration.

Bernd Bausch gravatar imageBernd Bausch ( 2019-08-27 18:48:47 -0600 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2019-08-29 12:51:41 -0600

renanb02 gravatar image

Based on Bernd's answer, I used Monit to guarantee that etcd and mariadb will be up when the machine reboots.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2019-08-27 13:35:52 -0600

Seen: 238 times

Last updated: Aug 29 '19