Minor: RTM server connection errors on console due to suspend

kradski

Reproduce:

1. Have active session at character select screen.

2. Put PS5 to sleep.

(Guessing, as I'm a non-DBD programmer) 3. Wait for an autoscale or restart event to happen with the RTM servers.

4. Wake PS5 back up without closing DBD.

5. Get persistent connection errors.

Resolve: force-restart the DBD app.

Without knowing any of the backend, my guess is one of the memory-cached startup steps obtains an RTM server list or possibly caches an long-ttl A record. That step either needs to be repeated during unsuspend operations too. I'd say force the cache dump/refresh/whatever on connection errors, but then during legit downtime you'd inadvertently get ddosed.

Cheers. :)