Skip to main content


About last night...

I discovered that my server ran out of memory and killed the database server process while it was performing a long-running #Friendica schema update, which corrupted the data, which prompted me to look into the daily backup I set up years ago... 1/4

ouch.

Also getting only 1/4 😱

Yeah, Friendica's Twitter connector doesn't import threads, I'll have to complete myself.
At least it stayed up while my server was down!
Ah, now I'm getting it. You're talking about syndicating TW posts back that your server doesn't know because it was down.
Yes, all my Twitter posts are mirrored back to Friendica, and vice-versa, all my Friendica posts are mirrored to Twitter.

Each individual step didn't require too much active time, but the multiple dumps each took several hours, the couple reimports attempts also were lengthy. I would say about 5 hours total over a full week between scouring the web for solutions to corrupted database, perusing MariaDB logs to check it was correctly functioning again, chasing rogue background tasks and crons, and deleting unused databases/server user.

But it did occupy a significant chunk of my thought space even when not actively working on it.

⇧