3 ms·
Keep in mind that 95% downtime happens when you deploy things or change configuration settings. If I am drunk dancing in the woods as a solo operator no one is
by ozim 2y ago
Keep in mind that 95% downtime happens when you deploy things or change configuration settings.
If I am drunk dancing in the woods as a solo operator no one is doing config changes on my servers.
The remaining 5% downtime like internet connection to the server facility, solar flares, UFO taking over the world - I would not able to do anything about anyway, would have to wait until it goes away.
- martinald 2y agoYes, I agree entirely. The amount of times that I've thought a particular service I've made is "reliable" because of great uptime for 2-3 years (with no changes), that I do a small innocuous change and cause some issues really makes me remember this. The most common issues I have with long term projects are small code/config changes (#1 by a ridiculous degree), then way below is drives filling up and then way below that is actual hardware failure. Drives filling up are often the most annoying to fix as they cause very odd user facing problems. Just fixed this week an old wordpress site that I spent over 2 hours trying to fix, trying everything, before I realised the mySQL database was full. It turns out if a mysql db is full the provider revokes insert privs on the user and wp login will just go in a loop back to the login page if it can't write to the database. No errors on the UI :(.