Official Kiwi Farms Pleroma Server - pt 3: official flagship instance of the fediverse

Jeff Bezos said:
I found this screenshot when browsing the fediverse server basedlist:

web-49-1.png


Apparently you can still reach users on instances that blocked if somebody from a non-blocked instance acts like a bridge
Click to expand...
Transmisisia? The mentallers are only good at making up stupid words.
 
  • Agree
Reactions: JoshPlz
I just signed up for this last night and was seeing lots of 500 errors and issues when trying to follow people or report a user for spam. Was going to report it here but I see the disk has crashed, maybe the disk going bad was the cause of those issues. We'll see when you get things migrated.
 
CrunkLord420 said:
Alright here's the deal. I've been banging around on the ol' server in prep for migration. Seems like we got some filesystem corruption on the Pleroma OS partition. Bad news is that the site is down because the filesystem is in read only mode. Good news is that there's nothing all that important on that filesystem and already have backups in as part of migration prep. Bad news is that the system is on a drive without RAID that also shared by the actual hypervisor itself. The drive we're on is a ticking timebomb. I'm going to do some extra backups and then just ignore the filesystem error for now. Migration has been A C C E L E R A T E D.
Click to expand...
God damn it, I was just making fun of Poast for going down for maintenance
 
  • Feels
Reactions: Harvey Danger and TimeTravel_0
The Pleroma database has been repaired, upgraded and restored, but I forgot to prioritize the transfer of the Pleroma media files. I'll start the instance up they finish. I did start it up for a second before I realized all the files were missing, but it looks like the DB wasn't catastrophically broken after everything.

In the mean time the git and gemini services have been restored. Synapse database is being re-imported from a psql file I created just before starting an upgrade on the old server, which was happening when the Pleroma filesystem went read-only.

I severely underestimated how large our files are, Josh's proxmox configuration with ZFS has compression, I guess. Trying to pull TBs worth of data off a RAID 1 HDD pair with compressed thinly provisioned ZFS partitions is not fun.
 
  • Like
  • Informative
  • Feels
Reactions: 6thRanger, The Sacred Chao, Oban Lazcano Kamz and 7 others
CrunkLord420 said:
The Pleroma database has been repaired, upgraded and restored, but I forgot to prioritize the transfer of the Pleroma media files. I'll start the instance up they finish. I did start it up for a second before I realized all the files were missing, but it looks like the DB wasn't catastrophically broken after everything.

In the mean time the git and gemini services have been restored. Synapse database is being re-imported from a psql file I created just before starting an upgrade on the old server, which was happening when the Pleroma filesystem went read-only.

I severely underestimated how large our files are, Josh's proxmox configuration with ZFS has compression, I guess. Trying to pull TBs worth of data off a RAID 1 HDD pair with compressed thinly provisioned ZFS partitions is not fun.
Click to expand...
ok but did you even try turning it off and then back on again?
 
  • Like
  • Thunk-Provoking
  • Informative
Reactions: Lake, Heinous Fuckery, Dead Red and 1 other person
  • Like
  • Agree
  • Thunk-Provoking
Reactions: Loose change, electric mouse, 820㎌Cap and 24 others
You must log in or register to reply here.
Back