• roofuskit@lemmy.worldEnglish
    5·
    20 days ago

    After a month and a half downtime all the users will have moved on to other instances. This is essentially a death sentence for the instance and its communities.

    • TrackShovel@lemmy.todayEnglish
      2·
      20 days ago

      You underestimate the userbase. I made a temp account in the mean time, but we are a hyper tight knit community. We will probably lose accounts - no question - but the core userbase will return

  • drspod@lemmy.mlEnglish
    2·
    20 days ago

    Alt text:

    Slrpnk.net is currently offline due to an unforseen hardware failure in combination with the main system-administrators having no physical access to the server location until mid July due to work or summer-holiday related travels.

    We are very sorry for this unforseen down-time, but slrpnk.net will return for sure and we already have some plans for a nice relaunch, so stay tuned!

    • squaresinger@lemmy.worldEnglish
      1·
      20 days ago

      What exactly happened there? It was the big thing, then I didn’t use it for a month or so and then it was gone.

      • philpo@feddit.orgEnglish
        1·
        20 days ago

        The admin basically ran it as a one man show with only one other admin who had very limited privileges. He then went on a “business trip” or workaction or longterm vacation - there were different stories. Anyway, the database went belly up, the other admin couldn’t do a thing and none could contact the admin. There are some rumours that he wasn’t who he claimed he was and actually was a Chinese national who simply returned home, but who knows that. As a matter of fact none had any meaningful contact with him for months then and it appears he did not return. (But is alive)

        A Austrian NGO who amongst others does host some mastodon instances,etc. took over and now feddit.org is on a very productive, professional and transparent level.

  • souperk@reddthat.comEnglish
    0·
    20 days ago

    Wondering if a volunteer could go to the physical location necessary to restore service. If it’s in Athens Greece, I can make the trip.

    Edit: The server is located in Azores, the flight would cost 415eur, I cannot afford that, maybe someone in Portugal could help?

    • IcyToes@sh.itjust.worksEnglish
      0·
      20 days ago

      Is it in a data centre or someone’s house? If the latter, would they let a stranger in?

      Surely they would need a backup and replicate db to so in case of hardware failure they switch over.

      Sounds like they could improve their setup.

      Too much of a single point of failure.

      • Kris@feddit.orgEnglish
        0·
        20 days ago

        Slrpnk.net admin here.

        The failure seems to have been in the main firewall, if it had been the server itself we could have easily restored it on another server from the backups on another machine. But as it stands, remote access is entirely cut off.

        There usually is another person with hardware access, but they are on summer holidays. This seemed like an acceptable risk at the time…

        An off-site backup would have been nice of course, but due to the costs involved in running an Lemmy instance of that size on a rented server, it would have not been a great option either.

        I have plans to add a KVM to the main firewall via a secondary connection, but even that might have not helped in this case. I’ll know more when I have physical access again.

        • nickwitha_k (he/him)@lemmy.sdf.orgEnglish
          01·
          20 days ago

          I’ve done a lot of SysAdmin and DCOps stuff in the past so, thought I’d give you some plausible suggestions (haven’t dug deep into Lemmy DB stuff and DNS/Federation of the stack, so not sure all is practical).

          Scenario 1 - Preserve and merge when access is restored

          Setup

          • Spin up two VMs/VPS (or one that has enough grunt for two Lemmy servers). Call them robak.slrpnk.net and slrpnk.net and point DNS appropriately.
          • Pull federated content from other instances and place it on robak, set as read-only.
          • Sync important comms to (new) slrpnk.net without content.
          • Allow users to sign up, vetting as possible (all mods). Keep a list of those that are vetted (call it vetted.list). Inform all users that any non-vetted users will have their content dropped when access is restored.

          Merge!

          • Once access is restored, ensure that (old) slrpnk.net is set to read-only.
          • Schedule a maintenance window (announce more time than you are likely to need).
          • During the maintenance window, put (new) slrpnk.net into R/O, or just block external access.
          • Query the db on (old) slrpnk.net for all users.
          • Subtract the vetted users from vetted.list from the list.
          • Drop all records from the resulting list of non-vetted users from (new) slrpnk.net.
          • Insert the records from vetted and new users (those without conflicts) into the DB on (old) slrpnk.net.
          • Validate that everything is working
          • Cut over DNS and spin down the new VMs/VPS.

          Scenario 2 - Server is in DC or Admin able to facilitate access

          • Get a db dump/backup.
          • Spin up temporary slrpnk.net on a VM/VPS.
          • Use backup of temporary server to restore data to original, when possible.