[#]mastoadmin hey folks—I noticed a strange issue that's been happening since today where when Elasticsearch is running, the scheduler process gets stuck on an Index process and slowly eats all my server RAM until the server bricks itself. Has anyone seen this and do you know how to debug this issue?
I'm on Hometown 1.1.1 / Mastodon 4.2.10, and I'm using Elasticsearch v7.
=> More informations about this toot | More toots from somnius@merveilles.town
@somnius
Netdata has saved me more than once in this sort of pickle
=> More informations about this toot | More toots from djm@merveilles.town
@djm This looks great, but I'm having trouble installing it! I have been meaning to get some kind of logging solution going that goes beyond journalctl—but there's so much documentation it's hard to sift through how this can work heh. I'll have to keep this in mind for a rainy day!
=> More informations about this toot | More toots from somnius@merveilles.town This content has been proxied by September (3851b).Proxy Information
text/gemini