Troubleshooting Tips for OpenStack Object Storage (Swift)
We hope all goes well but we're willing to help if all doesn’t go as planned.
If your tests fail, or you can’t auth, or something doesn’t work, here are some good starting places to look for issues:
- Swift logs all events in /var/log/syslog, so that is a good first place to look for errors. Most likely these are Python tracebacks.
- Make sure all of the server processes are running. For base Swift functionality, the Proxy, Account, Container, Object and Auth servers should be running.
- If one of the servers are not running, and no errors are logged to syslog, it may be useful to try to start the server manually rather than with a script. For example:
swift-object-server /etc/swift/object-server/1.confstarts the object server.
- If there are problems not showing up in syslog, then you will likely see the traceback on startup.
You can also go to http://answers.launchpad.net/swift to ask a question, or pop on the #openstack IRC channel to talk to Swift developers. You can also add discussion items to TroubleshootingSwift/Discuss here on the wiki.
503 or 507 Errors
If you see specific problems like 503 Service Unavailable, double-check the port values to ensure they match the value in etc/swift/auth-server.conf. When adding a new account/user, the auth server calls out to the proxy server based on the default_cluster_url config file value and it should match the bind_port value. You also have to configure the port for the proxy-server.conf under the [filter:auth] section, which defaults to 11000.
Unable to increase file descriptor limit.
When you don't run all the Swift servers as root, you can expect to see "Unable to increase file descriptor limit. Running as non-root?" warnings. These errors are expected and okay to ignore.