Conversation
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
at least akkoma is back to fully stable, for sure...
0
0
1