[ntp:questions] NTP sync failing with error: Leap not in sync

Jochen Bern Jochen.Bern at LINworks.de
Thu Apr 2 13:54:18 UTC 2015

On 04/01/2015 10:23 PM, Unknown wrote:
> Server dropped: Leap not in sync
> stratum 3, precision -23, leap 11, trust 000
>  1 Apr 14:28:05 ntpdate[18328]: no server suitable for synchronization
> found

That's indeed an error code labelling your server as unsuitable as a
sync source to your clients. I admit I've never seen it together with
another stratum than 15 (also an "is unsynced" marker), though.

The stratum being given as 3 suggests that your server considers itself
synced to one of its stratum 2 sources, and my first guess would be that
that server signals weird flags as well. (Which *should* cause your
server *not* to consider it suitable, either.)

Running ntpq against your server doesn't output its peers' leap seconds.
Try dry-running ntpdate against them from your server.

> 2 packets reassembled into response

NTP packets as used in syncing shouldn't be large enough to trigger any
MTU problems short of downright insane pMTUs. Do you have *duplicated*
packets happening in your network?

> server 0.centos.pool.ntp.org iburst
> server 1.centos.pool.ntp.org iburst
> server 2.centos.pool.ntp.org iburst

*Pool* servers but you *consistently* get mis-synced? Hmmmmmmm ... :-/

								J. Bern
*NEU* - NEC IT-Infrastruktur-Produkte im <http://www.linworks-shop.de/>:
Server--Storage--Virtualisierung--Management SW--Passion for Performance
Jochen Bern, Systemingenieur --- LINworks GmbH <http://www.LINworks.de/>
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Geschäftsführer Metin Dogan, Oliver Michel

More information about the questions mailing list