search

zhaoqin-github / misc

Miscellaneous things
0 stars 0 forks source link

Barbican can not start up after server restart #1

Open zhang-shengping opened 6 years ago

zhang-shengping commented 6 years ago

Barbican can not start up after server restart

Oct 24 22:35:38 localhost.localdomain systemd[1]: Unit openstack-barbican-api.service entered failed state.
Oct 24 22:35:38 localhost.localdomain systemd[1]: openstack-barbican-api.service failed.
Oct 24 22:35:39 localhost.localdomain systemd[1]: openstack-barbican-api.service holdoff time over, scheduling restart.
Oct 24 22:35:39 localhost.localdomain systemd[1]: Started Openstack Barbican API server.
Oct 24 22:35:39 localhost.localdomain systemd[1]: Starting Openstack Barbican API server...
Oct 24 22:35:40 localhost.localdomain gunicorn[15054]: 2018-10-24 22:35:40 [15054] [INFO] Starting gunicorn 18.0
Oct 24 22:35:40 localhost.localdomain gunicorn[15054]: Error: /run/barbican doesn't exist. Can't create pidfile.
Oct 24 22:35:40 localhost.localdomain systemd[1]: openstack-barbican-api.service: main process exited, code=exited, status=1/FAILURE
zhang-shengping commented 6 years ago

we need to create a new file name /run/barbican and change its owner to barbican:barbican after we restart server.

zhang-shengping commented 6 years ago

we may need to add this command as well: systemctl enable openstack-barbican-api.service