openstack/swift
Code Issues Proposed changes

Additional step for Debugging Issues in SAIO

Browse Source 
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
This commit is contained in:
Andrew Welleck 2016-01-25 10:03:18 -06:00
parent 0e91aa8368
commit c790db8936
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/development_saio.rst
View File

@ -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.