AMP has several components that are updated independently:
Note this article focuses on updating AMP’s components. The game server or other application that is managed by an AMP instance is also updated separately - by managing the instance and clicking “Update” on the Metrics and Status page.
On more recent versions of AMP you can handle updating both the instance manager and AMP instances by running the following commands:
sudo su -l
getamp update
On Linux older installs you’ll need to update the AMP instance manager (ampinstmgr) via your distributions package manager:
sudo apt update
sudo apt upgrade
This will update all packages on your system. If you want to only update AMP then replace the second command with:
sudo apt upgrade ampinstmgr
sudo yum update
This will update all packages on your system. If you want to only update AMP then run:
sudo yum update ampinstmgr
Make sure all instances are fully stopped. You can do this by running ampinstmgr stopall in the command prompt
Verify no AMP process are running in Task Manager and end them if so
Download a fresh copy of the installer 872 and running the setup as an upgrade.
Due to issues with upgrades on Windows, it’s best to run the AMPSetup.msi installer a second time choosing the repair option to ensure all items are upgraded fully.
Windows and Linux
ADS can manage instances that are of a similar version, where all parts of the version number are the same except the last. For example ADS version 1.9.6.2 could manage an instance of version 1.9.6.0 or 1.9.6.4, but not of 1.9.7.0.
When you do upgrade instances, do so as the user running AMP (such as amp on Linux or AMP on Windows). On Linux, switch to the amp user by running sudo su -l amp.
You can run the following command line (on both platforms) to bulk-upgrade all of your AMP instances:
ampinstmgr upgradeall
Sometimes you may wish to only update ADS, and then use the web interface to upgrade instances via the update button on the instances (or the Update All button):
ampinstmgr upgrade ADS
On Windows, it may be necessary to reboot the system after updating AMP.
The only way currently to update the “template” configurations for Generic Module instances is via ADS. That is, you must use either:
the update button on the instance tile: Update
or
the “Update All” button at the top of the instance list: Update All
Updating from the command line, or updating from the Support and Updates tab inside the instance, won’t update the Generic Module template configurations.
Generic Module templates can be changed at any time - they don’t need to wait for a new AMP release. So it is a good idea to keep your templates and Generic Module instances up to date.
In some cases after you update a Generic Module instance configuration, you will also need to update the application that the instances manages to get all the changes applied. Manage the instance and click “Update” on the Metrics and Status page to do this.