If you find a request that seems to be related to your issue, look at the response code associated with the request.Make sure to look for a relevant timestamp. Search for the name of the workbook, view, dashboard, or data source that is related to your issue.Look for the response code and message associated with the request ID.If you find a request that seems to be related to your issue, search the vizqlserver directory for entries that include the unique request ID from the Apache logs.The Apache logs will contain a fair amount of "noise" that does not apply to issues you are experiencing. Review the Apache logs ( \httpd\access.#_#_#_#_#_#.log and \httpd\error.log) for requests that may be related to the issue you are investigating. Note: The tsm.log is less wordy than the tabadmincontroller_*.log but can provide useful, complimentary troubleshooting information. This is where you'll get most useful information. Review the TSM Administration Controller log ( \tabadmincontroller\tabadmincontroller_node-.log) to understand any configuration or deployment done by TSM from the command line, Web UI, or API, including jobs started by TSM.
You should not edit, move or delete any files directly on the server.
#Tableau read zip file archive#
Important: Use this archive when looking at the log files. For more information see Log File Snapshots (Archive Logs). Reproduce the issue you are troubleshooting so the logs capture the events related to the problem.Ĭreate an archive of the logs.For more information including impact of different log levels, see Change Logging Levels.
This is something that Tableau Support will instruct you on. For details on creating log archives, see Log File Snapshots (Archive Logs). The clean up can delete important information Support may need. Important: If there is a chance you will want to get help from Tableau Support troubleshooting an issue, be sure to create a zipped archive of your logs before cleaning them up. For more information, see Remove Unneeded Files. The range and complexity of possible issues with Tableau Server means that there is no simple process you can use to investigate all problems, but a general approach would include these steps:Ĭlean up existing log files to reduce their size. hyper files in the dataengine folder, but are never included in the zipped log archive. Extract files are stored on Tableau Server computers as. It is not saved in logs or, in the case of live connections, in separate files on Tableau Server computers. The repository also includes layout and connection information for the workbooks, but does not have any data such as passwords, actual data from the database or data shown on the view.ĭata displayed in views comes from extract files or databases, and is cached in memory.
The repository contains metadata from Tableau Server (for example, usernames, groups, projects, permissions on Tableau Server, extract refresh schedules). The tsm maintenance ziplogs command allows users to not only generate a zipped archive of log files, but also to include Tableau Server repository data if the -d option is specified. Logging at the default INFO level only gathers safe environment information. This means that if you have any sensitive information in an environment variable, it may be included in a log.
#Tableau read zip file full#
Note: When logging at the DEBUG level, full environment information is gathered when Tableau starts. Log files do not contain any sensitive customer data such as passwords, results of the queries, or data shown on the views. Log files could contain some specific data such as names of database servers, as well as their IP addresses and ports, names or IP addresses of Tableau Server computers, and URLs and names of the workbooks and views accessed by users. Tableau Server logs only contain technical information useful for troubleshooting the status of different components, actions taken by different processes, communication attempts, queries to the database (not including results), and timings of requests, for example. Taken together these log files contain detailed information about internal communication between components of Tableau Server while processing users’ requests or performing automated tasks. Singly these give detailed information on the actions of each process. Every Tableau Server process writes information about what it is doing to its own log file.
0 kommentar(er)
