62
submitted 1 year ago* (last edited 1 year ago) by abeltramo@lemmy.world to c/selfhosted@lemmy.world

Mine is in the picture: 1544 days and counting!

It's an EC2 nano instance that's used only as a monitor for a few services that are running inside my VPN. It has served me well over all these years!


EDIT: before everyone starts screaming about "security":
It’s not internet facing and no port is opened, all it does is fire up a notification if/when something doesn’t reply.

Even in the unlikely scenario that someone gain access to it that means that my VPN is already compromised, and I’ve got bigger problems to worry about.

all 28 comments
sorted by: hot top controversial new old
[-] Makussu@feddit.de 42 points 1 year ago

Not so high because of frequent updates and reboots for security

[-] FancyGUI@lemmy.fancywhale.ca 3 points 1 year ago

I was about to say the same. My nodes have weekly updates, but that's fine. Just k8s things.

[-] Wxfisch@lemmy.world 27 points 1 year ago

So you never apply patches or updates, that seems like an odd thing to be proud of but different strokes for different folks I guess.

[-] abeltramo@lemmy.world 8 points 1 year ago

It's not internet facing and no port is opened, all it does is fire up a notification if/when something doesn't reply.

Even in the unlikely scenario that someone gain access to it (nobody did in the last ~4 years) that means that my VPN is already compromised and I've got bigger problems to worry about.

[-] Makussu@feddit.de 14 points 1 year ago

Makes sense but even then i would just run automatic updates every few months. Just to keep best practice. Nonetheless cool uptime, now do 10 years :)

[-] abeltramo@lemmy.world 5 points 1 year ago

Well now it's becoming kind of a challenge: will AWS terminate/migrate the instance at some point, or will I be forced to reboot?

[-] tal@kbin.social 19 points 1 year ago

I remember this story from about twenty years back hitting the news:

https://www.theregister.com/2001/04/12/missing_novell_server_discovered_after/

Missing Novell server discovered after four years

In the kind of tale any aspiring BOFH would be able to dine out on for months, the University of North Carolina has finally located one of its most reliable servers - which nobody had seen for FOUR years.

One of the university's Novell servers had been doing the business for years and nobody stopped to wonder where it was - until some bright spark realised an audit of the campus network was well overdue.

According to a report by Techweb it was only then that those campus techies realised they couldn't find the server. Attempts to follow network cabling to find the missing box led to the discovery that maintenance workers had sealed the server behind a wall.

[-] Crow@lemmy.world 18 points 1 year ago

My fridge has been on since it was plugged in. It’s also offline.

[-] ridel@lemmy.world 7 points 1 year ago

You have no power outages? Or you UPS your fridge? That's commitment.

[-] theolodger@feddit.uk 4 points 1 year ago

Power outages aren’t that common, so it’s quite possible

[-] key@lemmy.keychat.org 3 points 1 year ago

Unless you live somewhere with above-ground powerlines and wind. Biannual occurrence for me.

[-] CriticalMiss@lemmy.world 7 points 1 year ago

PBX admins are laughing in the background as their uptime is almost 4k days, running CentOS 5

[-] sv1sjp@lemmy.world 5 points 1 year ago

Personally I am shutting down my server in the midnights to make it relax for a bit. #MentallySupportingOurHomeServers Butt yes, I still agree with the comments above, even if theserver is not directly connected on Internet, upgrading is mandstory nowadays. Bots are everywhere, especially nowadays with all of these AI tools.

[-] jax@lemmy.cloudhub.social 5 points 1 year ago
[-] abeltramo@lemmy.world 9 points 1 year ago

Thanks for your high value contribution to this tread!

[-] xebix@lemmy.world 10 points 1 year ago

I logged in just to downvote.

Now for a relevant comment. I used to love those high uptime values as well, but I'll echo the security sentiments of others in this thread. On the other hand, as you said it's not public facing, so not as big a deal. I still think it's kinda cool!

[-] abeltramo@lemmy.world 8 points 1 year ago

Thanks, I wasn't expecting everyone to take this so seriously, it was supposed to be funny..

[-] eric5949@lemmy.cloudaf.site 1 points 1 year ago

Well propegating the idea it's cool to have years long uptimes regardless of the fact it may be practical for you in this instance iis nonetheless dangerous.

[-] jax@lemmy.cloudhub.social 3 points 1 year ago

Just because it’s not public facing doesn’t mean that it’s not an issue. It might be less of an issue, but it is still a massive vulnerability.

All it takes is one misconfiguration or other vulnerable system to use this as a jumping off point to burrow into other systems. Especially if this system has elevated access to sensitive locations within your network.

[-] green_dot@le.fduck.net 4 points 1 year ago

About 6 year uptime on one machine before we shut it down and relocated.

[-] Gormadt 3 points 1 year ago

Currently 60 days

When the power goes out my nas shuts down and also for updates

[-] memphis@lemmy.fmhy.ml 2 points 1 year ago

I think my first raspberry pi got to 500-ish days before we had a power outage

[-] JoeKrogan@lemmy.world 2 points 1 year ago

I don't know it depends on the patches really I have automatic updates so I guess a few months would probably be the longest between kernel patches

[-] activator90@lemmynsfw.com 2 points 1 year ago

A month probably. I have to reboot it mainly for updates

[-] sleepybear@lemmy.myspamtrap.com 2 points 1 year ago

Many years ago working for a monitoring software company someone had found a bug in the uptime monitoring rules where they reset after a year.

It was patched and I upgraded one client and their whole Solaris plant immediately went red and alerted. They told me to double it to two years and some stuff was still alerting.

They just said they’d try to get around to rebooting it, but it was all stable.

Everywhere else I’ve worked enforces regular reboots.

[-] PeterPoopshit@sh.itjust.works 1 points 1 year ago* (last edited 1 year ago)

I think I got up to 300 or so days on my old Athlon XP Gentoo server. I have "upgraded" since then and my current server can't go more than 2 days. I have an arduino connected to the motherboards reset button pin that resets it whenever the bash script that communicates with the arduino stops running but even that somehow still crashes at least once a week and needs manual intervention.

[-] negativenull@negativenull.com 1 points 1 year ago

My father ran an HP-UX server that did inventory management (not internet connected) that had an uptime greater than 10 years before it was migrated.

this post was submitted on 13 Jul 2023
62 points (100.0% liked)

Selfhosted

40394 readers
282 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 2 years ago
MODERATORS