| Re: [chrony-dev] Bug -- interaction between ntpdate and chronyd at bootup -- will never sync up |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Tue, Feb 05, 2013 at 11:50:20AM -0600, ray vantassle wrote:
> It's easy to duplicate.
> ntpdate starts up this way:
> NTPSERVERS="0.debian.pool.ntp.org 1.debian.pool.ntp.org
> 2.debian.pool.ntp.org 3.debian.pool.ntp.org"
> /usr/sbin/ntpdate $NTPSERVERS
>
> It makes 4 queries to each of 16 servers, for a total of 64 queries.
> That takes about 9.5 seconds.
> (A bit of overkill -- but that's the config in the ntpdate package.)
>
> At startup, ntpdate is invoked as a result of dhcp coming up or when
> the network starts up, via a script in /etc/network/if-up.d/
>
> /etc/init.d/chrony gets invoked about 2-3 seconds after ntpdate
> starts, to bring up chronyd.
Hm, I still can't reproduce it. I get the no majority and invalid tick
error messages, but it always seems to recover after couple minutes at
most.
What I find odd in the sources output you posted is that only one
of the servers seems to be reachable (377 in the reach column).
Can you please post your config and if possible also the tracking,
measurement and statistics logs (configured by the log and logdir
directives in chrony.conf) when that happens?
Thanks,
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.