Selfhosted

60210 readers

1317 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How would you resolve this issue: Your server's internet randomly becomes inaccessible until reboot. (Ubuntu 22.04, Netplan) (forum.stellarcastle.net)

submitted 3 years ago* (last edited 3 years ago) by Dax87@forum.stellarcastle.net to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] Dax87@forum.stellarcastle.net 0 points 3 years ago (1 children)

I forgot to mention that I'm not using DHCP, statically allocating a local IP

[–] dudeami0@lemmy.dudeami.win 0 points 3 years ago (1 children)

Is there a DHCP server at play? Is the static IP outside of the DHCP range? This does sound like a typical IP collision.

[–] Dax87@forum.stellarcastle.net 0 points 3 years ago* (last edited 3 years ago) (1 children)

DHCP is enabled on the router, but I believe the IP address is outside the designated DHCP range.

I'll double check when I'm home!

Edit: I will also say that this modem/router is dedicated only for the server, so there shouldnt be any other clients on it at all.

[–] hillbicks@feddit.de 0 points 3 years ago (1 children)

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.net 0 points 3 years ago (1 children)

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 0 points 3 years ago (1 children)

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.net 0 points 3 years ago (1 children)

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

[–] Atemu@lemmy.ml 0 points 3 years ago (1 children)

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

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

[–] Dax87@forum.stellarcastle.net 2 points 3 years ago

Thank you for this sweet tip! I'll definitely be using this.