[Starlingx-discuss] glance api service is not started in all-in-one deployment
Stefan.Dinescu at windriver.com
Fri Nov 2 10:11:14 UTC 2018
On StarlingX, glance-api is managed by SM (short for service management).
You can see a list of all the services by using "sm-dump" (from a root prompt or use sudo). If it is working, the sate should be "enabled-active". To restart the service us "sm-restart service glance-api".
Also check the logs (/var/log/glance/glance-api.log) for any obvious errors that prevent the service from restarting.
From: Fang, Liang A [liang.a.fang at intel.com]
Sent: Friday, November 02, 2018 11:34 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment
I deployed an starlingx all-in-one environment, and it seems glance api service has not been started.
I also checked other services such as cinder api / cinder volume, there are started.
/bin/sh /usr/lib/ocf/resource.d/openstack/cinder-schedule start
/bin/sh /usr/lib/ocf/resource.d/openstack/cinder-volume start
/bin/sh /usr/lib/ocf/resource.d/openstack/cinder-backup start
But these are not started by service file such as openstack-cinder-api.service / openstack-cinder-scheduler.service. This is really different with the deployment by devstack.
Could anybody point out how the services are started? How to restart cinder/glance service in starlingx deployment? Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Starlingx-discuss