Manually Delete Instance?

Technical Support
1

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.

Make sure you search before posting! Duplicate posts for the same issue may not be answered.

OS Name/Version: Ubuntu 24.04.1

Product Name/Version: (Always use the full version number - not ‘Latest’) 2.6.0.4 - 20241106.1

Problem Description:

Updated my AMP Controller and Target and I believe my Ubuntu target has a full disk drive. I'm unable to connect to it using the Controller.
Is there a way to manually delete an instance?

Steps to reproduce:

N/A

Actions taken to resolve so far: Not much to provide as I’m fairly certain the issue is disk space. Looking for advice on freeing up some space

2

You should be able to remote into the Target over SSH and delete extra backups and all that.
AMP’s files are stored under /home/amp/.ampdata/instances
You can safely edit files as the amp Linux user (sudo su -l amp to switch to the user)

To see if it’s a disk issue beforehand you can run df -h

3

Thanks for that, do you know what partition AMP is defaulted to install on? Is it sda1?
Do you know how to extend partitions in Ubuntu?

4

You’d have to google how to extend partitions, AMP is by default located in the same partition as the root directory

5

Well I’ve managed to free up enough space on the disk (i think) it’s currently sitting at 87% full.

I am currently running into this error in the Deployment Logs from my Controller server

22:23:02
Failure communicating with http://EDITED:8080/ - check that the host is available and reachable.
HttpRequestException
[0] (HttpRequestException) : No connection could be made because the target machine actively refused it. (EDITED:8080)
   at Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)
   at Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at AMPAPI.RemoteInstance.GetResponseDynamic(String Module, String Method, Object Parameters)
   at AMPAPI.RemoteInstance.API_Core.Login(String username, String password, String token, Boolean rememberMe)
   at InstanceManagerPlugin.RemoteInstanceManager.Login(String username, String password, String token)
SocketException
[1] (SocketException) : No connection could be made because the target machine actively refused it.
   at Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
Failed to update EDITED_GameServer_Name - Could not connect to the remote instance at http://EDITED/. Connection Refused

This all started after I updated my AMP to the latest version

6

Double check your firewalls on both machines, the Controller and Target need to be able to “see” each others web port

7

eh, there’s no firewall on the linux target server and it always was able to connect to the Controller before attempting to update.
I ended up backing up my instances and rolling the server snapshot back prior to target setup, expanded the main disk, and rebuilt the target connection.
Annoying and inconvenient, but did the job.

8

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