-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on server start #111
Comments
I'll look into making it not crash in this situation, but from the error it looks like Biolith's game state was corrupted. That's stored using Minecraft's own game state mechanism, so it suggests to me you are wise to restore from backup anyway. The odds are good some other game data was also corrupted... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today the server crashed after it's usual reboot. Looking at the crash report, I blamed Traverse. After removing it, the server started normally. Not wanting to remove Traverse, I then used yesterday's server backup, which runs fine as well.
Whatever happened to kill the server, must have happened yesterday. Currently asking around what people have been up to yesterday, looking for clues. Unfortunately I don't have any logs from yesterday. Only from today.
The text was updated successfully, but these errors were encountered: