The controller says it can't connect to the node. What should I do?

It may be that your node can't connect via its VPN link to the controller. To quickly check the status of the node and its status, you can run:


... and you should see a message similar to:

Active Directory Connectivity: OK (Not configured to use AD)
         Resolve API hostname: OK (no cluster API hostname defined to check)
          Daemons are running: OK
             Swift is working: OK
          Ping cluster API IP: OK
          VPN link is working: OK
                  System time: OK

If you have any errors in there, those errors are indications of the problem. Some of the most common reasons for things not working is that the VPN is blocked. If that is the case, you need to ensure that port 1194/UDP is allowed for outgoing traffic.


If you haven't been able to claim the node yet, the 'Daemons are running' will show 'NOT OK.' That's normal. Once the node has been successfully claimed, the daemons should be running.

My drives are not formatting and mounting. What's wrong?

  1. Make sure you don't have any entries for the storage drives in /etc/fstab. If /etc/fstab is mapping any of the storage drives for your node, the SwiftStack controller can't instruct the node to mount the drive properly.


    If you need to edit /etc/fstab to remove any entries, please do so carefully, as if you do it incorrectly, you may end up with an inoperable system.

  2. Also, if any of your storage drives have been used before in another system and include a boot sector, make sure you wipe out the boot sector before you put the drive in use in your Swift cluster.

I have some problems with my SwiftStack cluster

Enable Remote Diagnostics

If you run into any issue with your cluster, a diagnostic tarball from one or more nodes will help us look in to your issues and resolve things more quickly. The diagnostic tarball contains none of your data inside your Swift cluster. It only contains log files, configuration files, and the results of running some commands to determine system configurations which may be impacting Swift or the SwiftStack agent software.

To enable SwiftStack Support to retrieve a diagnostic tarball, you can log in to each node and issue the command:

sudo touch /etc/swiftstack-remote-diagnostics

After you've enabled SwiftStack remote diagnostics, please generate a support ticket to let our Support department know.

Disable Remote Diagnostics

You may revoke this access at any time by simply removing the above file on each node:

sudo rm /etc/swiftstack-remote-diagnostics