Fedia Discussions

2 readers

1 users here now

founded 1 year ago

MODERATORS

jerry@fedia.io

Federation is more broken than usual (fedia.io)

submitted 10 months ago* (last edited 10 months ago) by kbal@fedia.io to c/fedia@fedia.io

11 comments fedilink hide all child comments

When I look at https://fedia.io/all/newest right now there seems to be very little getting through today, with only 3 new threads in the past 10 hours.

Edit: 4 now that I've posted this one, and now I notice that they're all from local users.

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

[–] jerry@fedia.io 3 points 10 months ago (6 children)

Hi all. I am working on it. I am trying to figure out what the problem is this time rather than just restarting the containers.

[–] e-five@fedia.io 0 points 10 months ago (1 children)

if there's anything people can help with don't hesitate to ask in matrix!

One thing I wanted to raise to your attention was asdfzdfj's change to persist logging for docker setups which might make it easier to debug if your logs aren't persisted between container restarts

I mentioned in matrix but just in case since it's a bit of a gotcha for people that run in docker:

as a headsup for anyone running docker, there was a recent change to persist storage of logging just merged. it requires creating a directory and changing permissions on it. the admin guide was updated here but you may need to mkdir -p storage/logs and sudo chown $USER:$USER storage/logs where you run docker from by next sync/release

this may or may not be relevant to you depending on if sync'ing would change your compose setup

[–] jerry@fedia.io 2 points 10 months ago

I am going to apply this upgrade this weekend. I spent a few hours looking through logs this morning but didn't see anything obvious (there are a breathtaking amount of logs) so gave up and restarted the containers. Will look again when it fails after I make log storage persistent

load more comments (4 replies)