← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1692767] [NEW] Start keystone service failed with uwsgi in devstack

 

Public bug reported:

Enviroment
OS: CentOS7.2

I deployed the devstack environment successfully in CentOS system. After
rebooting the CentOS system, the keystone service could not be started.
The uwsgi raised exception as follows.

Apr 23 22:38:53 devstack.localdomain systemd[1]: devstack@keystone.service failed.
Apr 23 22:42:46 devstack.localdomain systemd[1]: Starting Devstack devstack@keystone.service...
Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: [uWSGI] getting INI configuration from /etc/keystone/keystone-uwsgi-public.ini
Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: open("./python_plugin.so"): No such file or directory [core/utils.c line 3686]
Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: !!! UNABLE to load uWSGI plugin: ./python_plugin.so: cannot open shared object file: No such file or directory !!!
Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: *** Starting uWSGI 2.0.15 (64bit) on [Sun Apr 23 22:42:46 2017] ***
Apr 23 22:42:46 devstack.localdomain systemd[1]: devstack@keystone.service: main process exited, code=exited, status=1/FAILURE
Apr 23 22:42:46 devstack.localdomain systemd[1]: Failed to start Devstack devstack@keystone.service.
Apr 23 22:42:46 devstack.localdomain systemd[1]: Unit devstack@keystone.service entered failed state.
Apr 23 22:42:46 devstack.localdomain systemd[1]: devstack@keystone.service failed.

So i think this is a bug. I tried to create the /var/run/uwsgi directory and chown it stack user. Then it works.
sudo mkdir -p /var/run/uwsgi
sudo chown stack:stack uwsgi

So what do you think that?

** Affects: keystone
     Importance: Undecided
     Assignee: Tao Li (eric-litao)
         Status: New

** Changed in: keystone
     Assignee: (unassigned) => Tao Li (eric-litao)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1692767

Title:
  Start keystone service failed with uwsgi in devstack

Status in OpenStack Identity (keystone):
  New

Bug description:
  Enviroment
  OS: CentOS7.2

  I deployed the devstack environment successfully in CentOS system.
  After rebooting the CentOS system, the keystone service could not be
  started. The uwsgi raised exception as follows.

  Apr 23 22:38:53 devstack.localdomain systemd[1]: devstack@keystone.service failed.
  Apr 23 22:42:46 devstack.localdomain systemd[1]: Starting Devstack devstack@keystone.service...
  Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: [uWSGI] getting INI configuration from /etc/keystone/keystone-uwsgi-public.ini
  Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: open("./python_plugin.so"): No such file or directory [core/utils.c line 3686]
  Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: !!! UNABLE to load uWSGI plugin: ./python_plugin.so: cannot open shared object file: No such file or directory !!!
  Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: *** Starting uWSGI 2.0.15 (64bit) on [Sun Apr 23 22:42:46 2017] ***
  Apr 23 22:42:46 devstack.localdomain systemd[1]: devstack@keystone.service: main process exited, code=exited, status=1/FAILURE
  Apr 23 22:42:46 devstack.localdomain systemd[1]: Failed to start Devstack devstack@keystone.service.
  Apr 23 22:42:46 devstack.localdomain systemd[1]: Unit devstack@keystone.service entered failed state.
  Apr 23 22:42:46 devstack.localdomain systemd[1]: devstack@keystone.service failed.

  So i think this is a bug. I tried to create the /var/run/uwsgi directory and chown it stack user. Then it works.
  sudo mkdir -p /var/run/uwsgi
  sudo chown stack:stack uwsgi

  So what do you think that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1692767/+subscriptions


Follow ups