kɜ:ʳ @chr@cybre.space

hey y'all, i'm no longer reachable on discord if you had my info there previously. if you need to get in contact with me, i'm @chr:cybre.space on matrix, @chr1x on wire, or you can email me at chr@cybre.space (or admin@cybre.space if you want to reach @nightpool as well)

hi i'm chr and its my life mission to boost every dragon

got quite a few new folks here today, welcome! your admins here at cybre.space are myself and @nightpool, you can read the instance rules at http://cybre.space/about/more, and likes ⭐ are florps here. if you have any questions, feel free to ask! happy pinging!

the ghost in the machine sounds like a pretty spooky guy

if you run mastodon on ubuntu or debian with jemalloc and you notice sidekiq crashing frequently, it may be related to this issue with FFI: https://github.com/mastodon/mastodon/issues/15751

the fix in our case was to add LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so to the systemd unit files, so that all native (non-ruby) code could use the same memory allocation system

just fixed an issue with cybre.space's sidekiq worker that was causing it to frequently (30-60s) restart, interrupting longer-running tasks and possibly causing posts to get lost from feeds. hopefully things should be a bit more stable now

and then suddenly its fine?? didnt get a response to my support ticket but i'll take it

well, this sucks

server slowness appears to be due to degraded disk performance on the host, following up with them to see if there's anything to be done about it

cybre.space users: this appears to be due to the cybre.space web server taking too long to respond and returning a 504 / timeout error. if you see this happen, it might mean the server is just processing slowly and will eventually submit the post! (looking into why it's taking so long, but this should help you avoid accidentally submitting duplicates in the meantime)

looks like cybre.space might be having intermittent problems with duplicating new posts made by users on here, looking into it now. (in the meantime, if someone sends you multiples of the same reply, it's probably not their fault!)

cybre.space users: our media provider is having an ongoing issue, so you've probably noticed some images not loading and some uploads not working today. incident page is here: https://status.digitalocean.com/incidents/hyclhcgjs16g

they identified the issue as of 4 hours ago, so hopefully it is resolved soon.

cybre.space is now on mastodon 3.3! there were quite a few changes since 3.1, you can read about them here:
https://github.com/tootsuite/mastodon/releases/tag/v3.2.0
and here:
https://github.com/tootsuite/mastodon/releases/tag/v3.3.0

there are a few known issues in the cybre.space fork, which i did not have time to address tonight, but should get to by the end of the week. please feel free to ping @ me or create new issues if you see anything else wrong after the update:

https://cybre.tech/cybrespace/mastodon/issues

okay after some, uh, brief jankiness due to a dependency needing an update, we should be fully back now

notifications might be missing while the post-update migrations run, they should be back shortly

lol the assets backed everything up for a bit there

anyway restarting now~

deploy starting. if cybrespace goes down, i fucked up and it should be back soon sry