Was this page helpful?
Yes No
Tableau Help > Tableau Server for Windows Help > 
Manage Server > Troubleshooting > Troubleshoot Server Processes

Troubleshoot Server Processes

When Tableau Server is functioning properly, processes will show as Active, Busy or Passive (Repository). If there is additional information, a message appears below the status icon:

Possible status indicators are:

The following sections provide troubleshooting recommendations for status messages that you may see.

Cluster Controller

This message will only display if you have more than two nodes.

Status: Down; Message: "Node degraded"

One or more of the following are true:

  • Repository on the node is stopped.
  • Node cannot respond to failover elsewhere on the cluster.
  • If Tableau Server is configured for high availability and this is the active repository, failover to the second repository occurs.
  • No status available for repository or file store on this node.

No action is necessary unless the cluster controller is regularly down or is down for an extended period of time.

If that occurs, take the following actions, in order, until the problem is resolved:

  1. Check disk space. If disk space is limited, save the log files (use tabadmin ziplogs) in case you need them for Support, then remove unnecessary files (tabadmin cleanup).
  2. In Windows Task Manager, stop the clustercontroller.exe process tree and let it restart automatically.
  3. Restart Tableau Server.
  4. Clean up the coordination service (ZooKeeper) files: Stop the cluster (tabadmin stop), clean up files (tabadmin cleanup --reset-coordination), and then start the cluster (tabadmin start).
  5. If Cluster Controller continues to show as down, save the log files (tabadmin ziplogs) and contact Support.

File Store

File Store status only reflects the state of the file store when the page was loaded.

An active status () with no message indicates that no extracts were being synchronized when the page was loaded. It is possible that the recurring "catch-all" job is running and synchronizing extracts.

Staus: Busy; Message: "Synchronizing"

"Synchronizing," usually indicates that extracts were being synchronized across file store nodes when the page was loaded.

However, the "synchronizing" message is also returned following installation (both single-node and multi-node). After Tableau initializes the status should disappear within 15 or 20 minutes.

Status: Down; "Data Extracts unavailable"

On a single-node installation: "Data Extracts unavailable" indicates that existing extracts may be available but publish/refresh will fail. On multi-node installations, this message indicates that extract synchronization will fail for this node.

No action is necessary unless the file store is regularly down or is down for an extended period of time.

If that occurs, take the following actions, in order, until the problem is resolved:

  1. Check disk space. If disk space is limited, save the log files (tabadmin ziplogs) in case you need them for Support, and then remove unnecessary files (tabadmin cleanup).
  2. Stop the filestore.exe process using Windows Task Manager and let it restart automatically.
  3. Restart Tableau Server.
  4. Clean up the coordination service (ZooKeeper) files: Stop the cluster (tabadmin stop), clean up files (tabadmin cleanup --reset-coordination), and then start the cluster (tabadmin start).
  5. If the file store continues to be down, save the log files (tabadmin ziplogs) and contact Support.

Status: Busy; "Decommissioning"

This message indicates that this File Store is in read-only mode and that any unique files on this node are being replicated to other file store nodes.

To remove this node, wait until the status message changes to "Ready for removal".

Status: Active; "Ready for removal"

This message indicates that the File store is in read-only mode.

You can safely stop (tabadmin stop) the cluster and remove Data Engine and/or File Store processes, or remove entire node.

Status: Active; "Decommission failed"

This message indicates that the File store is in read-only mode, and that at least one unique file failed to replicate to another file store node.

To resolve a failed decommissioning:

  1. Run the tabadmin decommission command again.
  2. Check disk space on other file store nodes. Decommissioning will fail if another file store node does not have enough space to store all the extracts.
  3. Check the tabadmin.log file on the primary node and workers for errors.
  4. Stop Tableau Server (tabadmin stop) and then try running the tabadmin decommission command again.
  5. Put the file store node back into read/write mode (tabadmin recommission), collect logs, and then contact Support.
  6. With Support: copy and merge extracts directory from this file store node to the same directory on another file store node.

Repository

Staus: Busy; Message: "Setting up"

The "Setting up" message indicates one or more of the following states:

  • Passive repository is being synchronized with active repository.
  • Repository is not ready to handle failover.
  • Repository may have gotten more than two minutes behind active repository and is being setup again (this is faster than waiting for a sync).
  • Failover occured and this former active repository is rejoining the cluster.

Wait until the repository status message changes to "Passive".

If this message does not appear, or if it is taking a long time:

  1. Check disk space and free space if possible.
  2. Check cluster controller logs for errors.
  3. Restart node.

Staus: Busy; Message: "Synchronizing"

Repository is synchronizing, for example after a failover.

Staus: Down; Message: n/a

When the Repository shows a status of down and there is no message, then the Repository is in one of the following states:

  • If the installation is configured for high availability, failover of the repository occurred.
  • Processes are restarting with updated database connection configurations after failover.
  • If another active repository is not available, Tableau Server is down.

Take these actions in the given order until the problem is resolved:

  1. Wait several minutes for cluster controller to attempt to restart.
  2. Restart Tableau Server (tabadmin restart).
  3. Check disk space to make sure there is free space. Collect logs (tabadmin ziplogs) in case you need them for Support, and then cleanup files (tabadmin cleanup).
  4. Restart Tableau Server.
  5. Stop Tableau Server, collect logs and cleanup coordination service files (tabadmin cleanup --reset-coordination)
  6. Start Tableau Server.
  7. Collect logs (tabadmin ziplogs) and contact Support.

Staus: Passive; Message: n/a

A passive status with no message indicates that the node is working as intended and that it is ready for failover if needed.

VizQL Server

Staus: Unlicensed; Message: n/a

For information about unlicensed status for a VizQL Server process, see Handle an Unlicensed VizQL Server Process.