Skip to content
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

DB corruption #22

Closed
FlorianLudwig opened this issue Apr 2, 2018 · 3 comments
Closed

DB corruption #22

FlorianLudwig opened this issue Apr 2, 2018 · 3 comments

Comments

@FlorianLudwig
Copy link

For my community server it seems the database got corrupted. I got a lot of funny business going on, like:

Wells in baskets
screenshot from 2018-04-02 21-08-56

Berry bushes in backpacks
screenshot from 2018-04-02 13-24-04

Friendly (as in not moving) bears
screenshot from 2018-04-02 12-57-05

At some point I had a berry bush turn into a bowl of dough when I picked a berry from the bush. (but cannot reproduce it anymore)

Also I am pretty sure I have had rattle snake skins before i updated the server.

Fixing the bug

It seems to be related to have a server without the 71 content update connecting to a 67 server. Not sure how this could make things go wrong but it does correlate

Recovery

Any ideas how to cleanup the db?

@FlorianLudwig
Copy link
Author

This seems to affect other community servers as well:

yay new update with horses, cactus ,and snakes. so to get a snake you pick a berry, for a cactus pick a berry from snake! and to get a dead tree pick all the berries off the cactus! HAHAHA i love new patches! and now the chill server crashes, joy that's what i get for wanting to see the desert and horses.
-- http://onehouronelife.com/forums/viewtopic.php?pid=5856#p5856

@jasonrohrer
Copy link
Owner

jasonrohrer commented Apr 2, 2018

I'm guessing that this is caused by you NOT updating your client along with your server.

The client won't update if useCustomServer is set, so it will fall out of sync with the server. Disable it in your client to get the update.

Note that this behavior will be improved in the next client update. The client will now complain if its version does not match the version of the server that you're trying to connect to.

Closing this for now. Please open a new one if the issue persists after updating your client.

@FlorianLudwig
Copy link
Author

FlorianLudwig commented Apr 6, 2018

I still believe there is more to it. For two reasons:

a) I could ride horses before. So if the client wasn't up to date there wouldn't be horses. And if the server wasn't up to date, what was I riding and how was i moving so fast from the server points of view?

b) Now I even updated client and server to 73. This means we got version number checks! So this cannot be happening anymore, right?
screenshot from 2018-04-06 22-31-19

Well, I am bear.

cnwillz pushed a commit to mybackupgroup/OneLife that referenced this issue Apr 8, 2019
JustinLove pushed a commit to JustinLove/OneLife that referenced this issue Feb 6, 2021
useOnContained and contFoodDish implementation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants