AMS Troubleshooting Guide

Overview

This page contains troubleshooting information for possible issues you may encounter while using AccelByte Multiplayer Servers (AMS).

Fleet issues

I don't see any VMs running

It may take up to 10 minutes for the VM to be provisioned. Please wait and check again.

I see a VM count greater than zero, but there are no dedicated servers (DS) running

• Check the DS logs to see if the servers are crashing.
• Verify the DS startup command to ensure it is correctly configured.
• Confirm that your game build is not faulty (e.g., a "bad build").

Does the instance type have the sufficient resources to run the server?

• Ensure your VM selection is appropriate for your DS's CPU and memory requirements. Consider using a larger VM if crashing persists.
• Use the AMS DS Metrics dashboard in Grafana to monitor the resource usage of individual DS and VMs.

Does your DS have the necessary AGS permissions?

If your DS relies on AccelByte Gaming Services (AGS), ensure you have followed the instructions for creating IAM clients with the correct permissions and namespace settings.

Logs and Artifacts issues

I can't find logs for my DS

Verify that log sampling is enabled for your fleet.

Log sampling is enabled, but logs are still missing

• Use Grafana to investigate the watchdog and artifact collector logs:
  1. Open the Explore view in Grafana.
  2. Select the Logs data source.
  3. Apply label filters:
     • ams_fleet = your_fleet_id
     • service_name = ams-watchdog or ams-artifact-collector
  4. Apply Logfmt operations to use the Logfmt parser.
  5. Run query to review the sequence of events and messages based on DS states.

The DS is reported to have "CRASHED," but there is no core dump

Ensure core dump sampling is enabled for your fleet.

note

A DS is considered "CRASHED" if it exits with a non-zero code. For example, Exit code 137 indicates the process was killed due to running out of memory (OOM). Use Grafana to check for memory usage.

DS Claiming issues

Player sessions are reporting failures in finding a DS

• Check your fleet to see if it has DS instances in a ready state.
• Consider increasing the buffer and max server count to meet higher demand.

I have DS instances in the ready state, but players can't claim them

• Use Grafana to confirm that your DS instances are running in the regions requested by players.
• Check the claim keys on your fleet to ensure they match the claim keys on the session template or the client version specified by the game client.
• Verify if Quality of Service (QoS) is enabled for the target region.

Players are being kicked out of sessions mid-game

• Ensure your DS correctly handles the drain signal, as recommended in the Listening to the drain signal section in the Integrate your dedicated server to AMS using the AGS SDK page.