Parent topic: Upgrading Orchestrator
Single Node Installation / Upgrading Orchestrator

Upgrading a Single Node from Orchestrator 2.3.5+ to the Current Release

The procedure in this topic is only for those upgrading from Orchestrator 2.3.5 + to the current release.

  1. (Preliminary step) Follow the backup steps described in Upgrading: Requirements to ensure easy rollback in case there are any issues.
    After upgrading, previously installed releases of Aspera Orchestrator are still present in /opt/aspera and can be used for rollback operations. For example:
    /opt/aspera/Orchestrator_version/
  2. Download the installation files for the new release.
    1. Go to the Aspera downloads website, http://downloads.asperasoft.com/en/downloads/27.
    2. Using your login credentials, download both installers:
      • version - Linux RPM x86_64 (Aspera Orchestrator)
      • versionCom - Linux RPM x86_64 (Aspera Common Components)
      After download, the installers appear with the following formats (aspera-common is the Aspera Common Components):
      aspera-orchestrator-version-0.x86_64.rpm
aspera-common-version-0.x86_64.rpm
    3. Save the installers to the machine where Orchestrator is to be upgraded.
  3. Stop Orchestrator services or all Aspera services.
    CAUTION:
    To avoid any issues with installation, be sure to run the asctl command applicable to your current setup:
    • If the version of the Aspera Common Components ("Common") installed with your current Orchestrator setup is the same as the Common required to install the new version of Orchestrator (for example, Orchestrator v. 2.7.0, v. 2.7.1 and v. 3.0.1 all use Common 1.2.19), run the following command:
      # asctl orchestrator:stop
    • If the version of Common installed with your current Orchestrator setup is a lower version than the Common required to install the new version of Orchestrator, run the following command:
      # asctl all:stop
stopping manager, engine and workers..
stopped...

Orchestrator Status:
  -> Orchestrator Manager NOT running
  -> Orchestrator Engine NOT running
  -> Mongrel serving orchestrator on port 3000 is NOT running
  -> Mongrel serving orchestrator on port 3001 is NOT running
  -> Mongrel serving orchestrator on port 3002 is NOT running
  -> Orchestrator Monitor NOT running
  -> Asynchronous Worker Process 0 is NOT running
  -> Asynchronous Worker Process 1 is NOT running
  -> Synchronous Worker Process 2 is NOT running
  -> Synchronous Worker Process 3 is NOT running
  -> Synchronous Worker Process 4 is NOT running
  -> Synchronous Worker Process 5 is NOT running
MySQL: Stop... done
Apache: Stop... done
  4. Upgrade the Aspera Common Components, if needed. 
    # rpm -Uvh aspera-common-version-0.x86_64.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:aspera-common-version-0    ################################# [ 50%]
Cleaning up / removing...
   2:aspera-common-version-0    ################################# [100%]
  5. Upgrade Orchestrator. 
    # rpm -Uvh aspera-orchestrator-version-0.x86_64.rpm 
Preparing... ########################################### [100%]
   1:aspera-orchestrator    ########################################### [100%]
  6. (High availability upgrade, only) If you are upgrading in a high availability (HA) environment that uses ACM software, turn off the MySQL, Apache, and Orchestrator services with the chkconfig command.
    This step is necessary for ACM to function properly.
    # chkconfig aspera_mysqld off
# chkconfig aspera_httpd off
# chkconfig AsperaOrchestrator off
  7. Complete the upgrade by setting up Orchestrator. 
    # asctl orchestrator:setup
  8. A Ruby version selection prompt appears: 
    Orchestrator
  Use Ruby 2.3.0 (y/n)? (current: y)
    Enter "y" to use Ruby 2.3.0 in the installation.
    CAUTION:
    When upgrading from an older version of Orchestrator (which runs Ruby 1.8.7) to Orchestrator 3.0.1, if you choose "y" for "Use Ruby 2.3.0 (y/n)?" and you have work orders with a current status of "In Progress", those work orders will fail after upgrade and you will need to restart any asynchronous steps. (This issue is caused by the older and newer Rails versions handling ActiveRecord in different ways).

    If for any reason it will not be possible to restart the asynchronous steps after upgrade, you must select "n" for"Use Ruby 2.3.0 (y/n)?" and continue to use Ruby 1.8.7 with Orchestrator 3.0.1.

    Note: If you select "n" at this prompt, Orchestrator will use Ruby 1.8.7 for the installation. You will still have access to all Orchestrator features; however, you will not experience the improved engine performance supported by Ruby 2.3.0.
  9. Check the following directory if there are capsules present in the folder. 
    /opt/aspera/var/config/orchestrator/capsules/

    Review the current release notes and remove any capsules that are no longer needed. Contact Technical Support for any questions regarding the handling of capsules after an upgrade.

  10. Restart Orchestrator and all Aspera services. 
    # asctl all:restart
Parent topic: Upgrading Orchestrator