After AMP upgrade to 2.4.0.6 - MC Instance won't start - requires reactivate - reactivate fails

OS Name/Version: Linux Ubuntu (bare) 22.04.1 LTS x86_64

Product Name/Version: AMP version 2.4.0.6 (Halimede), built 29/09/2022 16:10

Problem Description:

Used the web interface to upgrade from 2.4.0.4 to 2.4.0.6 with the popup notice of update available. After update, my only instance of Minecraft wouldn’t start. AMP WebUI noted I needed to re-enter my licence key so I did in the interface. Web server became unresponsive. Rebooted linux box. On reboot ADS01 runs and webUI works but instance log notes it needs reactivation. Tried reactivation using SSH CLI as user “amp”. Reactivation failed.

CLI INTERACTION:

  CubeCoders AMP  💻amp@linux1  📁~  ampinstmgr reactivate PlayVanilla-101
[Info] AMP Instance Manager v2.4.0.6 built 29/09/2022 16:11
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
Please enter value for Licence Key
>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

[Info] Checking licence key...
[Info] Licence Type:  AMP Professional
[Info] Current Usage: 4
[Info] Reactivating instance PlayVanilla-101...
[10:56:08] [Core Info]            : Starting AMP version 2.4.0.6 (Halimede), built 29/09/2022 16:10
[10:56:08] [Core Info]            : Stream: Mainline (Release) - built by CUBECODERS/buildbot on CCL-DEV
[10:56:08] [Core Info]            : $Loading configuration from {path}...
[10:56:08] [Core Info]            : OS: Linux / x86_64
[10:56:08] [Core Info]            : CPU: Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz (4C/8T)
[10:56:08] [Core Info]            : AMP Instance ID: 88bc69d6-525e-4633-bfa2-574783c1da0d
[10:56:09] [ModuleLoader Info]    : Loaded MinecraftModule version 1.0.0.3 by CubeCoders Limited
[10:56:09] [Core Info]            : Metrics publishing is enabled at udp://localhost:12820.
[10:56:09] [ModuleLoader Info]    : Loaded FileManagerPlugin version 1.0.0.0 by CubeCoders Limited
[10:56:09] [ModuleLoader Info]    : Loaded EmailSenderPlugin version 1.0.0.0 by CubeCoders Limited
[10:56:09] [ModuleLoader Info]    : Loaded WebRequestPlugin version 1.0.0.0 by CubeCoders Limited
[10:56:09] [ModuleLoader Info]    : Loaded LocalFileBackupPlugin version 1.0.0.0 by CubeCoders Limited
[10:56:09] [ModuleLoader Info]    : Loaded CommonCorePlugin version 1.0.0.0 by CubeCoders Limited
[10:56:09] [Core Info]            : Performing activation, please wait...
[10:56:10] [Core Error]           : Activation failed: VerificationFailed
[10:56:10] [Core Info]            : Failed to activate: Verification Failed
[10:56:10] [Core Info]            : -configonly specified or activation performed. Saving settings and shutting down. This is perfectly normal.
[Info] Done.

I notice that the count keeps going up which is kind of alarming and I wonder if that will be an issue when I pass 5 as well

` [Info] Current Usage: 4

Instance, of course won’t start in this state. Here’s the log from it that looks the same always:

[11:16:04] [Core Info]            : Starting AMP version 2.4.0.6 (Halimede), built 29/09/2022 16:10
[11:16:04] [Core Info]            : Stream: Mainline (Release) - built by CUBECODERS/buildbot on CCL-DEV
[11:16:04] [Core Info]            : OS: Linux / x86_64
[11:16:04] [Core Info]            : CPU: Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz (4C/8T)
[11:16:04] [Core Info]            : AMP Instance ID: 88bc69d6-525e-4633-bfa2-574783c1da0d
[11:16:04] [ModuleLoader Info]    : Loaded MinecraftModule version 1.0.0.3 by CubeCoders Limited
[11:16:04] [Core Info]            : Metrics publishing is enabled at udp://localhost:12820.
[11:16:04] [ModuleLoader Info]    : Loaded FileManagerPlugin version 1.0.0.0 by CubeCoders Limited
[11:16:04] [ModuleLoader Info]    : Loaded EmailSenderPlugin version 1.0.0.0 by CubeCoders Limited
[11:16:04] [ModuleLoader Info]    : Loaded WebRequestPlugin version 1.0.0.0 by CubeCoders Limited
[11:16:04] [ModuleLoader Info]    : Loaded LocalFileBackupPlugin version 1.0.0.0 by CubeCoders Limited
[11:16:04] [ModuleLoader Info]    : Loaded CommonCorePlugin version 1.0.0.0 by CubeCoders Limited
[11:16:05] [FileManager Notice]   : Using keypair with fingerprint L+k4r9lr6WL1FwOJwt8Ady99ffqg8mLosysE1B3jUME=
[11:16:05] [FileManager Info]     : SFTP Server started on 0.0.0.0:2224
[11:16:05] [Core Error]           : No valid AMP licence was found. Please run `ampinstmgr reactivate PlayVanilla-101` to reactivate this instance.

Steps to reproduce:

  • Start the server
  • Try to reactivate it

Actions taken to resolve so far:

I saw some other posts where similar problems (sort of) existed and tried to upgrade without cache. Upgrade performs with no errors, but can’t reactivate instance still. Also tried to put the key into the WebUI and click the reactivate all local instances button, but that continues to lock up stuff and the WebUI won’t respond to browser requests.

Thanks for the help

Is this running in a virtual machine? If so what type?

No VM. Bare metal Linux box. No dock either.

What’s the output of:

sudo lshw -class network -short

You may need to install lshw first via apt.

H/W path         Device          Class          Description
===========================================================
/0/100/1d/0      wlp5s0          network        Wireless-AC 9260

So you have no physical wired network adapters installed or present?

I did use the build in Ethernet, then added the wireless PCIe card, then disabled the Ethernet. It’s been working for while now on wireless. Had to store the box where wires can’t get to it.

Enable the wired interface (just don’t plug it in or assign an IP etc) and reactivate.

I’ll try to figure that out. It was a trick and a half for me to disable it to stop getting boot errors, which would stop AMP/MC stuff from starting. Thanks I’ll report back afterwards.

The other thing to check is if the wireless NIC is cycling its MAC address. That’ll upset AMPs licenencing systsem.

Is there a MAC registered somewhere with AMP that I can compare that to to make that determination?

Afraid not - the MAC address is merely one of the components that AMP uses to build the machine hash, which it never actually stores.

Right, that makes sense. You’re basically telling me that the hash is different now, most likely due to the fact that the registration used the Wired and now I’m trying to re-reg with the wireless. Is it possible to clear the registration(s) and register it as new to move forward with the wireless adapter only in case I need to do this over again in future?

Well that’s what ampinstmgr reactivate is supposed to do. I’m just looking into the issue now.

Wait 20 minutes, then run ampinstmgr --nocache upgradeall then do the reactivate again :slight_smile:

Will do. And thanks… support here is fantastic BTW!

I have actually the same error. I just updated my AMP too.

Do the same thing - ampinstmgr --nocache upgradeall followed by ampinstmgr reactivateall

Drat

[13:06:53] [Core Error]           : Activation failed: VerificationFailed
[13:06:53] [Core Info]            : Failed to activate: Verification Failed

i guess try to play with the ETH adapter again?

Which release stream are you using?