ADS01 doesn't start after update 2.4.8.0

Technical Support Installation Support
1

OS Name/Version: Windows 10 / 19045.3930

Product Name/Version: ADS91 / 2.4.8.0

Problem Description: ADS01 doesn’t start after update 2.4.8.0

Steps to reproduce:

  • Step 1

ampinstmgr --nocache upgradeall

Actions taken to resolve so far:

Restarted the computer.

image
image737×75 40.2 KB

1 Like
2

I’m having the same issue. Running “ampinstmgr upgradeall” errors out with a code 0.

Running “ampinstmgr upgrade ads” says it’s completed successfully, but checking if ADS is running shows it’s not.

3

I am getting the same thing. I clicked upgrade on the webapp and was waiting for it to finish upgrading, but after 15 minutes I was still getting no response so I rebooted and now im stuck in this situation. Im pulling my hair out trying to get it to start. Is there a way to revert to an older version?

EDIT: LastLog also only shows this and nothing else:

[03:53:41] [Core Info]            : Starting AMP version 2.4.8.0 (Decadeus), built 25/01/2024 01:11
[03:53:41] [Core Info]            : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[03:53:41] [Logger Info]          : Deleting 1 old log files...
[03:53:41] [Logger Info]          : Purging old audit logs (this may take a moment)...
[03:53:41] [Core Info]            : Running in a Proxmox LXC Container environment.
[03:53:41] [Core Info]            : OS: Linux / x86_64
[03:53:41] [Core Info]            : CPU: Intel(R) Core(TM) i9-10900F CPU @ 2.80GHz (10C/20T)
[03:53:41] [Core Info]            : RAM: 32768MB
[03:53:41] [Core Info]            : AMP Instance ID: 05bc2ffb-40d7-47df-8506-07c58da9d5d1
4

Hi, have you find any solution?
I still can’t get it to work…

5

No I havent found a solution yet. I did figure out that my Palworld server still works, however my Minecraft server doesnt. I think im just gonna wait for a patch or figure out how to revert to the previous version

6

Same for me. Can’t get ADS01 to start after the upgrade. All instances/containers that have been set up before seem to work, but ADS01 won’t start and the logs seem to be okay:

[00:00:00] [Logger Info]          : Rollover from previous log file: AMP_Logs/AMPLOG 2024-01-25 00-00-00.log
[00:16:00] [Core Info]            : Checking for AMP updates...
[00:16:00] [Core Info]            : A new update is available!
[06:16:00] [Core Info]            : Checking for AMP updates...
[06:16:00] [Core Info]            : A new update is available!
[12:16:00] [Core Info]            : Checking for AMP updates...
[12:16:00] [Core Info]            : A new update is available!
[16:51:33] [InstanceManager:gameuser Info] : Downloading AMP from https://downloads.cubecoders.com/AMP/Mainline/20240125.2/AMP_x86_64.zip...
[16:51:37] [InstanceManager:gameuser Info] : Complete
[16:51:49] [InstanceManager:gameuser Info] : fbd0b201ea709917a14c1f836649e96bc7470f7a3ff23a7b990bd6144c8ff1fe
[16:52:03] [InstanceManager:gameuser Info] : c7d76fef3b70fd331e94ba3bb0eb4471c5a27af2aed32be326dc2a4bc49f348a
[16:52:51] [Core:gameuser Info]   : Stop requested: AMP update requested via API
[16:52:51] [Core Notice]          : AMP shutdown requested.
[16:52:51] [Core Notice]          : Stopping Application...
[16:52:56] [Core Notice]          : Stopping Web Server...
[16:52:56] [Webserver Info]       : Web server shutdown.
[16:52:56] [Core Notice]          : Goodbye!
Rest in peace - Stephen Hawking 1942-2018
I miss you Casper. <3

ampinstmgr -i ADS01

[Info] AMP Instance Manager v2.4.7 built 31/12/2023 22:56
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Instance ID        │ 68abecd9-7eb2-4df9-8574-234effca04cf
Module             │ ADS
Instance Name      │ ADS01
Friendly Name      │ ADS
URL                │ http://127.0.0.1:8080/
Running            │ No
Runs in Container  │ No
Runs as Shared     │ No
Start on Boot      │ Yes
AMP Version        │ 2.4.8.0
Release Stream     │ Mainline
Data Path          │ /home/amp/.ampdata/instances/ADS01

ampinstmgr -s ADS01

[Info] AMP Instance Manager v2.4.7 built 31/12/2023 22:56
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info] Starting Instance: 'ADS01'
Can't find custom attr constructor image: /opt/cubecoders/amp/plugins/ADSModule.dll mtoken: 0x0a00001e due to: Could not load file or assembly 'SQLite-net, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
[Info] Waiting for AMP instance to start...
[Notice] AMP instance ADS01 is now running.
[Info] You can browse to this instance at http://XXX.XXX.XXX.XXX:8080/
[Info] Instance started in new session. Run 'ampinstmgr View ADS01' to view this instances live output.

Maybe the

Can’t find custom attr constructor image: /opt/cubecoders/amp/plugins/ADSModule.dll mtoken: 0x0a00001e due to: Could not load file or assembly ‘SQLite-net, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of its dependencies.

line is a hint, not sure if the dll is really relevant to a linux system.
However, as I was forced to the update to finish the setup of a new Minecraft Instance and it seems I can’t roll back I’m pretty frustrated now.
Got to tell the guys that the sessions are cancelled for the weekend.

7

From what I ready this is not important, and is not related to the issue. I get almost identical results to what you’re getting when typing those commands. I would really like to get this fixed so that I can fix my Minecraft server.

8

Hi, I have reverted back to the last version ( 20240109.1 ) and it seems to work again…

9

Good to hear, how did you revert to the last version?

10

Hey @Manuel_Guyot, sounds great! I would also like to know how to revert to the previous version. IS that done with the version zips stored on the server?

11

I managed to get the Instances up again ( can connect and play the Minecraft server ) but can’t Manage the Instances.

I did like this for Windows:

  1. First I made a copy of the folder AMPDatastore to have a backup if things goes wrong.
  2. In the Folder \AMPDatastore\Versions\Mainline I created a new Folder ( Backup ) and moved all the Folders of the versions inside it.
  3. I Copied back the previous version ( 20240109.1 ) inside the \AMPDatastore\Versions\Mainline Folder and renamed the Folder as 20240125.2.
  4. I ran “ampinstmgr upgradeall” which will be run from local drive.
  5. I verified that the Service is up and running in Windows ( AMP-ADS01 ), if not, I started it.
    After that, I could connect again and get into the Minecraft servers.

I hope this was an understandable explanation.

12

Unfortunately this didn’t work for me. I made a backup before trying this though, so nothing’s been permanently alterered

13

That was sad, I did it several times to try, and got it to work every time.
But I hope a patch will son come to fix that.

14

I can start single instances of the gameservers with ampinstmgr -s INSTANCENAME.
But still did not find a way to start ADS01 which is the Web-UI to configure existing instances or generate new ones. Still can’t find helpful logs anywhere on the System.

15

Have you looked in the system that the instance is started?

image

16

ADS01 is not running and won’t start. There is no real error message and the last log entries are from the update. There are no newer events that may give a hint to what is going wrong.
You can’t even check the docker logs, as the container won’t start.

17

Same problem for my controller with Debian Linux. Targets upgraded without problems.

18

Got the UI back (at least it works with advanced license):
Switch to development stream
ampinstmgr --ChangeInstanceStream ADS01 Development true
Start ADS01
ampinstmgr -s ADS01

I don’t know if this also works in the preview stream, development seems to work so far. Logs are looking good, UI is working as expected.

19

This worked for me! Thanks for sharing this workaround.

1 Like
20

Good to know that also worked for you @V3rmVick
Did you also switch to the development stream?
I try to figure out whether preview would also work.