Unexpected Server Shutdown in Oath of Office (Place ID: 122580487983776)

At approximately 3:40-3:50pm EDT on Monday, March 16th, a live server running under Place ID 122580487983776 with roughly 150 concurrent players suddenly shut down. Players in that server were removed with Error Code 288.

However, no shutdown command was issued by our team, and there were no deployments or updates occurring at that time.

After the shutdown, players attempting to rejoin the experience encountered Error Code 279 for several minutes before access returned to normal. Our team confirmed that the place was completely empty and no servers existed for those several minutes.

Summary of observed behavior:

  • Server with ~150 players terminated unexpectedly
  • Clients saw Error Code 288
  • Rejoining attempts returned Error Code 279 for a few minutes
  • The issue resolved itself without intervention
  • No manual shutdowns, updates, or server management actions were triggered from our side

I’m happy to provide any additional information if needed (timestamps, logs, etc.). Since the server was highly populated, I wanted to flag it in case it indicates a broader issue.

A private message is associated with this bug report

Hi Vinny,

Thank you for the detailed report. I was able to pinpoint your server and I can see that it shut down due to being out of memory. To observe this yourself, you can look into CloseReason in BindToClose.

For more help in diagnosing memory issues, you can consult this page.

Since this is not a bug, I will mark this post as “Can’t Fix”, but please feel free to ask if you have more questions.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.