Ask Your Question

how to debug swift on CentOS

asked 2013-10-08 13:53:17 -0500

henry1987 gravatar image

updated 2013-10-08 13:54:54 -0500


I installed a swift cluster on CentOS 6.4 which includes 5 virtual machines (nodes). All ports such as 8888,5000,35357, 6000,6001,6002 etc are opened. When I ran swift list command, I got

Account GET failed: http://x.x.x.180:8888/v1/AUTH_4e549f18a3f645ddaa034bb325e457ab?format=json 503 Internal Server Error [first 60 chars of response]

Service Unavailable

The server is currently.

The log file shows

Oct 8 12:44:04 sproxyc proxy-server Could not autocreate account 'AUTH_4e549f18a3f645ddaa034bb325e457ab' (txn: tx8eb1d81268d54682a60ff4c3e1e9779b) (client_ip: x.x.x.180)

Can anyone tell me what are the possible causes? how to debug swift?

The following are the settings.

the nodes are: keystone: x.x.x.179
sproxy: x.x.x.180
snode01: x.x.x.181
snode02: x.x.x.182
snode03: x.x.x.183

proxy-server.conf as shown below:


bind_port = 8888

workers = 8
user = swift

pipeline = catch_errors healthcheck proxy-logging cache authtoken keystone proxy-server

use = egg:swift#proxy
allow_account_management = true
account_autocreate = true

use = egg:swift#memcache
memcache_servers = x.x.x.180:11211

use = egg:swift#catch_errors

use = egg:swift#healthcheck

use = egg:swift#keystoneauth
operator_roles = admin, SwiftOperator
is_admin = true
cache = swift.cache

paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory
delay_auth_decision =true
signing_dir = /home/swift/keystone-signing
auth_protocol = http
auth_host = x.x.x.179
auth_port = 35357
admin_tenant_name =service
admin_user =swift
admin_password =stack
admin_token = ADMIN
auth_token = ADMIN
use = egg:swift#proxy_logging

edit retag flag offensive close merge delete


Also can you paste the configuration you keystone.conf?

koolhead17 gravatar imagekoolhead17 ( 2013-10-10 07:23:20 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2013-10-11 16:08:59 -0500

torgomatic gravatar image

You have a transaction ID: tx8eb1d81268d54682a60ff4c3e1e9779b. Look for that string in all the logs, not just the proxy logs, and you'll hopefully find some stack traces that tell you why your account servers are returning 500-series response codes.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-10-08 13:53:17 -0500

Seen: 901 times

Last updated: Oct 11 '13