Navigating the Support Bundle

A support bundle can be generated using one of the methods in the "Navigating the System" page. Normally these should be sent to Plotly’s Customer Success team to help us investigate an issue, but it’s possible to examine the bundle yourself.

The bundle contains some default information gathered by Replicated, which is described on their site, as well as information specific to Dash Enterprise, described here.

Description

File

Startup logs from the dash container - can be useful if Dash Enterprise fails to start.

containers/logs/{dash.stdout,dash.stderr}

Startup logs from the nginx web server in the dash container - can be useful if Dash Enterprise fails to start or is inaccessible from the web after starting.

dash/var/log/services/nginx

Startup logs from the uwsgi application server in the dash container - can be useful if Dash Enterprise fails to start or if the Manager or Portal are inaccessible from the web after starting.

dash/var/log/services/uwsgi

Startup and request logs from git-http-backend in the dash container - can be useful if an https push to deploy a Dash App fails.

dash/var/log/services/git-http-backend

Last 1000 lines of each running Dash App’s logs - can be useful to troubleshoot individual apps.

dash/commands/apps_docker.log/{stdout.raw,stderr.raw}

Logs of all Dash App containers that failed to start - can be useful to troubleshoot issues with app startup.

dash/commands/apps-failed-deploys.log/{stdout.raw,stderr.raw}

Last 1000 lines of each running Redis database’s logs - can be useful to troubleshoot Redis issues.

dash/commands/apps_redis.log/{stdout.raw,stderr.raw}

Status information for each Dash App - can be useful to troubleshoot individual apps.

dash/commands/apps-report.log/{stdout.raw,stderr.raw}

The dash container’s authentication log, including failed ssh attempts - can be useful to troubleshoot ssh app pushes.

dash/commands/auth.log/{stdout.raw,stderr.raw}

Last 1000 lines of all attempts to restore stopped apps when Dash Enterprise starts - can be useful to troubleshoot app startups.

dash/commands/dokku_restore.log/{stdout.raw,stderr.raw}

Last 1000 lines of the nginx (web server) access and error logs for each app - can be useful to troubleshoot issues accessing individual apps from the web.

dash/commands/{nginx_access.log,nginx_error.log}/{stdout.raw,stderr.raw}

Last 1000 lines of Dash Enterprise’s uwsgi (application server) access and error log - can be useful to troubleshoot issues with the Portal or Manager backends or app authentication.

dash/commands/uwsgi.log/{stdout.raw,stderr.raw}

Startup logs from the dashauth (auth server) container - can be useful if Dash Enterprise fails to start.

containers/logs/{dashauth.stdout,dashauth.stderr}

Last 1000 lines of the nginx (web server) access and error logs for the auth server - can be useful to troubleshoot authentication issues.

dashauth/commands/{nginx_access_last_1000.log,nginx_error_last_1000.log}/{stdout.raw,stderr.raw}

HAProxy’s logs - can be useful to see requests made by users or to troubleshoot issues accessing Dash Enterprise or its apps via the web.

containers/logs/{haproxy.stdout,haproxy.stderr}