Posts
474
Following
7
Followers
16
the burr's test account, sysadmin since never, forced to sysadmin since forever
there is no good cop there is no good militaryperson.

KILL 'EM ALL 1997

(art by @/garbanzzobean on Instagram)
repeated

evil fucking valerie

i have that "almost exclusively porter robinson" kinda bisexuality
0
1
0
friendly reminder that the entire world's economy has always been a sum-zero game.
0
0
0
repeated
ooooohhh richard nixon
0
1
1
repeated

every furry with the dumbest takes ever and something about programming or toki pona in their bio then turn 18 and immediately turn the biggest fucking Gooner loser on the entire planet Please stop posting porn to minors

2
3
4
water so cold :skull_death:
0
0
1
very long post, very boring, but gives more info on the very long downtime and my mistakes throughout it
Show content

so here’s a bit of a “post-mortem”, i guess :

  • starting ~11 PM @ 03/05/25, the Feathered Nextcloud server was migrated from the cloud server (referred to as GER) to the new server (rta FRA, i know, very creative names). however, one user was missing from the new LDAP and had to be migrated
  • to do so, I tried to use a YNH feature which should export the entire LDAP from GER. however, this also exports config files and… yeah, you really don’t want the rest on an already-configured server. I therefore tried to remove every file i could from the backup, before importing it in FRA, as to only keep the LDAP export which I originally wanted
  • while importing the backup it somehow still had some data that configured FRA like GER and overrode every previous YNH configuration. thinking that this should’ve worked normally, i didn’t do a backup of FRA’s config beforehand, hence creating an absolute chaos
  • it being 3 AM at this point, i “panicked” and did the first logical thing, which was to fully uninstall yunohost as to try to reinstall it, making a backup of every app on it beforehand (while forgetting to update the apps… very smart, but anyways)
  • the reinstall didn’t work as it first noticed that there was old config files
  • moving the old config files made it try and install, but miserably fail for… no obvious reason, sadly

this led me with no choice apart than sleeping because it was 4 AM and then reinstalling the entire server today, the 4th of May, which is what i did this entire fucking afternoon (please save me, i’m still not done…). i’m really sorry for how long the downtime was (an entire half-day), i promise i won’t do the same mistake twice, this was way too fucking annoying! fuck!

1
0
1
oh my FUCKING god okay akkoma is fully restored this is a lot less stress to have now. FUCK.
1
0
1
we are fully back, soon.
0
0
0
testing federation capacity on new hardware
1
0
0
lent is over and anna isn't back... it's over for fedi
0
0
0
repeated

Build a Bear and their lesser known spinoff Concoct a Twink

3
6
4
I need to pin this

RE: https://kill-corporati...
0
0
1
repeated
smoking that plutonian pack
0
1
1
@9 i just approved ur oomfcity account :)
1
0
0
i imagine downtime to be at around 5 or 8/9 PM.
2
0
0
there is going to be downtime on kill-corp either tonight or tomorrow as i physically swap the nvme ssd from a server to another.
1
0
1
elleeeeeee @sierra there is NO vlpn emoji pack on this chud servver I am RIOTING
1
0
0
repeated
how the fuck do you get to the admin frontend...
0
1
1
> DirectMessageDisabledPolicy


?? why is this on what does this do
0
0
0
@sierra @Eleonora the thesmes are fucking g brokenn grrrrr grrhgrrrr
1
0
0
Show older