I’ve been having this issue very sporadically (sometimes a couple times a week, sometimes once a month). I’m curious as to how the more veteran folk here would try and narrow down the cause of this issue.

I can provide more info if needed!

Edit: More Info:

  • Using a static IP (no DHCP) through Netplan.
  • Dax87@forum.stellarcastle.netOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Thanks for the suggestion. So I have the static IP assigned with DHCP disabled both through Netplan, not through the router.

    I’ll remember to check the Netplann (?) journal/logs around that time, or are you referring to dmesg?

    • hillbicks@feddit.de
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Since you’re not really sure what the issue is, check all the logfiles around the time the problem starts. maybe you’ll see a service stopping or starting.

      • Dax87@forum.stellarcastle.netOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Thank you I’ll do that! It’s hard to catch exactly when it happens. I think I need to get some monitoring and alert services up and running

        • hillbicks@feddit.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Easiest route you could go is setup a systemd timer which runs every 5 mins, pings an ip and write the result into a logfile. that way you have a timestamp for the problem start without going all out with monitoring.

          Good luck!

        • JoeKrogan@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 year ago

          Changedetection.io it can send you an email or message when your server fails to ping it.you will then have the times. Its a 5 minute job to set it up. Make an account and your email or number or whatever and make a curl request to the specific endpoint in a cronjob

        • Atemu
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          You don’t need to catch that moment live, it was already recorded.

          Take a look at journalctl -b -1 (previous boot).