Apologies to all for today’s performance issues and downtime.

Logging for our lemmy instance filled our main partition and brought everything to a halt. Our lemmy instance shares hardware with blahaj.zone, and the significant growth in lemmy over the last 10 days has caused the logs to grow in size exponentially! As a result of the logs filling up the main partition, both lemmy.blahaj.zone and blahaj.zone itself went down.

We’ve freed up some space, upgraded the hardware and spun everything up again, and it looks everything is back to normal.

Apologies for the inconvenience, and welcome back to everyone!

  • Nolando@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    Good to be back, and glad to hear it was only a slow hug-of-death. Any consideration in upgrading the server version to 17.4?

    Edit: are there any alternative channels where server status is posted?

    • Ada@lemmy.blahaj.zoneOPM
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Any consideration in upgrading the server version to 17.4?

      Yep. That’s on the radar. We’re trying to get a kbin instance up and running too, and we’ll most likely upgrade lemmy once that has been done.

      are there any alternative channels where server status is posted?

      Not yet. A week ago, it was basically just me on this instance. Now it’s me and my 1400 closest friends :)

  • colorfulmoth@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Nice to hear that everything is ok. Wouldn’t it be a good idea to shit out the logs to another form of long term storage? That could help during the influx of Reddit refugees.

    • Ada@lemmy.blahaj.zoneOPM
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Yeah absolutely. The main issue here is that this lemmy instance was spun up as a side project for me and until 10 days ago, I was basically the only user. We never planned for a reddit migration and 1400 user signups in a single week, so things are not currently configured optimally for two active instances.

      We’re aware of it though, and will get everything humming along smoothly, once we’ve had a chance to catch up :)