Hi, Harlan:
I've also tried "sntp -d -S 10.204.134.250" on the embedded system, and got
the following result:
"sntp [email protected] Thu Feb 16 09:54:19 UTC 2017 (1)
No ipv6 support available, forcing ipv4
kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or
directory
handle_lookup(10.204.134.250,0x2)
move_fd: estimated max descriptors: 1024, initial socket boundary: 16
sntp sendpkt: Sending packet to 10.204.134.250:123 ...
Packet sent.
sock_cb: 10.204.134.250 10.204.134.250:123
1970-01-01 19:25:26.407448 (-0100) +1487240461.716791 +/- 991493641.281683
10.204.134.250 s3 no-leap"
The sntp version is 4.2.8p8.
After a while, the date is still not synced.
By the way, when I set my own pc's date to an incorrect date, then use the
"/usr/sbin/sntp -s -l /tmp/sntp.log 10.204.134.250", the time is synced to the
right time very quickly.
I used sntp because this is early requirement from customers, ntpd, ntpdate
also used and these are alternative, we need to make sure all of them work.
Thanks
Best regards,
Catherine
________________________________________
From: Harlan Stenn <[email protected]>
Sent: Friday, February 17, 2017 12:07 PM
To: Wei, Catherine
Cc: [email protected]
Subject: Re: [Pool] problem about sntp
"Wei, Catherine" writes:
> Hello:
>
> I met an sntp sync time problem. Not sure if it's related to the upgrade
> of ntp. I logged on to a linux embedded box as root, and the time is
>
> "Thu Jan 1 16:10:15 CET 1970"
>
>
> Then I used sntp command:
>
> "/usr/sbin/sntp -l /tmp/sntp.log -t 10 10.204.134.250 -s"
>
>
> I got the following result:
>
> "
>
> sntp [email protected] Thu Feb 16 09:54:19 UTC 2017 (1)
> kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or d
> irectory
> 1970-01-01 16:04:55.269888 (-0100) +1487240461.813365 +/- 991493641.349652 10
> .204.134.250 s3 no-leap?
>
> "
>
>
> Considering the warning in the second line, I did some research and it was ju
> st a file used for the persistent history of KoD??, it just types a warning.
> I don't think this will affect the time sync.
It is just a warning and will not affecet time sync.
> According to the last line in the result, it prints out the offset in seconds
> , it seems that the print result is good, but the system time is not synced a
> fter
You used -s, which slews the correction. The correction is underway,
but a 500ppm slew corrects a 1 second change in about 33 minutes. So
it's gonna take a while.
I'm not sure why you're using sntp instead of running ntpd, but you
might want to use -Ss instead.
H
--
> I used the sntp command.
>
>
> Can anyone helps me with that? Appreciate it. It bothered me for several days
> . Thank you very much.
>
>
>
>
> Catherine,
>
> Best regards
> _______________________________________________
> pool mailing list
> [email protected]
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.ntp.org%2Flistinfo%2Fpool&data=01%7C01%7CCatherine.Wei%40arris.com%7C8ade3ec110e04b1cd68108d456ea7511%7Cf27929ade5544d55837ac561519c3091%7C1&sdata=gBaPB4rsWRwbxFhmB0mb4guLTgtjkCsg47F%2Foet0T5Q%3D&reserved=0
>
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
