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?
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?
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:
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.
You can refer to Locally debugging game servers and integration with PlayFab - PlayFab | Microsoft Docs to debug the root cause.
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.
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.
4 People are following this question.