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.
  • hillbicks@feddit.deEnglish
    3·
    1 year ago

    This might not be applicable to your use case, but maybe it helps.

    Couple of years ago I had a problem where ONE windows laptop was unable to access the internet. Sometimes it would work right away, sometimes it took 1 or 2 reboots, sometimes the damn thing wouldn’t budge.

    lo and behold, it turns out the windows laptop was assigned a DHCP address that one linksys router had as a static ip. Why that resulted in a sporadic error and not a constant one I’ll never know.

    So next time you have this issue, rip out the network cable from the server and try to ping the ip the server is supposed to have.

    Other than that, check the journal if something start to pop up around the time you experience the problem.

    • Dax87@forum.stellarcastle.netOPEnglish
      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.deEnglish
        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.netOPEnglish
          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

          • AtemuEnglish
            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).

          • hillbicks@feddit.deEnglish
            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.worldEnglish
            1·
            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