#SelfHosting - i love reading how much uptime you have.
-
#SelfHosting - i love reading how much uptime you have. But sorry, I am on the other side of the rainbow. My uptime maxes out at 23:59:59... because i force reboots daily.
And Now I am wondering if maybe i should shutdown my server for 8h sleep time and just serve static "Sorry, server is sleeping now" from some dummy host.
Yes - sometimes my genius is obvious.
-
#SelfHosting - i love reading how much uptime you have. But sorry, I am on the other side of the rainbow. My uptime maxes out at 23:59:59... because i force reboots daily.
And Now I am wondering if maybe i should shutdown my server for 8h sleep time and just serve static "Sorry, server is sleeping now" from some dummy host.
Yes - sometimes my genius is obvious.
@wikiyu I used to be in the "Look at my insane uptime!" club. I have since learned better.
If any of my servers uptimes are > 31d, I start getting twitchy, because that means monthly patches didn't run like they're supposed to.
-
@wikiyu I used to be in the "Look at my insane uptime!" club. I have since learned better.
If any of my servers uptimes are > 31d, I start getting twitchy, because that means monthly patches didn't run like they're supposed to.
@jjbaumgartner Nice point.
About updates I am now on a yolo side of world:
"alias yolo=sudo make all updates on my local pc, on my vps and on my homeserver, dont ask questions. --force && then reboot it"
and beside of that, both - vps and homserver has yolo type update in cron. And then reboot of course
Because - backups are not only to be a backup. I am now really see that I need them in case of issues that may happen at ANY night.
-
#SelfHosting - i love reading how much uptime you have. But sorry, I am on the other side of the rainbow. My uptime maxes out at 23:59:59... because i force reboots daily.
And Now I am wondering if maybe i should shutdown my server for 8h sleep time and just serve static "Sorry, server is sleeping now" from some dummy host.
Yes - sometimes my genius is obvious.
-
@wikiyu (Sharing a room with a loud IBM Workstation that masqueraded as server was a no go, especially with the girl I used to date, so it had to go to sleep)
-
#SelfHosting - i love reading how much uptime you have. But sorry, I am on the other side of the rainbow. My uptime maxes out at 23:59:59... because i force reboots daily.
And Now I am wondering if maybe i should shutdown my server for 8h sleep time and just serve static "Sorry, server is sleeping now" from some dummy host.
Yes - sometimes my genius is obvious.
@wikiyu Honestly, "server is sleeping" pages deserve to be a standard HTTP status code. 503 Service Unavailable just doesn't capture the vibe.
Also, daily reboots is just aggressive self-healing infrastructure. You're not chaotic, you're ahead of the curve.
-
@wikiyu Honestly, "server is sleeping" pages deserve to be a standard HTTP status code. 503 Service Unavailable just doesn't capture the vibe.
Also, daily reboots is just aggressive self-healing infrastructure. You're not chaotic, you're ahead of the curve.
And the most funny part is... that these daily reboots started from weird network errors caused by my previous ISP that was slowing down my internet while connected device has been up for more than 26h.
I was using my server as endpoint for their infrastructure instead of their router (that was rebooting every 12h for some reason).And that 24h reboot came from that.
Ofcourse i could just restart my network connection. But making reboot was easier. And now its just a routine.BTW I would say it is should be HTTP 2xx because it is a expected behaviour from my perspective
269 "f off, server went to bed" 
-
R relay@relay.infosec.exchange shared this topic