Ask Your Question

Error accessing Dashboard: "RuntimeError Unable to create a new session key"

asked 2014-07-23 06:56:37 -0500

fhussain gravatar image

updated 2014-07-23 06:57:03 -0500


I am trying to access Dashboard via web browser using the url http://controller/horizon . The login is successful, but after that a page is displayed " Something went wrong! An unexpected error has occurred. Try refreshing the page".

I have checked the error log in /var/log/apache2/error.log and the error is this:

RuntimeError: Unable to create a new session key. It is likely that the cache is unavailable.

Please help me solve the issue.


edit retag flag offensive close merge delete

6 answers

Sort by » oldest newest most voted

answered 2016-12-26 05:49:21 -0500

sanjay gravatar image

Thanks It worked after #SESSION_ENGINE = 'django.contrib.sessions.backends.cache'

edit flag offensive delete link more

answered 2016-06-08 06:35:37 -0500

MrDan gravatar image

Yes, this worked.

edit flag offensive delete link more

answered 2016-06-17 15:31:36 -0500

dchowdhu gravatar image

Yes, it did work. I had same problem and changing memcached location did work for me. However, I am sseeing "unexpected error" when browsing Network=>topology sections within horizon dashboard. Perhaps I need to configure network topology in the neurton.conf. Any suggestion.

edit flag offensive delete link more

answered 2016-09-26 06:25:23 -0500

Dhamodran P gravatar image

I too faced the same problem ,

Comment out the line SESSION_ENGINE from /etc/openstack-dashboard/local_settings file.

This fixed my issue

edit flag offensive delete link more


This also fixed my problem. Checked django document. It seemed that this is openstack doc error.

Jared gravatar imageJared ( 2017-02-13 21:40:29 -0500 )edit

answered 2017-07-23 14:29:23 -0500

Pranay Sagar gravatar image

I figured out my problem: The problem is I did not see the note after you edit /etc/sysconfig/memcached file. I had to change this line -l to this line -l MangementcontrollerIP (for Example- The IP that you set in mentioned file
/etc/openstack-dashboard/local_settings CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '', } } After the just run this command : systemctl restart memcached.service

Hope it will work for you ... if not Kindly paste you error.log file will trying to help you out ...

edit flag offensive delete link more

answered 2016-04-07 23:19:15 -0500

IceX gravatar image

I had the same problem....

SESSION_ENGINE = 'django.contrib.sessions.backends.cache'

CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': 'controller1:11211', } } If I use the fqdn (e.g controller1) in the location it fails, try changing it to the IP (e.g. or

SESSION_ENGINE = 'django.contrib.sessions.backends.cache'

CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '', } }

edit flag offensive delete link more


Did you solve this problem ? ı had same problem too.

gokhan.isik gravatar imagegokhan.isik ( 2016-05-30 05:45:36 -0500 )edit

We had the same problem after trying to change an endpoint. Removing the SESSION_ENGINE line worked as a workaround. The root problem was that memcached had started to run on another IP, so after fixing that (review its config.json file) and restarting the container, the problem was fixed

Joris gravatar imageJoris ( 2020-05-14 09:05:07 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2014-07-23 06:56:37 -0500

Seen: 5,204 times

Last updated: Jul 23 '17