All custom game servers full with "already quit" game instances, new servers not auto-scaling to start up, games not shutting down? (URGENT - affecting live / unchanged game)

Question

question

Brian Jordan asked Sep 17, '18

All custom game servers full with "already quit" game instances, new servers not auto-scaling to start up, games not shutting down? (URGENT - affecting live / unchanged game)

EDIT: Sounds like affecting 2 other titles as well (per Slack)

We just noticed our (unchanged) game started not letting players join multiplayer. It appears that quitting the game executable is no longer causing the server instance to be destroyed.

In addition, NEW servers aren't starting up when players matchmake (it says still waiting for new servers to start up)

I'm currently manually refreshing the server instances list & manually terminating games that have quit in order to allow players to play (but since it's no longer auto-scaling, we can only have 3 games per region)

Title: E79E

Live game build version # (unchanged since 5/29/2018): 0.12.2.3

Example lobby that did not terminate (manually terminated to capture logfile): 118B2245B0EDC683

Log line from our Unity output: "Quitting the game!" (which is immediately before a call to Application.Quit();)

Custom Game Servers

2018-09-17-13-23-53.png (79.1 KiB)

games.png (106.7 KiB)

1

10 |1200

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

Brian Jordan commented · Sep 17, 2018 at 05:41 PM

Terminated these server instances in case termination / server auto-scaling will start working again after opening slots:

(EDIT: Removed list of terminated instances since issue seems resolved)

0 ·

Answer 1 · 2018-09-17T18:24:55Z

brendan answered Sep 17, '18

We've been looking into this since it was first reported. The quick update is that it appears to be due to delays in responses to scaling requests in EC2. We're attempting to work around it, and we'll update shortly.

1

10 |1200

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

brendan commented · Sep 17, 2018 at 11:58 PM

As you guys are already aware from our earlier discussion, this has been resolved and we're looking into how best to work with AWS to prevent it in future.

0 ·

question