Dash Enterprise Administration
4.3.1
4.3.1
  • Changelog
  • Installation
    • Capacity Planning
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • Before you install
    • Dash Enterprise Single Server
      • Installation on cloud provider
      • On-premise installation on own server
      • Fully offline installation
    • Dash Enterprise Kubernetes
      • Amazon Web Services resource prerequisites
      • Google Cloud Platform resource prerequisites
      • Microsoft Azure resource prerequisites
  • Configuration
    • Set up your Server Manager
    • Run preflight checks
    • Configure basic settings
    • Authentication settings
      • Built-in local authentication
      • LDAP authentication
      • SAML authentication
    • Dash Enterprise Kubernetes additional required configuration
    • Configure optional settings
    • Add SELinux permissions to mapped directories
    • Other options and customizations
    • Using Snapshots & Backups
    • Running and logging into Dash Enterprise
    • Next steps
  • Advanced Configuration
    • General troubleshooting and problem solving
      • Dash Enterprise Kubernetes
    • Load balancer configuration
    • Reverse proxy setup instructions
    • Docker storage driver requirements and considerations
    • Import an LDAPS certificate from Active Directory into Dash Enterprise
    • Transfer Dash Enterprise to a new server
    • Sync license changes
    • Change channels for an upgrade
    • Admin panel reference
    • Configure Dash Enterprise to use common SAML IdPs
      • Active Directory Federation Services (AD FS)
      • PingFederate
      • Okta
    • Configure Dash Enterprise to use common LDAP IdPs
      • Okta
  • Upgrade
    • Prepare for the upgrade
    • Upgrade
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • After the upgrade
  • Advanced Troubleshooting
    • Dash Enterprise Architecture and Internals
    • Navigating the System
    • Navigating the Support Bundle
    • Getting Help and Reporting Issues
    • Troubleshooting Specific Issues
Powered by GitBook
On this page
  • Configure the upgraded instance
  • Run the upgraded instance
  • Monitoring the upgrade
  • Known Upgrade Issues
  • Clean up after the upgrade

Was this helpful?

  1. Upgrade

After the upgrade

PreviousDash Enterprise for KubernetesNextDash Enterprise Architecture and Internals

Last updated 2 years ago

Was this helpful?

Configure the upgraded instance

After the upgrade has been installed, browse to the Settings page of Dash Enterprise Server Manager and confirm your server is configured as desired. For more information, see .

Run the upgraded instance

After checking your configuration, click Save to start the new version.

Monitoring the upgrade

Upgrading Dash Enterprise can take anywhere between 20 minutes and two hours depending on the number of Dash apps & Workspaces on the platform and how long it takes for these apps to start. When Dash Enterprise is upgraded or restarted, all of the Dash Apps & Workspaces are rerun. To not overwhelm the server, Dash Enterprise restarts the services in batches, runs one service per CPU core. Also, when running more than four services in parallel, the Docker daemon itself has degraded performance and may further slow down this process.

Note that the UI in the Server Manager will display the application as being “Ready” before it is. This is a known bug. Instead, monitor the status of your upgrade by ssh’ing into the host and running:

docker logs -f dash

to view the status of apps being created. Check service and app restore operations:

sudo docker exec dash tail -f /var/log/services/dokku-restore

If the upgrade gets stuck and the other logs don’t show anything useful:

sudo docker exec dash tail -f /var/log/nginx/error.log

These commands do not apply to Dash Enterprise Kubernetes.

Logs are buffered so you won’t see progress as the app is built, you will only see the logs once the app has finished building.

Known Upgrade Issues

If a Dash app fails to start, then the Dash Enterprise server can fail to restart. This is a bug and will be fixed in a future release. Detect that an app has failed to start by running this command:

sudo docker exec dash tail /var/log/nginx/error.log

If you see error messages like:

2020/07/08 18:09:30 [emerg] 32215#32215: "server" directive is not allowed here in /home/dokku/bite-portal/nginx.conf:2
2020/07/08 18:09:31 [emerg] 32216#32216: "server" directive is not allowed here in /home/dokku/bite-portal/nginx.conf:2

Then you can fix this issue by running:

sudo docker exec -ti dash bash
rm -rf /home/dokku/*/nginx.conf
dokku ps:rebuild --all

Clean up after the upgrade

Once you are confident that the upgrade was successful, you may remove your backup with the following command:

sudo rm -rf /plotly.bak

There is no disadvantage associated with keeping the backup file as long as you have enough disk space.

Section 7.3: Basic settings