![](https://beehaw.org/pictrs/image/9bf506d7-191d-4ac4-b701-f69795917b97.png)
![](https://lemmy.ml/pictrs/image/c66ab020-6977-46de-a1cc-bb81744e3e14.png)
We ran into this bug in a production system a few months back. We had a legacy cluster of windows workbenches which connected to each other using an encrypted communications API on an isolated network. We initially couldn’t determine why the system clocks fell out of sync in a rather cascading fashion. Guess this explains it. We ended up resolving it by bridging them to the internet and forcing a sync with time servers. A few months later, it happened again. At the time we thought it to be a bug in Windows. Go figure it was.
Even in the most stable distros I’ve had this issue. We had a RHEL 9 server acting as a graphana kiosk and it failed after an update. Something dbus related. I’d love to know why, as it’s been the only failure we ever had but nonetheless it shakes confidence. Windows 11 updates trashed three servers, one to the point we had a to fly an engineer out. My hope is that immutable distros fix this.