1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi Stephane,
That spike definitely seems concerning.
The Event tab was also flooded with crashing processes
Are you using a debug build? Based on the above statement, my assumption would be that the crash is probably creating a massive core dump which is flooding the disk. Have you tried root causing the crash itself? I would recommend using GameLift Anywhere to test your server on a local machine. This may help identify potential crashes, and memory leaks (that might be in turn causing a massive crash dump).
If you are still facing issues, I would recommend creating a support case so the service team can directly help out here.
Shashank
répondu il y a 6 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 5 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Hi Shashank,
Thank you for your answer.
The build is not a debug build, it is a production one. I am afraid the processes crashed due to the disk space being full, and not the opposite.
The GameLift Anywhere solution to try and reproduce is definitely a good option to investigate, thank you for the tip.
Otherwise, I have some updates: in the build causing the disk to flood, we were dumping logs on a different file for each match (using the matchId as part of the file name). I must insist that the logs file were not the cause of the disk being flooded (as you can see on the screenshot of the "du" command). But somehow, after stoping writing in different file for each match, the problem have not appeared yet. This makes me believe that you had a good intuiting about memory leaks. Maybe the way we were handling file writing was bad in the opening/close process. I'll try to investigate more if I have the time.
Thank you so much for your time and suggestions, it was truly appreciated.
Stephane
Actually, I just discovered that the GameLift Server SDK build was a development one. Thank you for your insights, I will change that.