Ask Your Question
1

failed to start keystone

asked 2014-05-15 07:28:36 -0500

arindamchoudhury gravatar image

updated 2014-05-15 10:11:18 -0500

Hi,

I am using fedora 20. While I am running packstack I am getting this error:

Error: 

Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Redirecting to /bin/systemctl start  openstack-keystone.service
Job for openstack-keystone.service failed. See 'systemctl status openstack-keystone.service' and 'journalctl -xn' for details.
Wrapped exception:
Execution of '/sbin/service openstack-keystone start' returned 1: Redirecting to /bin/systemctl start  openstack-keystone.service
Job for openstack-keystone.service failed. See 'systemctl status openstack-keystone.service' and 'journalctl -xn' for details.
Error: /Stage[main]/Keystone/Service[keystone]/ensure: change from stopped to running failed: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Redirecting to /bin/systemctl start  openstack-keystone.service
Job for openstack-keystone.service failed. See 'systemctl status openstack-keystone.service' and 'journalctl -xn' for details.

Keystone log says:

2014-05-15 14:18:47.155 20320 INFO keystone.common.openssl [-] openssl genrsa -out /etc/keystone/ssl/private/cakey.pem 2048
2014-05-15 14:18:47.245 20320 INFO keystone.common.openssl [-] openssl req -new -x509 -extensions v3_ca -key /etc/keystone/ssl/private/cakey.pem -out /etc/keystone/ssl/certs/ca.pem -days 3650 -config /etc/keystone/ssl/certs/openssl.conf -subj /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com
2014-05-15 14:18:47.254 20320 INFO keystone.common.openssl [-] openssl genrsa -out /etc/keystone/ssl/private/signing_key.pem 2048
2014-05-15 14:18:47.333 20320 INFO keystone.common.openssl [-] openssl req -key /etc/keystone/ssl/private/signing_key.pem -new -out /etc/keystone/ssl/certs/req.pem -config /etc/keystone/ssl/certs/openssl.conf -subj /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com
2014-05-15 14:18:47.342 20320 INFO keystone.common.openssl [-] openssl ca -batch -out /etc/keystone/ssl/certs/signing_cert.pem -config /etc/keystone/ssl/certs/openssl.conf -days 3650d -cert /etc/keystone/ssl/certs/ca.pem -keyfile /etc/keystone/ssl/private/cakey.pem -infiles /etc/keystone/ssl/certs/req.pem

journalctl -xn

-- Logs begin at Wed 2014-05-07 15:29:55 CEST, end at Thu 2014-05-15 16:27:53 CEST. -- May 15 16:27:53 aopcach.uab.es keystone-all[30542]: ImportError: cannot import name systemd May 15 16:27:53 aopcach.uab.es systemd[1]: openstack-keystone.service: main process exited, code=exited, status=1/FAILURE May 15 16:27:53 aopcach.uab.es systemd[1]: Failed to start OpenStack Identity Service (code-named Keystone).
-- Subject: Unit openstack-keystone.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit openstack-keystone.service has failed.
-- 
-- The result is failed. May 15 16:27:53 aopcach.uab.es systemd[1]: Unit openstack-keystone.service entered failed state. May 15 16:27:53 aopcach.uab.es systemd[1]: openstack-keystone.service holdoff time over, scheduling restart. May 15 16:27:53 aopcach.uab.es systemd[1]: Stopping OpenStack Identity Service (code-named Keystone)...
-- Subject: Unit openstack-keystone.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit openstack-keystone.service has begun shutting down. May 15 16:27:53 ...
(more)
edit retag flag offensive close merge delete

Comments

Is that the entire contents of your keystone log? There are no errors there, which is puzzling. What does journalctl show as the output from the keystone service startup?

larsks gravatar imagelarsks ( 2014-05-15 08:47:41 -0500 )edit

4 answers

Sort by » oldest newest most voted
4

answered 2014-05-16 08:44:50 -0500

I think this corresponds to https://bugzilla.redhat.com/1098160 That suggested that this install is corrupted due to devstack

edit flag offensive delete link more
0

answered 2015-01-31 16:54:46 -0500

Hi all, I have similar problem once installed, keystone cannot be started, I suspect an installation problem :

[root@localhost ~]# sudo systemctl start openstack-keystone.service && sudo systemctl enable openstack-keystone.service Job for openstack-keystone.service failed. See "systemctl status openstack-keystone.service" and "journalctl -xe" for details. [root@localhost ~]# journalctl -xe janv. 31 23:48:11 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:11 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:11 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:11 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:11 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:12 localhost.localdomain keystone-all[32608]: 2015-01-31 23:48:12.472 32608 CRITICAL keystone [-] ConfigFileNotFound: An unexpected error preve janv. 31 23:48:12 localhost.localdomain systemd[1]: openstack-keystone.service: main process exited, code=exited, status=1/FAILURE janv. 31 23:48:12 localhost.localdomain systemd[1]: Failed to start OpenStack Identity Service (code-named Keystone). -- Subject: L'unité (unit) openstack-keystone.service a échoué -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel (http://lists.freedesktop.org/mailman/...)

-- L'unité (unit) openstack-keystone.service a échoué, avec le résultat failed. janv. 31 23:48:12 localhost.localdomain systemd[1]: Unit openstack-keystone.service entered failed state. janv. 31 23:48:12 localhost.localdomain systemd[1]: openstack-keystone.service failed. janv. 31 23:48:12 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:12 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:12 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:12 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:12 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:12 localhost.localdomain sedispatch[635]: AVC Message for setroubleshoot, dropping message janv. 31 23:48:12 localhost.localdomain setroubleshoot[32565]: SELinux is preventing keystone-all from getattr access on the file /usr/share/keystone/keystone janv. 31 23:48:12 localhost.localdomain python[32565]: SELinux is preventing keystone-all from getattr access on the file /usr/share/keystone/keystone-dist.co

                                                   *****  Plugin catchall (100. confidence) suggests   **************************

                                                   If you believe that keystone-all should be allowed getattr access on the keystone-dist.conf file by def
                                                   Then you should report this as a bug.
                                                   You can generate a local policy module to allow this access.
                                                   Do
                                                   allow this access for now by executing:
                                                   # grep keystone-all /var/log/audit/audit.log | audit2allow -M mypol
                                                   # semodule -i mypol.pp

janv. 31 23:48:12 localhost.localdomain systemd[1]: start request repeated too quickly for openstack-keystone.service janv. 31 23:48:12 localhost.localdomain systemd[1]: Failed to start OpenStack Identity Service (code-named Keystone). -- Subject: L'unité (unit) openstack-keystone.service a échoué -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel (http://lists.freedesktop.org/mailman/...)

-- L ... (more)

edit flag offensive delete link more
0

answered 2015-06-04 07:08:44 -0500

Mitali gravatar image

Enable Keystone Debug: $ runuser -s /bin/sh keystone -c "/usr/bin/keystone-all --debug"

[root@Controller-Fedora-Fresh ~]# runuser -s /bin/sh keystone -c "/usr/bin/keystone-all --debug" Traceback (most recent call last): File "/usr/bin/keystone-all", line 120, in <module> config.setup_logging() File "/usr/lib/python2.7/site-packages/keystone/config.py", line 56, in setup_logging log.setup('keystone') File "/usr/lib/python2.7/site-packages/keystone/openstack/common/log.py", line 461, in setup _setup_logging_from_conf(product_name, version) File "/usr/lib/python2.7/site-packages/keystone/openstack/common/log.py", line 525, in _setup_logging_from_conf filelog = logging.handlers.WatchedFileHandler(logpath) File "/usr/lib64/python2.7/logging/handlers.py", line 392, in __init__ logging.FileHandler.__init__(self, filename, mode, encoding, delay) File "/usr/lib64/python2.7/logging/__init__.py", line 902, in __init__ StreamHandler.__init__(self, self._open()) File "/usr/lib64/python2.7/logging/__init__.py", line 925, in _open stream = open(self.baseFilename, self.mode) IOError: [Errno 13] Permission denied: '/var/log/keystone/keystone.log'

Check keystone log file permission:

[root@Controller-Fedora-Fresh ~]# ll /var/log/keystone/keystone.log -rw-r--r--. 1 root root 177 Jun 3 18:05 /var/log/keystone/keystone.log

edit flag offensive delete link more
0

answered 2014-05-15 10:05:33 -0500

larsks gravatar image

In the future, please update your question with the new information rather than posting it as a comment. Thanks!

Looking at what you've posted, there's a clear error message there:

May 15 16:27:53 aopcach.uab.es keystone-all[30542]: ImportError: cannot import name systemd 
May 15 16:27:53 aopcach.uab.es systemd[1]: openstack-keystone.service: main process exited, code=exited, status=1/FAILURE 
May 15 16:27:53 aopcach.uab.es systemd[1]: Failed to start OpenStack Identity Service (code-named Keystone). -- Subject: Unit openstack-keystone.service has failed -- Defined-By: systemd

It looks like your system is missing the systemd-python package. Try installing that package and see if it resolves the problem.

If this does correct the problem, you may want to open a bug in Red Hat's bug tracker.

edit flag offensive delete link more

Comments

hi,i am failed to

 [ruan@cloudlab38 /]$ sudo  /etc/init.d/openstack-keystone start
   Starting keystone:                                         [FAILED]

where should I check the logs?how can I get more information? thx

Ryans gravatar imageRyans ( 2014-05-27 02:00:36 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-05-15 07:28:36 -0500

Seen: 5,936 times

Last updated: May 16 '14