AMP not running after update

Note - If you do not fill in every section below, your post won’t be answered - you must provide the steps you have followed so far and the actions you’ve already taken. Make sure to remove this notice from your post too.

OS Name/Version: Ubuntu 20.04.6 LTS

Product Name/Version: v2.4.5.4 built 26/06/2023 18:20

Problem Description: After updating with new patches, I was no longer able to access the GUI, I found amp to not be running, I did a system reboot and attempted to manually start ADS01 wish no joy.
What do I do next to try and solve this?

ampinstmgr StartAllInstances
[Info] AMP Instance Manager v2.4.5.4 built 26/06/2023 18:20
[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=, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
[Info] Waiting for AMP instance to start...
[Notice] AMP instance ADS01 is now running.
[Info] Starting Instance: 'EasyMode01'
[Info] bddfb2ffd3bfd3b2c7d4bef25ddd034be68f30917e0146897bbe9755ee09094e
[Info] Starting Instance: 'Starbound01'
[Info] 1feadd5659580d0827b2edcc5f9cc69f6db72663b8b588201475fa17d9bef2c3
[Info] Starting Instance: 'tModLoader1401'
[Info] a1df1ad83978e823e82d92d72884d4a56285e087e929795ef770435701c61700
[Info] Starting Instance: 'ATM801'
[Info] 7a1f6c8921454113283c7abc66ce343c0480c340cfe430eff2fe2ac3c8ac5e0f
[Info] Starting Instance: 'Necesse01'
[Info] 4bdf217f697b188e4aa21c9b77d3599767a1dc673eb68a063346fb1ff9bb3303
[Info] Starting Instance: 'Modded01'
[Info] 7a3f932e25ee02d2a498c3eea357b473f95e103a8cec146da99198f1741710cf
amp@localhost:~$ ampinstmgr View ADS01
[Info] AMP Instance Manager v2.4.5.4 built 26/06/2023 18:20
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Notice] ADS01 is not running.


[03:47:50] [Logger Info]          : Starting AMP version (Decadeus), built 14/07/2023 20:41
[03:47:50] [Logger Info]          : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[03:47:50] [Logger Info]          : Running in a VMware environment.
[03:47:50] [Logger Info]          : OS: Linux / x86_64
[03:47:50] [Logger Info]          : CPU: Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz (8C/8T)
[03:47:50] [Logger Info]          : RAM: 24007MB
[03:47:50] [Logger Info]          : AMP Instance ID: 74db8d08-3cb7-47a6-9f4d-4d90d195d2b7

Steps to reproduce:

  • Issue happened after I did latest patch update
sudo apt-get update
sudo apt-get upgrade -y
sudo su amp
apminstmgr upgradeall

Actions taken to resolve so far:
ampintrmgr StartAllInstances

Yes, current bug introduced with the latest patch

OK Thanks, should I just wait for Mike to release an update?

Yep, no workarounds known. I can’t even create new instances and I am not on the latest patch. Feel free to sharpen pitchforks in the meantime

Apologies for that guys - an update got re-staged after it was recalled for not working. If you run ampinstmgr upgradeall it’ll automatically downgrade itself to the correct version.

For anyone interested how to fix this. on the AMP user sudo su -l amp
run ampinstmgr upgradeall --nocache
once that’s done. run systemctl restart ampinstmgr.service

There’s no need to use --nocache any more, since the new release system was put in place it doesn’t actually do anything useful. The new system is capable of executing rollbacks if I instruct it to from my end :slight_smile:

Thank you Mike for fixing so quick :slight_smile: I hope you enjoy your weekend.

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