TitleID: 88F85
Repro steps: 1. Have a client request a multiplayer server. 2. Turn off the client's internet. Our game server waits 1 minute for a player to connect before calling Unity's Application.Quit(). Expected behavior: Server state goes to standby. Actual behavior: Server state stuck active.
[1]: /storage/attachments/5862-capture15.png
[2]: /storage/attachments/5863-capture16.png
Repro steps: 1. Have a client request a multiplayer server. 2. Turn off the client's internet. Our game server waits 1 minute for a player to connect before calling Unity's Application.Quit(). Expected behavior: Server state goes to standby Actual behavior: Server state stuck active
Is Application.Quit called? Servers never go back to StandingBy after Active, when the process exits we create a new one.
@Dimitris-Ilias Gkanatsios you are right. There was a "pause" in "run_playfab_server.bat". In case this helps anyone else, do not put pauses/sleeps at the end of scripts running on the server :-P, and Dimitris is always right :).
Sorry, yes I knew that. I should've said "Expected behavior: New standby comes online. Actual behavior: No new standby server gets created".
The server look-up page (capture15) shows an active with zero players. That should be a standby. Logging into the VM and opening the task manager shows 2 servers running (capture16). There should be 3.
Normally, if I "End task" my game server in the VM, a new standby gets created instantly but starting yesterday, it doesn't.
How is this .bin process called? Any chance what calls it is alive but for some reason cannot create a third instance of it?
We are using the standard game servers with free 750 core-hours . So, I believe Playfab multiplayer agent is responsible for starting standby servers. It does so by calling our "run_playfab.bat". 
I just tested it again. Our game server calls Application.Quit() to kill itself but no standby server get launched.
33 People are following this question.
