The latest does show a fail after KillInactiveSessions Begin but before KillInactiveSessions End. See the excerpt here, which shows the results that span the time from the freeze through the restart:
Code: Select all
2022-10-19 19:23:14|[debug] KillInactiveSessions Begin
2022-10-19 19:24:55|Unexpected balance (121) in House Ring account at startup
2022-10-19 19:24:55|Crash recovery implemented, details in Event Log
2022-10-19 19:25:56|[debug] KillInactiveSessions Begin
2022-10-19 19:25:56|[debug] KillInactiveSessions End
More a question on whether or not there are specific settings on server-side (or client-side) that could help or other things you've seen that could cause these issues. I note there are other threads in the forum that reference this behavior. We've not seen it at this level in the past, so hard to dismiss the likelihood that it's related, somehow.
From the server side, I understand that a disconnect looks like a disconnect. Was wondering if anything is done client-side that could help diagnose, e.g., console logging that could be viewed through developer tools.