Yes it's also possible that my solution "works" because it distracts me for long enough for NTP to sync :)
On Wed, May 24, 2017 at 12:20 PM, Zachary Amsden <[email protected]> wrote: > This is similar to what I hit with NTP the other day after a restart. I > tried a number of things, and I think the only thing that worked was > waiting for NTP to sync. Pitfalls: ntpdate requires a host on the command > line, and doesn't read the configuration file. > > There was some circumstantial evidence that a connection to the Ubuntu NTP > pool failed during boot - overload or random connection failure, but I > never got an exact cause. > > On Wed, May 24, 2017 at 12:09 PM, Tim Armstrong <[email protected]> > wrote: > > > I see that with some frequency when restarting my system. > > > > I usually manage to fix it with a non-scientific approach of running some > > combination of these commands until ntp-wait works: > > > > sudo service ntp restart > > sudo ntpdate -s ntp.ubuntu.com > > ntp-wait -v > > > > On Wed, May 24, 2017 at 11:33 AM, Jim Apple <[email protected]> > wrote: > > > > > testdata/cluster/admin > > > > > > calls ntp-wait which returns an error: > > > > > > "ntpq: read: Connection refuseLeap status not avalaible" > > > > > > Has anyone seen this? There are 0 Google hits for refuseLeap and the > > > string is not present in my repository or my /etc/. > > > > > >
