Upgrading Shares On Demand 3.4.6 to 3.5.4


.This article covers the steps required to upgrade the software on your 3.4.6 Shares On Demand to the 3.5.4 released versions.



  1. SSH to your server, and 'sudo' to the root user.  See this article for more details.  
  2. Back up your existing Console.  (Use the console Web UI for console - backup of Shares is covered below)
  3. Make sure there are no active transfers on your server
  4. Download the latest software packages for Shares On Demand
# wget http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-ondemand-init-shod-3.4.5-103198.noarch.rpm http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-ondemand-tools-3.4.0-103198.noarch.rpm http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-shares- http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-entsrv-  http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-common- http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-console-



  1. Backup the Shares Application. Make a note of the ID of the created backup directory.
    # /opt/aspera/shares/u/setup/bin/backup /your_backup_dir
  2. Backup the Console Database
    # asctl console:backup_database
  3. Stop all Console processes
    # asctl all:stop
  4. Stop the shares nginx web server
    # /opt/aspera/shares/sbin/sv stop nginx
  5. Install the Aspera server, console and console software
    # rpm -Uvh aspera-ondemand-init-shod-3.4.5-103198.noarch.rpm
    # rpm -Uvh aspera-ondemand-tools-3.4.0-103198.noarch.rpm 
    # rpm -Uvh aspera-entsrv- 
    # rpm -Uvh aspera-common-
    # rpm -Uvh aspera-console-
  6. Run the Console Upgrade procedure
    # asctl console:upgrade
  7. Stop the apache process (it was started automatically by the Console upgrade.  With this install, we will use nginx for the web server, not Apache.
    # asctl apache:stop
  8. Install the new Shares rpm
    # rpm -Uvh aspera-shares- 
  9. Configure Shares to use the existing MySQL (that comes with Aspera Console). Find the MySQL password which is used for the production version of MySQL
    # less  /opt/aspera/console/config/database.yml
  10. Edit /opt/aspera/shares/etc/my.cnf.setup and enter in the new password. Here is an example of a working config. NOTE: We also changed localhost to
    user = root
    password = 7b3b67b4-7eh6-43a9-b6a6-485b78327bd3
    host =
    port = 4406
  11. Run the Shares 'upgrade' utility
    # /opt/aspera/shares/u/setup/bin/upgrade
  12. Change the file name of the newly created console_cluster.conf
    # mv /opt/aspera/shares/etc/nginx/conf.d/console-cluster.conf /opt/aspera/shares/etc/nginx/conf.d/console-cluster.conf.bak
  13. Restart Nginx:

    # service aspera-shares restart
  14. Your system should be upgraded.  Please login and confirm that everything is working as expected.


Powered by Zendesk