One of the things that greeted me once I started looking at server health, was that the TimeSync in eDir was +1:51 from true. All the servers agreed on this, which is by design. But still... nearly two minutes? Aye!
It turns out that the server configured as Reference forgot which server it was synching against. Since it didn't have anything to sync against, it went with its local clock-chip instead. Unfortunately, clocks in servers are famously unreliable beasties, and it drifted nearly two minutes in the time I was away.
So I fixed it. I also told the two PRIMARY servers under my control to sync against the same NTP timesource in their configured-sources list, so at least the correct time will be involved in time negotiations.
I'd like to convert to XNTP, but that'll require ALL of the servers in the tree modifying their configured sources to accomodate that change. We're not quite there yet.
Tags: novell, netware
It turns out that the server configured as Reference forgot which server it was synching against. Since it didn't have anything to sync against, it went with its local clock-chip instead. Unfortunately, clocks in servers are famously unreliable beasties, and it drifted nearly two minutes in the time I was away.
So I fixed it. I also told the two PRIMARY servers under my control to sync against the same NTP timesource in their configured-sources list, so at least the correct time will be involved in time negotiations.
I'd like to convert to XNTP, but that'll require ALL of the servers in the tree modifying their configured sources to accomodate that change. We're not quite there yet.
Tags: novell, netware