5 ms·

18:37:01 up 1618 days, 6:40, 6 users, load average: 0.00, 0.00, 0.00 Just go away and burn ;)

by Borg3 3y ago

riku_iki 3y ago
survivalship bias..
- profstasiak 3y ago
  the original comment was about the possibility of achieving 100% uptime, not that it's an expected outcome > A dedicated server from OVH running some processes under lxc and systemd can achieve 100% yearly uptime.
  - moondev 3y ago
    What is point exactly of saying something "might" happen 100% of the time?
    - Borg3 3y ago
      The point is, that if you want it to happen, you can do it with just minor effort.
      - riku_iki 3y ago
        and when your single server dies, it suddenly stops happening..
        Borg3 3y ago
        If my backend home server dies. I will rebuild it from spare parts right away. If one of frontend servers dies, nothing really happened. Ill spawn new one somewhere else (VPS, cheap dedibox, whatever).
milesvp 3y ago
Impressive uptime. Sidenote: I used to take pride with these kinds of uptime. I now see it as a significant risk. If I take over a machine with an uptime of more than a month, I assume that the machine cannot survive a reboot. Which means I spend a lot of time trying to figure out how to deploy that server with all the data it needs. These days there’s likely deployment systems in place that prevent some of the horrors I’ve seen, but there was a time in the not to distant past when you had to assume someone ssh’d into a box at least once a quarter to muck with something. If they didn’t reboot, there was no guarantee the changes they made would survive.
- Borg3 3y ago
  Well, it depends on model how you manage servers. Cattle vs Pets. And of course true for takeover, thats nightmare whatever it have uptime or not ;) I have just several servers here and there so their are all pets to me. Im 99% sure, server would boot cleanly. The remaining 1% is HW failure, with, can happen. Example: I have a software FW running on some older HW here w/ 2 disks in Soft RAID 1. I had to power it down for 2 days due to electric maintenance in building. What a suprise was booting it. One disk failed right away making creepy noise. Other was ok, but server was booting long, so I hooked up monitor to check things out. Well, second disk was NOT in good condition either, it started to spit I/O errors here and there. Anyway. I managed to boot FW to working state, but immediatly got spare HW and started preparing for replacement. Now it runs 3 disks in Soft RAID 1 :)
paulddraper 3y ago
Having an operating system run for 4 years is cool, but let's not pretend that's service uptime.
fanf2 3y ago
Ah, unpatched and full of security vulnerabilities.
- Borg3 3y ago
  Oh I really like those comments. People think that keeping autoupgrades on without control keeps them secure. Right... And then you keep hearing stories about server wont go up because of update, or stuff breaks horribly. Not to mention brining new bugs to the table. Its not that simple. I care what I install on my servers. Everything is carefully selected. Additionally, I follow KISS concept, so I run simple things that are managable.

18:37:01 up 1618 days, 6:40, 6 users, load average: 0.00, 0.00, 0.00 Just go away and burn ;)

by Borg3 3y ago

18:37:01 up 1618 days, 6:40, 6 users, load average: 0.00, 0.00, 0.00 Just go away and burn ;)

riku_iki 3y ago

survivalship bias..

profstasiak 3y ago
the original comment was about the possibility of achieving 100% uptime, not that it's an expected outcome > A dedicated server from OVH running some processes under lxc and systemd can achieve 100% yearly uptime.
- moondev 3y ago
  What is point exactly of saying something "might" happen 100% of the time?
  - Borg3 3y ago
    The point is, that if you want it to happen, you can do it with just minor effort.
    - riku_iki 3y ago
      and when your single server dies, it suddenly stops happening..
      - Borg3 3y ago
        If my backend home server dies. I will rebuild it from spare parts right away. If one of frontend servers dies, nothing really happened. Ill spawn new one somewhere else (VPS, cheap dedibox, whatever).

milesvp 3y ago

Impressive uptime. Sidenote: I used to take pride with these kinds of uptime. I now see it as a significant risk. If I take over a machine with an uptime of more than a month, I assume that the machine cannot survive a reboot. Which means I spend a lot of time trying to figure out how to deploy that server with all the data it needs. These days there’s likely deployment systems in place that prevent some of the horrors I’ve seen, but there was a time in the not to distant past when you had to assume someone ssh’d into a box at least once a quarter to muck with something. If they didn’t reboot, there was no guarantee the changes they made would survive.

Borg3 3y ago
Well, it depends on model how you manage servers. Cattle vs Pets. And of course true for takeover, thats nightmare whatever it have uptime or not ;) I have just several servers here and there so their are all pets to me. Im 99% sure, server would boot cleanly. The remaining 1% is HW failure, with, can happen. Example: I have a software FW running on some older HW here w/ 2 disks in Soft RAID 1. I had to power it down for 2 days due to electric maintenance in building. What a suprise was booting it. One disk failed right away making creepy noise. Other was ok, but server was booting long, so I hooked up monitor to check things out. Well, second disk was NOT in good condition either, it started to spit I/O errors here and there. Anyway. I managed to boot FW to working state, but immediatly got spare HW and started preparing for replacement. Now it runs 3 disks in Soft RAID 1 :)

paulddraper 3y ago

Having an operating system run for 4 years is cool, but let's not pretend that's service uptime.

fanf2 3y ago

Ah, unpatched and full of security vulnerabilities.

Borg3 3y ago
Oh I really like those comments. People think that keeping autoupgrades on without control keeps them secure. Right... And then you keep hearing stories about server wont go up because of update, or stuff breaks horribly. Not to mention brining new bugs to the table. Its not that simple. I care what I install on my servers. Everything is carefully selected. Additionally, I follow KISS concept, so I run simple things that are managable.