Unable to start ADS after upgrade

[Christian_M]

Hi after trying to update to 2.4.5.4 ADS will not start anymore.

OS Name/Version: Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-76-generic x86_64)

Product Name/Version: v2.4.5.4

Problem Description:

 CubeCoders AMP  💻amp@game  📁~  ampinstmgr start ADS
[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=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
[Info] Waiting for AMP instance to start...
[Error] Failed to start AMP. Exit code was 0
[Info] This instance failed to start. Run 'ampinstmgr LastLog ADS01' to view it's most recent log.
  CubeCoders AMP  💻amp@game  📁~  

[23:29:52] [Logger Info]          : Starting AMP version 2.4.5.4 (Decadeus), built 14/07/2023 20:41
[23:29:52] [Logger Info]          : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[23:29:52] [Logger Info]          : Running in a QEMU KVM environment.
[23:29:52] [Logger Info]          : OS: Linux / x86_64
[23:29:52] [Logger Info]          : CPU: 13th Gen Intel(R) Core(TM) i5-13600K (4C/4T)
[23:29:52] [Logger Info]          : RAM: 29367MB
[23:29:52] [Logger Info]          : AMP Instance ID: e2f585f7-04c4-4936-97c3-57e870d68827

  CubeCoders AMP  💻amp@game  📁~  ampinstmgr status
[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
Instance Name      │ Friendly Name    │ Module     │ IP              │ Port  │ Up
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼───
ADS01              │ ADS              │ ADS        │ 0.0.0.0         │ 8080  │  

 CubeCoders AMP  💻amp@game  📁~  systemctl status ampinstmgr
● ampinstmgr.service - AMP Instance Manager
     Loaded: loaded (/etc/systemd/system/ampinstmgr.service; enabled; vendor preset: enabled)
     Active: active (exited) since Fri 2023-07-14 23:27:36 UTC; 5min ago
       Docs: https://github.com/CubeCoders/AMP/wiki/AMP-systemd-script-(Linux)
    Process: 1649 ExecStart=/opt/cubecoders/amp/ampinstmgr startboot true (code=exited, status=0/SUCCESS)
   Main PID: 1649 (code=exited, status=0/SUCCESS)
        CPU: 1.932s

Jul 14 23:27:21 game sudo[1675]: pam_unix(sudo:auth): auth could not identify password for [amp]
Jul 14 23:27:26 game ampinstmgr[1649]: [Error] Failed to start AMP. Exit code was 0
Jul 14 23:27:26 game ampinstmgr[1649]: [Info] Waiting for AMP instance to start...
Jul 14 23:27:27 game sudo[1708]: pam_unix(sudo:auth): conversation failed
Jul 14 23:27:27 game sudo[1708]: pam_unix(sudo:auth): auth could not identify password for [amp]
Jul 14 23:27:31 game ampinstmgr[1649]: [Error] Failed to start AMP. Exit code was 0
Jul 14 23:27:31 game ampinstmgr[1649]: [Info] Waiting for AMP instance to start...
Jul 14 23:27:32 game sudo[1740]: pam_unix(sudo:auth): conversation failed
Jul 14 23:27:32 game sudo[1740]: pam_unix(sudo:auth): auth could not identify password for [amp]
Jul 14 23:27:36 game ampinstmgr[1649]: [Error] Failed to start AMP. Exit code was 0

Thats all logs i could find

Steps to reproduce:

Ran update to 2.4.5.4 from the gui

Actions taken to resolve so far:

System reboot
ampinstmgr --nocache upgradeall

[Eli_Gulley]

I have the exact same issue, and have tried the same command. Every time I start my ADS instance, it says its running, but when I use:

ampinstmgr view ADS01

My console tells me it isn’t running at all.

[Poor_Quality_Edits]

Almost all of us are having the issue, I would just wait until it gets fixed.

[Wardude202]

Can confirm same issue.
Any rough idea how long they usually take to fix this kind of issue?

[Greelan]

Given this is so fundamental, I’d expect a hotfix in a few hours when Mike wakes up

[reginald_chan]

was this upgrade due to the patch that got released

[Mike]

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.

[Wardude202]

i just did this, but i still seem to have the same issue @Mike

ran ampinstmgr upgradeall

also ran systemctl restart ampinstmgr.service
Should i be doing anything else?
Also good morning, Lovely way to wake up to your Saturday morning :')

---

As i am a new user here i can only reply 3 times here @Mike so peep this comment

i have added --nocache to see what it does.
[Info] Downloading AMP from https://downloads.cubecoders.com/AMP/Mainline/20230714.3/AMP_x86_64.zip...

Seems like .3 patch still.

---

RAN IT ONCE AGAIN…
and i see a .2
[Info] Downloading AMP from https://downloads.cubecoders.com/AMP/Mainline/20230714.2/AMP_x86_64.zip...

We’re up and running! @Mike Shout out to you / the other devs.
I get versioning shit can be a pain <3

FIX:

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

[Mike]

Humour me and run it again, it should be rolling back to the .2 patch rather than .3 - might have taken for the cache of the old manifest to be dropped.

[Martin_Dunn]

Still pulling .3 for me whatever I do.

[Zebgames]

I’m having the same issue. I’ve run ampinstmgr upgradeall and each time it installs .3 not .2

[Mike]

Can you both try it again @Martin_Dunn and @Zebgames ? Just flushed the upstream caches.

[reginald_chan]

ampinstmgr --nocache upgradeall might help

[reginald_chan]

i too also getting the .3 upgrade and not willing to upgrade again and then break it again

[Mike]

–nocache doesn’t do anything useful since the new release system got put in place.

The .3 update has been recalled so it shouldn’t be showing, if you restart you’ll get the correct version info.

[Zebgames]

Hey Mike, et All,

After repeated tries after flushing, it looks like about 30 minutes had to pass for the flushing to take effect. I have “upgraded” back down to .2. My instances are now starting again.

Thanks for the quick turnaround on a Sunday.

[Martin_Dunn]

Now back on .2 - Thankyou!