Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

RDO: Keystone dies after 1 - 3 days, can't login into horizon dashboard

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?

As a workaround, I'll now create a cron job to restart keystone, if a dead keystone pid file exists :-)

click to hide/show revision 2
No.2 Revision

RDO: Keystone dies after 1 - 3 days, can't login into horizon dashboard

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.

later.

The solution was to start keystone

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

status keystone dead but pid file exists

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

start Starting keystone: [ OK ]

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

status keystone (pid 18754) is running...

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?

As a workaround, I'll now create a cron job to restart keystone, if a dead keystone pid file exists :-)

RDO: Keystone dies after 1 - 3 days, can't login into horizon dashboard

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.

later.

The solution was to start keystone

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

keystone dead but pid file exists exists

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

Starting keystone: [ OK ] ]

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

keystone (pid 18754) is running...

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?

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

[root@controller ~]# crontab -e

0 3 * * * /etc/init.d/openstack-keystone start

RDO: Keystone dies after 1 - 3 days, can't login into horizon dashboard

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:

[root@controller ~]# crontab -e

0 3 * * * /etc/init.d/openstack-keystone start