What is the OpenStack Cinder service status troubleshooting method

This article mainly introduces "what is the troubleshooting method of OpenStack Cinder service status". In daily operation, I believe many people have doubts about what is the troubleshooting method of OpenStack Cinder service status. The editor consulted various materials and sorted out simple and easy operation methods. I hope to help you answer the question of "what is the troubleshooting method of OpenStack Cinder service status"! Next, please follow the small series to learn together!

Recently, I manually built an openstack environment. When creating a hard disk, it failed. Check the log, and the prompt cannot be scheduled. It is suspected that there is a problem with the cinder node. Go to the cinder node to check the service. The status shows normal.

systemctl status openstack-cinder-volume.service

Then look at the finder service in the control node, openstack volume service list

Under normal circumstances:

The result shows that the state of the cinder-volume is down, check the log and find no error message, restart the various services of the cinder still have no effect, and finally decide to trace the source code (Note: The code in this article corresponds to the OpenStack Train version).

Find the implementation code corresponding to the openstack volume service list.

now = timeutils.utcnow(with_timezone=True)

Since the openstack-cinder-api.servic service is started on the controller node, what is obtained is the current time of the controller node.

services = objects.ServiceList.get_all(context, filters) Eventually gets all the service data from the services table in the finder database.

alive = abs(delta_sec)