The instance was down so long, I was worried it wasn’t ever coming back.

  • Wander@yiffit.netM
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    I’m sorry. Apparently the Lemmy server component went down but because the frontend was still responsive my downtime monitor didn’t detect it as down.

    • l_b_i@yiffit.net
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      With a little blip a few minutes ago, it looks like https returns 500, so the downtime monitor might not be working 100%. Also its update time is listed as hundreds of hours ago.

      • Wander@yiffit.netM
        link
        fedilink
        English
        arrow-up
        0
        ·
        8 months ago

        I’m working on it. Apologies for the downtime. I added enough resources to keep this from happening for another year, although I’ll try to migrate to 0.19 this week.

    • l_b_i@yiffit.net
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      would it be worth it to add an api monitor to the health checks?
      curl --request GET --url 'https://yiffit.net/api/v3/community?name=meta' --header 'accept: application/json'

      • Wander@yiffit.netM
        link
        fedilink
        English
        arrow-up
        0
        ·
        8 months ago

        Thank you. I’ll add that to the status monitor. Do you have experience in system administration? I am basically unable to take proper care of yiffit at the moment, often being out of town and I need some help :(

      • Wander@yiffit.netM
        link
        fedilink
        English
        arrow-up
        0
        ·
        8 months ago

        Yes, I’ll upgrade this week at latest. Sorry for keeping us back. Historically that used to be the safest decision for Lemmy, but I do realize it’s been a long time.