[ntp:questions] NTP shows all servers in condition "reject"

Steve Kostecke kostecke at ntp.org
Tue Jun 10 13:49:40 UTC 2008

On 2008-06-09, Ronny Egner <Ronny.Egner at siv.de> wrote:
> Dear List,
> i´m having slight problems getting ntp to synchronize.
> The problem i am facing occur on all my new 6 servers
> which are all equally configured (Red Hat AS 4 U4, 64-bit).

Are they VMs?

> The ntp.conf configuration file:

None of my comments about your configuration file are germane to the
lack of sync issue, but ...

> restrict default nomodify notrap noquery
> restrict

These restrictions are OK. They do not block time service.

> server solaris-server
> server windows-dc-serverA
> server windows-dc-serverB

You can reduce the initial sync time from ~ 5 minutes to ~15-20 seconds
by appending 'iburst' to your server lines.

> broadcastdelay  0.008

The broadcast delay line is meaningless, but harmless, unless this ntpd
is operating as a broadcastclient.

> keys            /etc/ntp/keys

The keys line is meaningless, but harmless, because the symmetric key
configuration is incomplete.

> ntpq> peers
>   remote           refid    st t when poll reach delay  offset jitter
> solaris-server     10.x.y.2  5 u   18   64  377  0.259 892.342 30.508
> windows-dc-serverA 10.x.v.1  4 u   17   64  377  0.214 847.816 50.335
> windows-dc-serverB 10.x.v.1  4 u   22   64  377  0.272 923.808 45.667

There is a signifiant diference in offsets between those remote time
servers. And the jitter is quite high. Are all of these server on the
same LAN? Are any at remote sites or reached over a VPN?

> ntpq> rv 39492
> assID=39492 status=9014 reach, conf, 1 event, event_reach,
> srcadr=solaris-server, srcport=123, dstadr=10.x.y.z, dstport=123, leap=00,
> stratum=5, precision=-18, rootdelay=31.601, rootdispersion=10316.483,

The root dispersion suggests that this peer has not been synced to a
real time source is quite a while. This needs to be fixed first.

Could you please post the solaris-server 'ntpq -p' billboard from (in a
condensed format as shown above)?

> ntpq> rv 39493
> assID=39493 status=9014 reach, conf, 1 event, event_reach,
> srcadr=windows-dc-serverA, srcport=123, dstadr=10.x.y.z,
> dstport=123, leap=00, stratum=4, precision=-6, rootdelay=31.250,
> rootdispersion=10285.095, refid=10.x.v.1, reach=377, unreach=0,

Same problem here, too.

Steve Kostecke <kostecke at ntp.org>
NTP Public Services Project - http://support.ntp.org/

More information about the questions mailing list