If that occurs, take the following actions, in order, until the problem is resolved: No action is necessary unless the cluster controller is regularly down or is down for an extended period of time.
No status available for repository or file store on this node.If Tableau Server is configured for high availability and this is the active repository, failover to the second repository occurs.Node cannot respond to failover elsewhere on the cluster.This message will only display if you have more than two nodes. The following sections provide troubleshooting recommendations for status messages that you may see. Because of this, reacting immediately to service or process alerts can be counter-productive, especially in an installation with redundant services that can handle requests while one restarts. This can take 15 to 30 minutes to complete. If a service or process stops responding or goes down, Tableau Server attempts to restart it. Note: Tableau Server is designed to be self-correcting. Permission changes related to the Run As service account may also cause multiple service failures, see Verify Folder Permissions.
TABLEAU PUBLIC SERVER DOWN UPDATE
If the password has expired, you must update it in Tableau Server, see Updating the Run As service account password. If you are seeing multiple Status: Down messages, verify that the Run As service account password has not expired. If there is additional information, a message appears below the status icon: When Tableau Server is functioning properly, processes will show as Active, Busy or Passive (Repository). For information about the Tableau Server status page and the TSM status page, see View Server Process Status. Note: The information in this article refers to the Tableau Server status page.
0 kommentar(er)
