On a RDO installation (controller and 2 compute nodes) I'd the following problem: couldn't login to the dashboard.

The message by login was:

An error occurred authenticating. Please try again later.

The solution was to start keystone

[root@csky03 ~]# /etc/init.d/openstack-keystone status

keystone dead but pid file exists

[root@csky03 ~]# /etc/init.d/openstack-keystone start

Starting keystone: [ OK ]

[root@csky03 ~]# /etc/init.d/openstack-keystone status

keystone (pid 18754) is running...

But the problem remains, since keystone dies after 1 - 3 days.

Is this RDO specific on an all in one controller and 2 compute nodes? Or does this happen also to other distros.

I could find some similar questions here, which stated to change SELinux to permissive or disable it at all, but in my case thats already in place.

Is anybody else facing a similar problem?

Any ideas why keystone dies after 1 - 3 days?

Note: a funny thing from my observations after some weeks: if I work with the system the whole day, this didn't happen to me anytime, but it seems that, if I sleep, keystone likes to sleep too :-) But sometimes it needs more that 2 days to go in sleep mode.

As a workaround, I'll now create a cron job to start keystone and let you know if it could fix the problem after 1 - 3 days:

Which openstack-keystone version is that?
Please add debug = True in keystone.conf before next restart, hopefully that will catch more info.
Or run it from shell with keystone-all -d and capture terminal output e.g. using script(1)

3 answers

There are some socket issues with keystone in the original havana release. Bug chain is at https://bugs.launchpad.net/python-nov... . This is now being backported to stable Havana so should appear in RDO when the next stable release is out.