this post was submitted on 15 Jun 2023
11 points (100.0% liked)

Selfhosted

39948 readers
513 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
11
How would you resolve this issue: Your server's internet randomly becomes inaccessible until reboot. (Ubuntu 22.04, Netplan) (forum.stellarcastle.net)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/selfhosted
33 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
[–] [email protected] 2 points 1 year 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?

[–] [email protected] 2 points 1 year 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.

[–] [email protected] 2 points 1 year ago (3 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

[–] JoeKrogan 1 points 1 year ago* (last edited 1 year ago) (1 children)

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

[–] [email protected] 1 points 1 year ago

Thanks I'll give that a shot! I was thinking about using a solution with my VPS, but I may go this route.

[–] [email protected] 1 points 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!

[–] [email protected] 1 points 1 year 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).

[–] [email protected] 2 points 1 year ago

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