From c790db89369221473bcbfc23f301424ab8d30d60 Mon Sep 17 00:00:00 2001 From: Andrew Welleck Date: Mon, 25 Jan 2016 10:03:18 -0600 Subject: [PATCH] Additional step for Debugging Issues in SAIO Adding an additional debugging step for the SAIO "Debugging Issues" section. Adding step to check if memcache is running and to start it if its not. Change-Id: I0bfa563f595dbefcf907494451fad45e6310db88 --- doc/source/development_saio.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/source/development_saio.rst b/doc/source/development_saio.rst index 2dfd0ffbcb..bca218cad5 100644 --- a/doc/source/development_saio.rst +++ b/doc/source/development_saio.rst @@ -587,3 +587,7 @@ doesn't work, here are some good starting places to look for issues: cannot rate limit (unit tests generate a lot of logs very quickly). Open the file ``SWIFT_TEST_CONFIG_FILE`` points to, and change the value of ``fake_syslog`` to ``True``. +#. If you encounter a ``401 Unauthorized`` when following Step 12 where + you check that you can ``GET`` account, use ``sudo service memcached status`` + and check if memcache is running. If memcache is not running, start it using + ``sudo service memcached start``. Once memcache is running, rerun ``GET`` account.