Server issues: New server

[Seizure]

W8 anyone?

[Pieczywo]

FUUUUUUUUUUUUUUU ;( i have lost everything from my inventory, all my eq, and the boat with 2 chest of curios and stealed wax and my wardrobes are empty i hate this game


just kidding, want to play more i have cloned the saw q148

[kotsa]

ya items plants got rollback but stats not ..... and i got again cubpoabrds of those pies ..... this need be fixed or some1 will use this with bad intention/... or already did for dupe pies/cheese

[Thijssnl]

FUUUUUUUUUUUUUUU ;( i have lost everything from my inventory, all my eq, and the boat with 2 chest of curios and stealed wax and my wardrobes are empty i hate this game


just kidding, want to play more i have cloned the saw q148

Dont think 1 saw is worth all your other stuff, or your stuff must be really lowlevel :<

[MrGemini]

just kidding, want to play more

Dont think 1 saw is worth all your other stuff, or your stuff must be really lowlevel :<

I think with "just kidding" he means he didnt loose something.

[Masti]

So why was the rollback from a day or two ago?
I made so much progress and I'm sure I'm not the only one. A warning could've been nice.
Could someone explain what the heck happened?

Edit:
Just went into my house, and for some reason, my cupboards weren't rolled back, but instead the whole freakin' outside world was?

Allright, so, if I had stored something in my cupboards before the rollback, it would've effectively multiplied, like my 2 Blood Sterns just now.
Why would you not warn us about this?

[rye130]

The server ran out of memory and crashed. Data was lost. There was no warning because it wasn't planned.

[Masti]

Holy Ancestors that was fast.
That is indeed quite unfortunate, but from that arise a couple more questions regarding the current state of the server.
First of all, in what intervals are the backups made and was the memory overload caused by the game's code or some sort of a DDOS attack or does it perhaps still remain unknown?
Secondly, if the server just crashed, how did some data stay intact while the other parts were, seemingly, copied in from a backup afterwards?

Thank you for legitimately answering my question and with such haste.

[mvgulik]

A warning could've been nice.

That is indeed quite unfortunate, but from that arise a couple more questions regarding the current state of the server.
First of all, in what intervals are the backups made and was the memory overload caused by the game's code or some sort of a DDOS attack or does it perhaps still remain unknown?
Secondly, if the server just crashed, how did some data stay intact while the other parts were, seemingly, copied in from a backup afterwards?

Current state of server is: UP
Anything else is "No Good"

Additional crash detail might be pried loose from Loftar at next crash at irc://irc.synirc.net/Haven ... If he knows them at the point that is.

[loftar]

First of all, in what intervals are the backups made

Backups are quite irrelevant for the purpose of these kinds of events, because unless I do them constantly (and they can't be done without shutting down the server), they're bound to be older than the data as it was rolled back to anyway.

was the memory overload caused by the game's code or some sort of a DDOS attack or does it perhaps still remain unknown?

In either event, it was caused by the game's code, because a DDoS attack shouldn't cause memory leaks to begin with. Whether, however, there is an exploit that can be used to trigger the bug that causes the server to consume memory rapidly is unknown, however, since I don't know what causes it (or I would have fixed it). I have found no reason to suspect that it is an exploit, however.

The difference in this case, however, is that so much memory was consumed that the kernel's OOM killer went in and reaped the server process before I had a chance to take care of it properly. I am considering turning off memory overcommitting.

Secondly, if the server just crashed, how did some data stay intact while the other parts were, seemingly, copied in from a backup afterwards?

It's simply the last saved version of the data that is used. The data that has been "lost" was simply such data that had not been saved from the live state of the server at the point where the kernel killed it.