Selfhosted

40347 readers

402 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

265

Self Hosting Fail (feddit.nl)

submitted 8 months ago by padook@feddit.nl to c/selfhosted@lemmy.world

95 comments fedilink hide all child comments

I woke up this morning to a text from my ISP, "There is an outage in your area, we are working to resolve the issue"

I laugh, this is what I live for! Almost all of my services are self hosted, I'm barely going to notice the difference!

Wrong.

When the internet went out, the power also went out for a few seconds. Four small computers host all of my services. Of those, one shutdown, and three rebooted. Of the three that ugly rebooted some services came back online, some didn't.

30 minutes later, ISP sends out the text that service is back online.

2 hours later I'm still finding down services on my network.

Moral of the story: A UPS has moved to the top of the shopping list! Any suggestions??

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

[–] Kuinox@lemmy.world 115 points 8 months ago* (last edited 8 months ago) (14 children)

When you are bored, backup a VM then hard kill it and see if it manage to restart properly.
Software should be able to recover from that.
If it doesn't, troubleshoot.

[+] pezhore@lemmy.ml -11 points 8 months ago (11 children)

While I appreciate the sentiment, most traditional VMs do not like to have their power killed (especially non-journaling file systems).

Even crash consistent applications can be impacted if the underlying host fs is affected by power loss.

I do think that backup are a valid suggestion here, provided that the backup is an interrupted by a power surge or loss.

[–] taladar@sh.itjust.works 43 points 8 months ago (9 children)

most traditional VMs do not like to have their power killed (especially non-journaling file systems).

Why are you using a non-journaling file system in 2024 when those were common 10+ years ago?

[–] lazynooblet@lazysoci.al 4 points 8 months ago (1 children)

It's been a while since a power cut affected my services, is this why?

I remember having to troubleshoot mysql corruption following abrupt power loss, is this no longer a thing?

[–] taladar@sh.itjust.works 8 points 8 months ago

Databases shouldn't even need a journaling filesystem, they usually pay attention to when to use fsync and fdatasync.

In fact journaling filesystems basically use the same mechanisms as databases only for filesystem metadata.

load more comments (7 replies)

load more comments (8 replies)

load more comments (10 replies)