Lemmy.World Announcements

29066 readers

346 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world/

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

DM https://lemmy.world/u/lwreport
Email report@lemmy.world (PGP Supported)

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Join the team

founded 1 year ago

MODERATORS

ruud@lemmy.world

lwadmin@lemmy.world

lwCET@lemmy.world

jelloeater85@lemmy.world

Serinus@lemmy.world

lw_mod_notification@lemmy.world

MrKaplan@lemmy.world

690

[Fixed] Comments temporarily broken, being worked on (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by ruud@lemmy.world to c/lemmyworld@lemmy.world

56 comments fedilink hide all child comments

There was another attack going on (as you might have noticed). We're working on a fix. In the meantime, we've blocked the listing of comments, so we at least aren't down, but it did break comments.

Hope to have a fix in the next hour. Stay tuned!

Update OK we've implemented a fix, again many thanks to @sunaurus@lemm.ee for his assistance. This will prevent the outages we've seen last couple of days. Let's see what they will come up with next...

you are viewing a single comment's thread
view the rest of the comments

[–] BitOneZero@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

@ruud@lemmy.world and @sunaurus@lemm.ee

I added some self-awareness of concurrency to the Lemmy API Rust logic: https://github.com/LemmyNet/lemmy/pull/3805/files - this should allow a more standard in-band response to concurrency slow-response server overloads. Keywords ('woodstocksnoopy' as watchdog, and even more alarming keyworld to find in your logs: 'SITE_OVERLOAD') were added to the logging to make it explicit when this is happening.

@sunaurus@lemm.ee