Openntpd 3.7 client syncing with opennpd 3.6 server, any issues?

[Erling Ringen Elvsrud]

to den 22.06.2006 klokka 12:46 (+0200) skreiv Erling Ringen Elvsrud:
> Hello,
> 
> I have the following configuration:
> 
> 3 Servers running openntpd:
> 
> ntp1	Openntpd 3.6.1p1-2 (Debian Stable)
> ntp2	Openntpd 3.6.1p1-2 (Debian Stable)
> ntp3	Openntpd 3.6.1p1-2 (Debian Stable)
> 
> Various clients running Ubuntu Dapper and Openntpd 3.7p1-1ubuntu1.
> 
> According to syslog ntp1-ntp3 synchronizes time between each other
> sucessfully (I have added Server ntp1 ntp2 in /etc/openntpd/ntpd.conf on
> Server 3, and corresponding setup on Server1 and Server2).
> 
> But,
> 
> If I run: ntpd -d on a Dapper client I get these messages:
> 
> reply from 192.168.1.32: not synced, next query 625s
> reply from 192.168.1.32: not synced, next query 625s
> reply from 192.168.1.32: not synced, next query 625s
> reply from 192.168.1.32: not synced, next query 625s
> reply from 192.168.1.32: not synced, next query 625s

I Accidentally sent this e-mail a bit early. The log output should be:

reply from 192.168.1.32: not synced, next query 625s
reply from 192.168.1.31: not synced, next query 659s
reply from 192.168.1.30: not synced, next query 652s

such log messages are repeated over and over. The 3 ip's are of
ntp1-ntp3 described earlier.

I'm pretty confident that the setup of the servers are OK as they sync
with the other servers (get "adjusting clock..." messages in syslog)

If anyone is aware of incompabilities between OpenNTPD 3.6 and 3.7 or
any other causes of this problem please reply.

Thanks,

Erling Ringen Elvsrud