The OpenStack Object Storage service, also called Swift, provides object-based storage space for storing files. Unlike the block store, the object store is accessed using the API, and not the file system directly.

The Object Storage service writes its log files in /var/log/syslog (or messages on some distros). Logging can be customized by editing the log_name, log_facility, and log_level  parameters in the object server configuration files.

To begin troubleshooting any issues with the Object Storage service, you must first ensure that the required services are running. 

The following processes should be running on the node where Swift is installed:

• Proxy server
• Account  server
• Container server
• Object server
• Auth server

If any of the preceding processes are not running, you must look at the syslog to get hints about the errors. If no errors are logged to syslog, you can attempt to start the server manually from the command line as follows:

# swift-object-server /etc/swift/object-server/1.conf

The Swift proxy server is the endpoint that listens for Swift API requests. To check if this process is running properly, simply execute the swift list command. If this command returns an error, there is a problem with the proxy server process:

# swift list

In case of errors, you can check the syslog to get clues about the root cause.
You can then attempt to start the process manually by invoking the following command:

# swift-init main start