[ntp:questions] Not being able to sync the embedded target (client) with the host (server)

William Unruh unruh at invalid.ca
Fri Mar 14 19:47:11 UTC 2014


On 2014-03-14, Laszlo Papp <lpapp at kde.org> wrote:
> Hi,
>
> I was told that this would not be a bug, although I could not figure
> out yet why it is not working. As far as I know, this should work
> simply by putting the following two lines into the client
> configuration:
>
> driftfile /etc/ntp.drift
> server 192.168.A.B iburst

Is that literal or are A and B really numbers.
What are you getting the various log files (you had better put in some
lines to tell ntpd to use log files. )

>
> Yet, the time is not getting sync'd. This is the server configuration, fwiw:
>
> server 0.pool.ntp.org iburst
> server 1.pool.ntp.org iburst
> server 2.pool.ntp.org iburst
> server 3.pool.ntp.org iburst
>
> # restrict default kod nomodify notrap nopeer noquery
> # restrict -6 default kod nomodify notrap nopeer noquery

Always remove all lines that are not absolutely necessary. 

>
> restrict 192.168.0.0 mask 255.255.255.0 nomodify
>
> restrict 127.0.0.1
> restrict -6 ::1
>
> driftfile /var/lib/ntp/ntp.drift
> logfile /var/log/ntp.log
>
> I do not see any error in the syslog either. I have tried to use "ntpd
> -q" for a one-shot set without much luck. I am probably doing
> something fundamentally wrong, but I was not able to figure out yet.

statsdir /var/log/ntp/
statistics peerstats
statistics loopstats

will give some info.

>
> Cheers, L.



More information about the questions mailing list