AMP crashes out on the backend and it causes all instances to stop

OS Name/Version: Debian 11

Product Name/Version: 2.6.0.8 - 20250124.1

Problem Description:
I don’t really know where to start with this but I’ll be in different games I see a massive spike in data writing to my drives and then amp shows the backend drops (“Connection to the backend…will reconnect…”) and it full hard resets all I can see are the CPU activity… you can see it dip when the crash occurs. I’m at a loss for words. Does anyone have any suggestions of where I can start looking? are there logs anywhere that can be pulled?



I don’t see that it’s running out of resources (RAM / CPU / storage)

Slow method invocation: Servers took 7036ms to complete.
Slow response: ADSModule.Servers took 7037ms to complete.
Slow response: ADSModule.Servers took 7763ms to complete.
Slow response: ADSModule.Servers took 7758ms to complete.
Slow method invocation: Servers took 7496ms to complete.
Slow response: ADSModule.Servers took 7498ms to complete.
Slow method invocation: Servers took 7036ms to complete.
Slow response: ADSModule.Servers took 7038ms to complete.

Looking in debians log /var/log/syslog the only thing im seeing is

Jan 25 19:51:20 gameserver qemu-ga: info: guest-ping called
Jan 25 19:52:06 gameserver systemd[1]: amptasks.service: Failed with result 'timeout'.
Jan 25 19:52:06 gameserver qemu-ga: info: guest-ping called
Jan 25 19:52:06 gameserver systemd[1]: amptasks.service: Unit process 394715 (ampinstmgr) remains running after unit st>Jan 25 19:52:06 gameserver qemu-ga: info: guest-ping called
Jan 25 19:52:06 gameserver ampinstmgr[394744]: [Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:58
Jan 25 19:52:36 gameserver ampinstmgr[394744]: [Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CC>Jan 25 19:52:40 gameserver systemd[1]: Failed to start AMP Instance Manager Pending Tasks.
Jan 25 19:52:43 gameserver qemu-ga: info: guest-ping called
Jan 25 19:52:43 gameserver systemd[1]: amptasks.service: Found left-over process 394715 (ampinstmgr) in control group w>Jan 25 19:52:43 gameserver qemu-ga: info: guest-ping called
Jan 25 19:52:43 gameserver ampinstmgr[394785]: [Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:58            Jan 25 19:52:43 gameserver ampinstmgr[394785]: [Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CC>Jan 25 19:52:43 gameserver systemd[1]: This usually indicates unclean termination of a previous run, or service impleme>Jan 25 19:52:43 gameserver qemu-ga: info: guest-ping called
Jan 25 19:52:43 gameserver systemd[1]: Starting AMP Instance Manager Pending Tasks...
Jan 25 19:52:43 gameserver qemu-ga: info: guest-ping called
Jan 25 19:52:43 gameserver systemd[1]: Starting AMP Instance Manager Firewall...
Jan 25 19:52:43 gameserver qemu-ga: info: guest-ping called
Jan 25 19:52:43 gameserver systemd[1]: ampfirewall.service: Succeeded.
Jan 25 19:52:43 gameserver systemd[1]: Finished AMP Instance Manager Firewall.
Jan 25 19:52:43 gameserver systemd[1]: amptasks.service: start operation timed out. Terminating.
Jan 25 19:52:43 gameserver systemd[1]: amptasks.service: Failed with result 'timeout'.

Steps to reproduce:

Step 1: Start the panel
Step 2: Let the server run for while
Step 3: It intermittently will have this issue and crashes out.

Actions taken to resolve so far: Full restart of the server ran package updates to see if that was the issue. I reduced resources from the instances. I can’t seem to find a reason for it.

You can right click an instance to view it’s logs, or check the deployment log on the left.
One sanity check I’d recommend would be to see if you have too many backups or scheduled restarts scheduled all at the same time. Just a guess as I see the tasks service having a weird time in the syslog there.

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