Shadow @ Piefed.ca

u/shadow@piefed.ca
9 posts · 18 comments

Recent posts

Recent comments

on Piefed.ca upgraded to 1.7 · c/main · 4 pts · 32d

I also did a bunch of performance tuning on the infra + db, and patched a few slow queries in piefed. Should definitely be zippier!

on Status of federation issues? · c/main · 3 pts · 101d

I just threw some additional logging into the piefed code to try to figure out what's going on, this has been happening too long and it's being elusive =(

on Status of federation issues? · c/main · 1 pts · 101d

If you see this happen with a post / thread, can you follow up here with it for me to check the logs against please?

on Status of federation issues? · c/main · 2 pts · 101d

There seems to be some unknown bug in piefed (or our infra possibly) that I've had no luck in figuring out with Rimu. It's an ongoing battle =(

on Federation issues again · c/main · 1 pts · 123d

Argh. I think I've found the problem and applied a fix, let me know if it persists after this please!

on Federation issues? · c/main · 3 pts · 150d

Hmmm, I applied the latest updates a couple days ago but not seeing any errors in the logs. I just pulled in the latest changes yet again in case there was a fix, but I'll dig more later today.

on Sorry for the post spam · c/main · 1 pts · 180d

Sigh, this is fixed properly now.

For the curious: We didn't have the send_queue cronjob enabled, so scheduled messages weren't sent out when they were supposed to. Piefed seems to have a bug where the cron is enabled way in the future, it spams those old scheduled messages regularly.

As for why the struggle fixing it... this is embarrassing but I was looking at the wrong database. Last week I copied our "pyfedi" db to "pyfedi_utf" as part of correcting a problem with the db character encoding. I've been applying changes to the "pyfedi" db to fix this, instead of the "pyfedi_utf" database.

Lesson learned - clean up the old database once you know the new one is good.