-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Errors while startup #1536
Comments
@tastybento this is the github issue where are old and new tables in database. |
https://cdn.discordapp.com/attachments/310623455462686720/763002234933346324/unknown.png But after server start one of that long names recreated again. So i it will throw error again after restart. But everything seems to be working with short db tables, players didnt report any missing things. |
@BONNe Yes, the migration command is a problem. I don’t think it is using the latest short names. I’ll check it. |
It is oneblock: |
Hello, thanks for reply. |
@kFxDaKing https://ci.codemc.io/job/BentoBoxWorld/job/AOneBlock/126/ uses the shorter named table. When used, it should migrate directly over. Take backups, and let me know if you see any issue. |
Ill test it tomorow, thank you. |
https://imgur.com/a/xTIkRpd |
Well, there was a longstanding bug in BentoBox where the tables were not being renamed. I do not understand how or why that happened so this is the root cause. You will need to use the latest BentoBox build. If you do get an error, please share the full console log from start up (the zip file) so I can see what other errors are happening. |
I'm closing this issue since it seems the bug has been solved. |
Description
Describe the bug
Errors while server startup - https://imgur.com/a/rur4xdW (include server.cfg)
Steps to reproduce the behavior
Yesterday i transferen json2mariadb, then i used cmd /bb migrate.
After that i changed config "JSON2MARIADB" to MARIADB.
WHen i startup server there is those errors, but everything looks working.
Environment
Output of
/bbox version
(Mandatory)The text was updated successfully, but these errors were encountered: