Lazer room events page stuck on "match in progress" if something happens server side

[Theighlin]

https://osu.ppy.sh/multiplayer/rooms/1544877/events

By stuck i mean this

and by something i mean that the server seems to have crashed/lost connection to a lot of users yesterday.

This room was played live on stream

If you don't want to click the link the flow goes kinda like this:

• Game is aborted
• Game is started but get following notification: Play in this state is not permitted. Request to https://osu.ppy.sh/api/v2/rooms/1544877/playlist/18701987/scores timed out after 10 seconds idle (read 0 bytes, retried 0 times).
• Host tries to abort match but gets : An unexpected error occurred invoking 'AbortMatch' on the server.
• Host tries to change the song and finally gets: Connection to the multiplayer server was lost. Exiting multiplayer.

[bdach]

There was a transient outage last night around midnight GMT. It affected several systems at once. To my naive eyes it appears to have been a network issue that resolved on its own. Spectator server is likely not resilient enough to survive this sort of thing so if anything it should be tracked as a spectator server issue rather than here. Or this should just be closed if it was an outage / incident that we have no control over (looks like that to me but I don't have that much experience staring at metrics).

[Theighlin]

Adding here because it seems it's kinda the same thing or related/caused by the same problem,
profile realtime page also shows the room as active forever https://osu.ppy.sh/users/11577732/realtime

More importantly, it seems the host/creator? of the stuck room can't create another room while that one is active.
The streamer in question tried to open a new room 2 days after the incident and got a "number of simultaneously active rooms reached" error. He had to have someone else open a room, invite him and give him host.

[peppy]

I fixed the case in question here. Generally I've been doing this manually when it pops up.

We probably need some smarter logic in server-spectator to clean up rooms on restart or on error detection.

Which is to say, I don't see this as an osu-web issue so let's move it to that project.