[Voyage-linux] ntpdate set time forward on multiple interfaces
Teco Boot
(spam-protected)
Sat Feb 5 06:02:58 HKT 2011
On daily voyage, on Alix2, I see a problem with ntpdate (if-up.d)
Jan 1 00:01:31 AHR-101-003 kernel: [ 31.525815] ath0: no IPv6 routers present
Feb 4 21:42:51 AHR-101-003 ntpdate[1438]: step time server 213.239.154.12 offset 350170879.769154 sec
Feb 4 21:42:51 AHR-101-003 kernel: [ 31.969750] eth0: no IPv6 routers present
Mar 11 19:24:12 AHR-101-003 ntpdate[1520]: step time server 194.171.167.130 offset 350170879.823446 sec
root at host:~# date
Fri Mar 11 19:25:18 GMT 2022
root at host:~# ntpdate 213.239.154.12
4 Feb 21:44:28 ntpdate[1754]: step time server 213.239.154.12 offset -350170879.762962 sec
root at host:~# ntpdate 213.239.154.12
4 Feb 21:45:12 ntpdate[1755]: adjust time server 213.239.154.12 offset 0.002778 sec
root at host:~# ntpdate 194.171.167.130
4 Feb 21:45:29 ntpdate[1756]: adjust time server 194.171.167.130 offset -0.000282 sec
Because both eth0 and ath0 comes up in parallel, and both trigger ntpdate, time is set forward twice.
After install of liblockfile1 and lockfile-progs, problem is solved.
Jan 1 00:17:45 AHR-101-003 kernel: [ 29.345156] eth0: no IPv6 routers present
Feb 4 21:59:05 AHR-101-003 ntpdate[1441]: step time server 192.87.36.4 offset 350170879.844205 sec
Feb 4 21:59:06 AHR-101-003 kernel: [ 30.258018] ath0: no IPv6 routers present
Feb 4 21:59:21 AHR-101-003 ntpdate[1744]: step time server 192.87.106.3 offset 0.001582 sec
Thanks, Teco
More information about the Voyage-linux
mailing list