Hey all, thanks for sending me emails when thing are going wrong. We hit the max memory limit again because somehow my elasticsearch config got overridden and the max heap size disappeared, meaning Elasticsearch was consuming all available memory and locking up Redis again.
Servers sure are fun, aren't they? 😢
Anyways, I'm gonna keep an eye on the dashboards to make sure our memory usage doesn't spiral out of control again. Thanks for reporting!
=> More informations about this toot | More toots from somnius@merveilles.town
@somnius How are you handling configuration management for the server?
There are so many settings for every piece of software these days it can really make your head spin.
=> More informations about this toot | More toots from tuxinator@merveilles.town
@tuxinator To be honest there are tons of ways I can improve things, right now everything is running as separate processes all on one server and I am manually editing all configs on my own. I missed the Elasticsearch one when I upgraded that particular process (that's what reset the config and caused the memory problem)
Eventually when I have the time outside of work and everything else I need to rethink the server architecture. I think I'll start posting about that in the forum to get ideas
=> More informations about this toot | More toots from somnius@merveilles.town
@somnius Yea I'd be happy to throw around some ideas to make your life easier for upgrades and general automation of manual tasks. (I don't think I have a forum account yet though)
For the size of our community everything on one server should be totally fine though. I would avoid overcomplicating that at all costs. :sadlinux:
=> More informations about this toot | More toots from tuxinator@merveilles.town
@somnius thank you for your hard work :) It's nice to see the instance back up <3
=> More informations about this toot | More toots from neauoire@merveilles.town This content has been proxied by September (ba2dc).Proxy Information
text/gemini