Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

Moving An Instance From One Server to Another

  • 1.8K Views
  • Last Post 02 November 2021
  • Topic Is Solved
dbowerman posted this 02 November 2021

I am attempting to migrate several instances from a stand alone server to a dedicated target server.

End state will have a the controller and one target will be on an unraid server in docker containers, and a Windows VM (on the same unraid server) hosting a target.

I have the Linux Target "paired" with the controller but when I attempt to attach an existing instance (on the target server), I get the below output and the instance is not created. This leads me to believe I might be missing an argument but I cant seem to find any documentation.

As a note, the instance is currently active and running on the standalone server. I don't see why this would have an effect but I figured I would mention it. Once I get this to work, I will move it permanently but I don't want to interrupt the servers uptime before I know I what it will take to move it if I can help it.

Error:

[00:29:03] [Core Error]           : Unable to set Core.AMP.PreviousVersion (Version) to 
[00:29:03] [Core Error]           :  is not a valid Version

Full Console Output:

root@49ed280bc81b:/home/amp/.ampdata/instances# ampinstmgr --AttachInstance
[Info] AMP Instance Manager v2.3 built 27/10/2021 16:40
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
Please enter value for Instance Path (The directory on disk containing the AMP instance, must contain a copy of AMPConfig.conf)
>/home/amp/.ampdata/instances/Satisfactory

[Notice] AMP Service port ranges have not been specified, using any available...
[Notice] Application Service port ranges have not been specified, using any available...
[00:29:02] [Core Info]            : Starting AMP version 2.3.0.2 (Triton), built 01/11/2021 17:22
[00:29:02] [Core Info]            : Stream: Mainline (Release) - built by CUBECODERS/buildbot on CCL-DEV
[00:29:02] [Core Info]            : Running in a Docker environment.
[00:29:02] [Core Info]            : OS: Linux / x86_64
[00:29:02] [Core Info]            : CPU: Intel(R) Core(TM) i9-10900X CPU @ 3.70GHz (10C/20T)
[00:29:02] [Core Info]            : AMP Instance ID: 5aa180dc-ab47-49e3-a8c6-2dbd73d57caa
[00:29:03] [ModuleLoader Info]    : Loaded GenericModule version 1.0.0.0 by CubeCoders Limited
[00:29:03] [Core Info]            : Metrics publishing is enabled at udp://localhost:12820.
[00:29:03] [ModuleLoader Info]    : Loaded FileManagerPlugin version 1.0.0.0 by CubeCoders Limited
[00:29:03] [ModuleLoader Info]    : Loaded EmailSenderPlugin version 1.0.0.0 by CubeCoders Limited
[00:29:03] [ModuleLoader Info]    : Loaded WebRequestPlugin version 1.0.0.0 by CubeCoders Limited
[00:29:03] [ModuleLoader Info]    : Loaded LocalFileBackupPlugin version 1.0.0.0 by CubeCoders Limited
[00:29:03] [ModuleLoader Info]    : Loaded CommonCorePlugin version 1.0.0.0 by CubeCoders Limited
[00:29:03] [ModuleLoader Info]    : GenericModule requests dependency steamcmdplugin...
[00:29:03] [ModuleLoader Info]    : Loaded steamcmdplugin version 1.0.0.0 by CubeCoders Limited
[00:29:03] [Core Error]           : Unable to set Core.AMP.PreviousVersion (Version) to 
[00:29:03] [Core Error]           :  is not a valid Version
[00:29:03] [Core Info]            : -configonly specified or activation performed. Saving settings and shutting down. This is perfectly normal.
root@49ed280bc81b:/home/amp/.ampdata/instances#

Order By: Standard | Newest | Votes
dbowerman posted this 02 November 2021

That was correct, the did need to be activated. I did notice that the .lic file was not correct.

I have the servers activated, and I can confirm that they are running and I can connect to them. However, I was unable to connect "manage" the imported instances from the controller. It was spinning on "Connecting to remote AMP instance...". I created a new instance to see if management would work for a new instance and I can confirm that it does.

After some poking around I found that the binding address for the instances was 127.0.0.1:[port] but the new instance was 0.0.0.0:[port]. I followed the instruction in the config file and ran the command ampinstmgr rebind for each instance, correcting the address to 0.0.0.0:[port] for each of the imported instances. Attempting to connect at that point gave me an authentication error. Looking at the config file again, I saw that the Login.AuthServerURL= was set to localhost. Looking at the new config file, it was pointing this value to the controller. Updated the parameter and replaced localhost with the IP of the controller. I am now able to manage the instance from the controller.

I am not sure if this is the advisable way to make this change but it is how i got it to work.

Mike posted this 02 November 2021

They probably need reactivating too. ampinstmgr reactivateall

dbowerman posted this 02 November 2021

Thank you for the reply

AMP is installed under the amp user in the docker, by default the UI in unraid connects to the root account of the docker container. Ran command as amp user and the instances were imported. After fixing the port issues, seems like they don't want to stay running. Will look more into it this afternoon.

Mike posted this 02 November 2021

You're logged in as root. Don't do that.

Install AMP normally, copy the instances over then run 'ampinstmgr repair' as the AMP user.

Close