.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.
- SSH to your server, and 'sudo' to the root user. See this article for more details.
- Back up your existing Console. (Use the console Web UI for console - backup of Shares is covered below)
- Make sure there are no active transfers on your server
- 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-18.104.22.168140-1.x86_64.rpm http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-entsrv-22.214.171.124434-linux-64.rpm http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-common-126.96.36.199170-0.x86_64.rpm http://download.asperasoft.com/sw/ondemand/3.5.4/aws/aspera-console-188.8.131.52800-0.x86_64.rpm
- 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
- Backup the Console Database
# asctl console:backup_database
- Stop all Console processes
# asctl all:stop
- Stop the shares nginx web server
# /opt/aspera/shares/sbin/sv stop nginx
- 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-184.108.40.206434-linux-64.rpm
# rpm -Uvh aspera-common-220.127.116.11170-0.x86_64.rpm
# rpm -Uvh aspera-console-18.104.22.168800-0.x86_64.rpm
- Run the Console Upgrade procedure
# asctl console:upgrade
- 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
- Install the new Shares rpm
# rpm -Uvh aspera-shares-22.214.171.124140-1.x86_64.rpm
- 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
- 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 127.0.0.1
user = root
password = 7b3b67b4-7eh6-43a9-b6a6-485b78327bd3
host = 127.0.0.1
port = 4406
- Run the Shares 'upgrade' utility
- 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
# service aspera-shares restart
- Your system should be upgraded. Please login and confirm that everything is working as expected.