question

Antti Tuppurainen avatar image
Antti Tuppurainen asked

Multiplayer server build that works in mock vm goes unhealthy. How can we debug this?

After upload, server Usage stays in Target Standby, and the build goes from Deploying to Unhealthy after a few hours.

No servers or logs are recorded.

The same build works in the mock vm without errors.

How can we debug the root cause?

multiplayer
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
Ivan Cai avatar image
Ivan Cai answered

Firstly, have you verified containerization? For specific steps, please refer to https://docs.microsoft.com/en-us/gaming/playfab/features/multiplayer/servers/locally-debugging-game-servers-and-integration-with-playfab#verifying-containerization.Can you tell me your title id and the status of the current server build?

There are three reasons why the build goes from Deploying to Unhealthy:

  • All the initial set of VMs are deemed Unhealthy. Some reasons include:

    None of the game servers have sent a heartbeat via GSDK for more than 10 minutes after being started. This usually indicates that the server is crashing, and you will see a NoServerHeartbeat health status for each VM in the region.

    The PlayFab Multiplayer Agent itself is crashing, or not being initialized on the VM (rare occurrence). Essentially the multiplayer service has not received a heartbeat from the Agent for over 10 minutes.

      • None of the VMs have reached a Running state (mostly stuck in loading assets) for more than 90 minutes.
      • None of the game servers have reached a StandingBy state for more than 90 minutes (although they are sending a heartbeat). This indicates an issue during game server initialization.

      You can refer to Locally debugging game servers and integration with PlayFab - PlayFab | Microsoft Docs to debug the root cause.

      3 comments
      10 |1200

      Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

      Antti Tuppurainen avatar image Antti Tuppurainen commented ·

      Yes, we've verified containerization.

      Additionally, the builds spontaneously began to function about 10 hours ago without any action on our part, and are now in the Deployed state and functioning as expected.

      The question remains: If containerization is verified, and heartbeats are verified, and we've done all local checks to ensure that the build functions in the local mock VM, but the build still goes unhealthy, how can we debug this?

      Note to moderators: Please don't mark this question as answered yet. It is not answered.

      0 Likes 0 ·
      serverstatus2.png (123.2 KiB)
      Antti Tuppurainen avatar image Antti Tuppurainen Antti Tuppurainen commented ·

      Our title ID is 3ABC3.

      0 Likes 0 ·
      Ivan Cai avatar image Ivan Cai ♦ Antti Tuppurainen commented ·

      We have investigated your title, this issue is probably caused by a situation in our deployment process. In this case, please notify us as soon as possible. We are very sorry for the situation you encountered.

      0 Likes 0 ·

      Write an Answer

      Hint: Notify or tag a user in this post by typing @username.

      Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.