Node Specific Commands

Sometimes it's helpful to login to a SwiftStack node and investigate utilizing commands directly on the node


/usr/bin/ssdiag and /usr/bin/ssdiagtarball are two commands that can be helpful for troubleshooting the most common error scenarios on a SwiftStack node.

The Troubleshooting FAQ entry has more details on using ssdiag.

Swift Commands

All of the Swift programs and commands are located in /opt/ss/bin. In particular, swift-init can be used to manually stop or start a specific Swift process for debugging purposes.

Startup Scripts

A number of upstart scripts exist in /etc/init, including:

  • ssreload
  • ssstop
  • ssstart
  • ssremount

You can stop the ssnoded monitoring process with sudo stop ssnoded, which will then allow for manual override of specific Swift processes. To stop all services, using sudo start ssstop can be helpful.

Node Logs

Swift processes will log to /var/log/swift/all.log, which can be useful in viewing specific transaction information and troubleshooting client failures with the Swift cluster.

SwiftStack processes will log into various log files in /var/log/ss*. Being able to read those files can be helpful in troubleshooting errors that may occur within the cluster.


SwiftStack Node Agent, Swift or Gateway code may be fully uninstalled by running uninstall-swiftstack-node as the superuser. While this can be done at any time, it is recommended to delete the Node in the SwiftStack Controller GUI first, then uninstall the Node's software.