How to Upgrade Enterprise Server to v.3.1.3 on Your AMI Host


This article is for customers who have Aspera On Demand running Enterprise Server v3.0 or v3.1.0 and would like to upgrade to Enterprise Server v3.1.1.

NOTE: If you don't know your Enterprise Server version, you can SSH into your AMI host from a Terminal or a Command Prompt and run ascp -A to find out the version information.

        # ssh -i [customer's pem] -p 33001 [ec2-user]@[ec2 host IP]
# ascp -A


Upgrade Procedure

(1) Connect to your AMI host from a Terminal/Command Prompt via SSH as root


        # ssh -i [customer's pem] -p 33001 [ec2-user]@[ec2 host IP]
# sudo su -

   NOTE: make sure the permission of the key is set to 400.


(2) Download the ES 3.1.1 package from our website

Use your customer login to download the package.  If you don't know your customer login and password, please contact Aspera Support at to obtain your login credentials.

# wget

(3) Manually stop asperanoded, asperatrapd and asperalee

       # /etc/init.d/asperanoded stop
      # /etc/init.d/asperatrapd stop
      # /etc/init.d/asperalee stop

    Then check to make sure they are stopped:

    # ps aux | grep aspera

    You should not see any of these processes running:

    If they are still running, kill the processes by running

      # kill -9 [PID of the process]


(4) Install Enterprise Server v.3.1.1

     # rpm --nodeps -Uvh aspera-entsrv-

(5) Restore server keys

 Identify the saved keys aspera_server_key.pem.rpmsave and aspera_server_cert.pem.rpmsave, copy and rename them to aspera_server_key.pem and aspera_server_cert.pem

       # cd /opt/aspera/etc 
# cp aspera_server_key.pem.rpmsave  aspera_server_key.pem
# cp aspera_server_cert.pem.rpmsave aspera_server_cert.pem


(6) Restart asperanode


       # /etc/init.d/asperanoded restart


(7) Enable trapd (which is disabled automatically by the upgrade) 

        # /opt/aspera/bin/  enable 
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk