Instances shut down arbitrarily

OS Name/Version: Debian 11

Product Name/Version: v2.4.3, built 14/03/2023 21:50

Problem Description:
The game server instances automatically shut down every few days. In the console logs there is an error message that the AMP installation does not have a valid license and other error messages (see screenshots). I have already tried to reactivate the license locally in the panel.

Check the logs from when the shutdown occurs rather than after the restart.

Oops right. I have overlooked that. So now you can see all the info.

Hello, I have the same problem as mentioned above and I’ve been waiting for a solution for 4 days. is there a known solution?

Same again, have you checked the logs? You need to look at the time the shutdown occurred.

Hello there, I am the owner of that server and somehow AMP creates several instances (shadow instances). Actually only 1 instance is active and installed “normally” but if I check my current activations it shows 9 activations in total. Amp activations

Looking inside the logs there seems to be a docker issue after updating and reconnectiong to the same old container.

After I logged into the panel today I was greeted by an offline Instance. Trying to start this instance results in the following Error:

Unable to complete task
This Task could not be completed: Starting Instance - Starting Nemeseos (Nemeseos01)…- State: 3. Startup failure: Docker returned error code 125

After looking inside the logs produced today and yesterday I found the following:

[09:33:00] [Core Info]            : Starting AMP version (Decadeus), built 14/03/2023 21:50
[09:33:00] [Core Info]            : Stream: Mainline (Release) - built by CUBECODERS/buildbot on CCL-DEV
[09:33:00] [Logger Info]          : Deleting 7 old log files...
[09:33:00] [Core Warning]         : Current time zone is set to CET - It is recommended you switch to UTC+0 to avoid time-zone related issues
[09:33:00] [Core Info]            : OS: Linux / x86_64
[09:33:00] [Core Info]            : CPU: 11th Gen Intel(R) Core(TM) i5-11600 @ 2.80GHz (6C/12T)
[09:33:00] [Core Info]            : RAM: 64131MB
[09:33:00] [Core Info]            : AMP Instance ID: cf31xxx0-bxx8-4fb9-xxxx-849xxxxxxe3
[09:33:00] [ModuleLoader Info]    : Loaded ADSModule version by CubeCoders Limited
[09:33:00] [ModuleLoader Info]    : Loaded FileManagerPlugin version by CubeCoders Limited
[09:33:00] [ModuleLoader Info]    : Loaded EmailSenderPlugin version by CubeCoders Limited
[09:33:00] [ModuleLoader Info]    : Loaded WebRequestPlugin version by CubeCoders Limited
[09:33:00] [ModuleLoader Info]    : Loaded LocalFileBackupPlugin version by CubeCoders Limited
[09:33:00] [ModuleLoader Info]    : Loaded CommonCorePlugin version by CubeCoders Limited
[09:33:00] [ModuleLoader Info]    : ADSModule requests dependency InstanceManagerPlugin...
[09:33:00] [ModuleLoader Info]    : Loaded InstanceManagerPlugin version by CubeCoders Limited
[09:33:00] [ModuleLoader Info]    : ADSModule requests dependency SystemUserManagerPlugin...
[09:33:00] [ModuleLoader Info]    : Loaded SystemUserManagerPlugin version by CubeCoders Limited
[09:33:00] [ModuleLoader Info]    : Loaded steamcmdplugin version by CubeCoders Limited
[09:33:00] [Core Info]            : Metrics server started OK on port 12820
[09:33:00] [ADS Info]             : ADS startup complete in 118ms
[09:33:00] [ADS Info]             : Updating remote source CubeCoders/AMPTemplates
[09:33:00] [ADS Info]             : Updating existing remote source
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:   git config pull.rebase false  # merge (the default strategy)
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
[09:33:00] [FileManager Notice]   : Using keypair with fingerprint cpxxxxxxxj/zznxxxxEK/g4ICxxxxxtyH/xxxPu/dxx=
[09:33:01] [FileManager Info]     : SFTP Server started on
[09:33:01] [WebServer Info]       : Websockets are enabled.
[09:33:01] [WebServer Info]       : Webserver started on
[09:33:01] [Logger Warning]       : RouterTimer@10Hz with 2 jobs started
[09:33:01] [Core Info]            : Checking for AMP updates...
[09:33:01] [Core Info]            : AMP is up-to-date.
   89f8caf..02a5dac  main       -> origin/main
Updating 89f8caf..02a5dac
 v-risingconfig.json | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
[09:33:07] [InstanceManager Info] : docker: Error response from daemon: Conflict. The container name "/AMP_Nemeseos01" is already in use by container "a1e18fa36200fc00bff619b1e30a8476193058875c2f8898fcfa53029d305550". You have to remove (or rename) that container to be able to reuse that name.
[09:33:07] [InstanceManager Info] : See 'docker run --help'.
[10:03:00] [Core Info]            : Checking for AMP updates...
[10:03:00] [Core Info]            : AMP is up-to-date.

If you need further information please type it below. Ochin or myself will be looking into it.

With kind regards

Jens Humke

This should be a separate thread, please don’t tack different issues onto existing threads.

It is the same issue unless you consider the activation issue as something different.

Activation issues aren’t related to instance shutdowns (unless the log specifically says its a licence issue)

Well that’s something we try to figure out. While going through the logs I saw an activation issue as well and so I believed it was relevant too.

[Core Error]           : No valid AMP licence was found. Please open a shell as the 'amp' user and run ampinstmgr reactivate Nemeseos01 to reactivate this instance.

That means the hardware profile changed, please make a new thread with all the normal information.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.