Upgrading Console where the database (MySQL) is hosted on a separate server


This brief article documents the steps that need to be taken in order to upgrade Aspera Console when the MySQL database is hosted in a different server than Console.

We will use the following values for example purposes in the instructions:

  • Aspera Console web application is installed on (console
  •  MySQL DB is running on (mysql
  • MySQL daemon is listening on TCP port 4406. 
  • Both servers are running on a RedHat based OS (RHEL or Centos.)


  • Product: Console
  • Operating System: Linux



1. MySQL Backup 

On the machine with the Mysql server, backup the database in case of the need for disaster recovery. The backup can be executed via a dedicated program or simply by using the mysqldump utility provided by the mysqld installation.

Note the backup can take a significant amount of space on the disk and considerable time to backup depending on the size of the database and the speed of the server, so please allow adequate time.

The command to make the backup with mysqldump is the following, where you should replace your password and desired path name to the backup:

mysqldump -u root -pROOT_PASS --all-databases > /your/path/allmysql_console.db.sql


2. Aspera Console Backup

Make a backup of the Console configuration files on the machine with the Console server.

If you have Console 1.6.0 or later, you can do this on the Console web interface. Go to the Configuration tab of the main navigation menu and click on Database. Click on Backup to create a new backup.

For previous versions of Console, make a backup of the following:

  • /opt/aspera/console/config
  • the SSL certificates on apache (see this file for their locations: /opt/aspera/common/apache/conf/extra/httpd-ssl.conf)

If space is available a tar of /opt/aspera is recommended:

tar -cvzf /SOME_PATH/console-backup-date.tgz /opt/aspera


3. Stop All Aspera Console Processes

From the command prompt on the Aspera Console Server ( as user root run the following:

asctl all:stop


4. Upgrade aspera-common rpm

Download the common and console packages from the Aspera download site using your company credentials. From the command prompt on the Aspera Console Server ( as user root issue the following command:

rpm -Uvh aspera-common-<version>.rpm 

This command may print a warning on the screen about /opt/aspera/common/apache/conf/ashttpd.conf. If the default configuration is applied this warning can be ignored. If the file has been modified for your own ssh certs they can be merged into the new ashttpd.conf after upgrading.

5. Upgrade aspera-console rpm 

From the command prompt on the Aspera Console Server ( as root user issue:

[root@console ~]# rpm -Uvh aspera-console-<version>.rpm 

This command successfully ends by asking you to run asctl console:upgrade

6. Console Upgrade Script 

As stated above, please issue this command from the prompt:

asctl console:upgrade

This will print some settings and will ask:

Are these settings correct? (y/n/x with x for exit) 

Since you need to modify the settings, type n and press ENTER.

You will then be asked about the setup:

Streamlined or detailed setup (s/d)? (current: s) 

Now type d and press ENTER.

In the following setup you can configure the Console database to be your remote MySQL database. Below is an example of the process using the values stated as a sample in the beginning of this article (please adjust as appropriate for your environment):

MySQL will run on this machine (y/n)? (current: y) n
What is the database server's host name or IP address?
What port is the remote MySQL listening on? 4406
What user should we use to connect to the database? root
What password should we use to connect to the database?
Password: ******

Enter IP address of network interface for Apache to listen on: (current:
What hostname or IP address should Apache use to identify itself (in the SSL Certificate)? (current:
What port would you like to run Apache http on? (current: 80)
What port would you like to run Apache https on? (current: 443)
Would you like to generate a self-signed SSL certificate, or install your own ([g]enerate,[c]opy,[s]kip) (current: s)?
What IP address will managed nodes use to log to the database (by default)? (current:

Please adapt your answers to your current configuration, in details:

  • You need to know the user (in this example it is root on Mysql) where Console can write on the aspera_console DB. This info can be found by looking inside the file /opt/aspera/console/config/database.yml
  • Be sure to set the database server hostname/ip address correctly

 The upgrade should run smoothly (time depends on the connection to the DB, the size of the DB and the power of the console server) and if it is correctly completed, the setup asks if Apache/Mysql/Console should be restarted.

There is no need to restart MySQL locally. The local copy of MySQL (installed by the common package) can be disabled once the upgrade is completed. To disable use the following:

asctl mysql:disable

At this point your console is upgraded.

Last Note

In some rare cases the administrator password of Console may be not retained during the upgrade. If this happens, it is always possible to reset the password or to create an alternate 'admin' user that can be used to access and reset any exist admin user's password. The command to use is the following, where you can input an existing user to change the password or input new values to create a new user:

console:admin_user user_name email user_password

Once completed the Console should be upgraded.


Aspera Support is happy to assist with this upgrade via a web meeting. Contact support to schedule your upgrade should you require assistance.

Powered by Zendesk