Update Failure with Application Deployment - Update failed with strange behaviour

System Information

Field Value
Operating System Windows - Windows 10 Enterprise on x86_64
Product AMPService ‘Callisto’ v2.5.1.4 (Mainline)
Virtualization None
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Problem Description

Issue

I tried to update the AMP instance to 2.5.1.6 however ADS01 is not updating.
Right after my first attempts to update it, the server went unresponsive, after restarting the windows host, the instances was disappeared. I have to run ampinstmgr repair to get it back. right after that ADS01 changed from port 8080 to 8083 while Palworld change to 8082.
Currently running version 2.5.1.4 - 20240814.2
An AMP Update is Available: 2.5.1.6 - 20240814.2

Reproduction Steps

  • Stop Palworld instances (Only instance)
  • Click Updates > Upgrade this instance
  • Server went unresponsive
  • Rebooted the Windows Host
  • Palworld Instance Disappeared, AMP instance manager show initial config page
  • run ampinstmgr repair, ampinstmgr startall, ADS01 changed to port 8083, Palworld changed to port 8082
  • Tried to run ampinstmgr stopall > ampinstmgr upgradeall > Reboot > Current Version is still 2.5.1.4

After started the Palworld instance, i cant manage it as it shows Failed to login to remote instance.

Same problem on Debian 12 Help me please

Try this, worked for me in ubuntu. SSH to your server:

sudo su -l amp
ampinstmgr upgradeall

Great, now nothing is going on.
Website no longer accessible, instances no longer accessible.
The main thing is to execute upgradeall.

Funny that the game servers are running but you no longer have access to the software

Which has helped for me and has done so several times, whenever an update comes.

sudo su -l amp
ampinstmgr stopall
su
remove ampinstmgr

reinstall = bash <(wget -qO- getamp.sh)

Now everything is running again
I use Debian 12, no idea what goes wrong here that no normal AMP update can be installed

You could have simply restarted ADS lol

ampinstmgr start ADS

Lol No…

no because it then tells me no ads instance was found

Probably because you ran the command as the wrong user. Have to be amp

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