Title: Building Object Storage Service Ring Files Describe the issue: If you follow the suggestions in the doc here: sudo swift-ring-builder /etc/swift/account_builder_file add zX-node_ip_address:6002/device_mountpoint partition_count You will probably specify the real IP of the machine. The documentation never mentions that by default all three services (account, container, object) only listens on 127.0.0.1 address. This results in "swift list" command giving this not too helpful message: # swift list Account GET failed: http://10.34.60.70:8080/v1/AUTH_0462cfe859364e2e92a1f78309576d02?format=json 503 Internal Server Error [first 60 chars of response] <html><h1>Service Unavailable</h1><p>The server is currently /var/log/messages has this: Jun 21 16:34:34 localhost proxy-server ERROR with Account server 10.34.60.70:6002/1 re: Trying to GET /v1/AUTH_0462cfe859364e2e92a1f78309576d02: Connection refused (txn: txa9da9f28b14846ab8e9bee8e705380d2) Jun 21 16:34:34 localhost proxy-server Account GET returning 503 for [] (txn: txa9da9f28b14846ab8e9bee8e705380d2) (client_ip: 10.34.60.70) Suggestions for improvement: Either - mention that you should specify 127.0.0.1 in the ring-builder command or - tell the user to change the bind address to the real IP or 0.0.0.0 # grep bind_ip /etc/swift/*-server.conf /etc/swift/account-server.conf:bind_ip = 127.0.0.1 /etc/swift/container-server.conf:bind_ip = 127.0.0.1 /etc/swift/object-server.conf:bind_ip = 127.0.0.1 Additional information: It started working after I changed these to 0.0.0.0
Ok, ready for QA with the next doc release.