Exact same thing happened to me the other day. Like exactly. Maybe we live in the same area.
this post was submitted on 03 Mar 2024
268 points (96.9% liked)
Selfhosted
49863 readers
440 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 2 years ago
MODERATORS
Two pitfalls I had that you can avoid:
- look at efficiency. It's not always neglible, was like 40% of my energy usage because I oversized the UPS. The efficiency is calculated from top power the UPS can supply. 96% efficient 3kW UPS eats 4% of 3kW, 120 watts, even if the load you connected is much smaller than 3kW
- look at noise level. Mine was loud almost like a rack server, because of all the fans.
I replaced that noisy, power hungry beast with a small quiet 900W APC and I couldn't be happier
when you say some services on your network are you talking about machines or softwares?
for machines yes ups makes sense for softwares writing some scripts to run on start up should be enough another alternative can be setting up wake on Lan that way you can bring all up again wherever you are
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CSAM | Child Sexual Abuse Material |
| DNS | Domain Name Service/System |
| NAS | Network-Attached Storage |
| PiHole | Network-wide ad-blocker (DNS sinkhole) |
| Plex | Brand of media server package |
| RAID | Redundant Array of Independent Disks for mass storage |
| SATA | Serial AT Attachment interface for mass storage |
| VPS | Virtual Private Server (opposed to shared hosting) |
| ZFS | Solaris/Linux filesystem focusing on data integrity |
8 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.
[Thread #567 for this sub, first seen 3rd Mar 2024, 16:05] [FAQ] [Full list] [Contact] [Source code]
In addition to ups, an LTE failover. I've had my Comcast crap be offline for hours.
I'd like that, but also a really long-running UPS. multi-hour power outages are surprisingly common in my area.
Thats no longer a UPS.
You could get something like a powerwall, something designed to power things from batteries for a long time.
Or get a generator with an automatic failover. The UPS then covers the downtime between powerfailure and generator taking load
Why is that no longer a UPS?
Generally, UPS (lead acid) batteries are not designed for long-cycle deep discharge.
They are designed to hold their rated load for a minute or so until the power is restored (generators start, power-uncuts) or the servers have a chance to shut down.
But maybe thats dated information, and modern UPSs are designed to run from batteries for a few hours.
That seems like a weirdly and artificially narrow definition of UPS.
Does this require a lot of gear? Or does it simply act as another gateway?
It requires an LTE capable gateway and a data plan. As for the rest you can simply write your routing tables so that if the main gateway doesn't work, use the secondary gateway with lower prio.
load more comments
(1 replies)
Could also be a good opportunity to add a service monitor like Uptime Kuma. That way you know what services are still down once things come back online with less manual discovery on your part.
My suggestion just changes your threat model, so may not be a good one based on your wants.
Perhaps consolidate systems? Managing less devices = less points of failure. But adds the risk of any given failure being more severe.
This thought came to me this morning. I have 4 machines both because the BEAST grows organically, and because we're always trying to avoid that single point of failure. Then a scenario comes along that makes you question your whole way of thinking, diversifying may actually create more problems
I feel your pain. Just the other day the disk on my home assistant machine died after a power outage and I had to replace it with another disk and restore from backup.
The same thing happened to me recently except the power outage killed one of my host drives.
I got three refurbished APC ups's from https://www.Excessups.com and have been in the process of setting up NUT to shut things down when power goes out.