Having an issues with recent pulls or db update giving db errors on game server #510
-
Low Priority, as this is just a test box (unless the issues turn out to be global) On July 17, when I pulled from base branch and updated with dbtool/rebuilt, the game client kept throwing a lot of DB errors: Previous working merge/sql update before that was June 27. The server is up to date as of writing this, and the only conflicts were the conf files, as pointed out to me by clay.
I resolved the conflicts and relaunched the game to the same errors but didn't want to pester Clay anymore so I sat on it for a few days. Today, I was able to restore a backup of the db using dbtool and got the server up and running, but due to DB being behind its causing other issues (obv). So I pulled again, used dbtool to update, rebuilt, and got the same db errors as the other day. Clay mentioned with all the recent cor changes and DB formats theres bound to be issues... I'm apprehensive to even post this because I know there's going to be growing pains but at the same time I wanted to know if it's just me or a global issue and if it is the latter to make sure its a known issue. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
You default confs shouldn't have an impact on the server, since they need to be copied one level higher. What could be going wrong is that its expecting some value that's not being set in the updated version of the configuration. There's a PR open that changes one item, but the last time I can think of it changing was minor, when updating some default strings, and before that when adding capacity point modifier. There have been a ton of DB changes recently, so that would explain the errors on startup, but what is dbtool doing? |
Beta Was this translation helpful? Give feedback.
-
DBtool ran fine (to my eyes, idk)
|
Beta Was this translation helpful? Give feedback.
-
You might be behind on some other core updates as well. The hidden flag for RoE was added some time ago, and that's one place you're erroring out (#392 ), systemid is from Teo's rework for SDT, and that table should have been pulled in, assuming you've pulled latest. Can you try pulling the latest code in a separate location to see if the errors are still occurring on your end? |
Beta Was this translation helpful? Give feedback.
You might be behind on some other core updates as well. The hidden flag for RoE was added some time ago, and that's one place you're erroring out (#392 ), systemid is from Teo's rework for SDT, and that table should have been pulled in, assuming you've pulled latest.
Can you try pulling the latest code in a separate location to see if the errors are still occurring on your end?