Server Status Thread

[loftar]

Shouldn't it be words[2] == "crashed"?

Yes, it should, but I had in fact already fixed that. The reason for the outage earlier today was because I wasn't at home and so didn't have the alarm with me. I was going to bring my laptop, but I forgot it last minute. It was thanks to Jorb calling my phone that I noticed it. And of course it crashed like literally five minutes after I left home. :P

- Notifications about server status from devs

You may want to check the front home page. It is updated live with server status, and I usually update it live with troubleshooting status when it does crash. If the server is crashed and I haven't written anything on the front page, that most likely means I haven't noticed the crash for whatever reason.

- Post some details of server's current hardware and investigate lags.

I am in fact strongly considering upgrading the server hardware, see eg. this thread. It's currently running on a Skylake Xeon, and Hetzner has Zen 4 servers available, which should be a fairly strong upgrade. I also suspect part of lag problems is also due to the SSDs in the current server having weirdly long write latencies sometimes, and I suspect they've gotten better since too.

[HarryDresden]

Seems like they have some pretty good NVMe offerings but they get pricey quickly. Zen4 is super solid, would recommend it over Sapphire Rapids.

[DreadKatak]

Timber

[moj1]

This is 2nd time server crashed exactly when I was fighting to tame an animal, couldn't it do it 2 minutes earlier or later?

[vatas]

[loftar]

The reason for this crash is that someone managed to put a stack in itself somehow. I'm not sure how to accomplish that, and it already being inside itself makes it difficult to find the root cause. For this case, I think I'll just add an assertion so that it instead crashes when it actually happens, so that I can hopefully see how that is done. Unfortunately that means that this crash might happen again before it is solved.

[TheServant]

The reason for this crash is that someone managed to put a stack in itself somehow. I'm not sure how to accomplish that, and it already being inside itself makes it difficult to find the root cause. For this case, I think I'll just add an assertion so that it instead crashes when it actually happens, so that I can hopefully see how that is done. Unfortunately that means that this crash might happen again before it is solved.

everyone will try to put a stack inside a stack so expect the crash soon

[loftar]

everyone will try to put a stack inside a stack so expect the crash soon :mrgreen: :mrgreen: :mrgreen:

Honestly, I hope they succeed.

[HamsterBBT]

The reason for this crash is that someone managed to put a stack in itself somehow. I'm not sure how to accomplish that, and it already being inside itself makes it difficult to find the root cause. For this case, I think I'll just add an assertion so that it instead crashes when it actually happens, so that I can hopefully see how that is done. Unfortunately that means that this crash might happen again before it is solved.

If I may report something, the sea shells still remain in the pack after opening in the pack

[gravesmerch]

wonder if is related to the 1 item stack?

also when adding soil stacks to treepots, holding shift won't pickup next stack, but maybe thats intended