Opened 15 years ago

Closed 15 years ago

#1 closed defect (fixed)

ntpd drif file blijft op 0.0000 staan

Reported by: huub Owned by: somebody
Priority: major Milestone:
Keywords: Cc:
Resource needed to fix:

Description

ntpd corrigeert wel de tijd, maar maakt geen ntpd.drift bestand aan, zodat telkens weer een relatief grote correctie moet worden uitgevoerd en de klok onnauwkeurig is.

Er is ook een boodschap 'servers not reachable' die ik niet kan thuisbrengen.

Zie de logfile:
/var/log/ntp.log:

27 Feb 11:20:45 ntpd[8202]: synchronized to 172.20.128.98, stratum 3
27 Feb 11:20:54 ntpd[8202]: time reset +9.127663 s
27 Feb 11:28:22 ntpd[8202]: synchronized to 172.17.8.68, stratum 3
27 Feb 11:28:52 ntpd[8202]: no servers reachable
28 Feb 18:47:23 ntpd[8202]: synchronized to 172.20.128.98, stratum 3
28 Feb 18:53:52 ntpd[8202]: time reset +388.824812 s
28 Feb 19:00:02 ntpd[8202]: synchronized to 172.17.8.68, stratum 3
28 Feb 19:00:16 ntpd[8202]: no servers reachable
28 Feb 19:01:07 ntpd[8202]: synchronized to 172.20.128.98, stratum 3
28 Feb 19:02:13 ntpd[8202]: no servers reachable
1 Mar 01:44:01 ntpd[8202]: synchronized to 172.20.128.98, stratum 3
1 Mar 01:45:25 ntpd[8202]: time reset +84.560951 s
1 Mar 01:56:50 ntpd[8202]: synchronized to 172.20.128.98, stratum 3
1 Mar 01:57:30 ntpd[8202]: no servers reachable
1 Mar 09:39:12 ntpd[8202]: synchronized to 172.20.128.98, stratum 3
1 Mar 09:40:50 ntpd[8202]: time reset +97.666245 s
1 Mar 09:48:28 ntpd[8202]: synchronized to 172.20.128.98, stratum 3
1 Mar 09:49:22 ntpd[8202]: no servers reachable

Change History (2)

comment:1 by huub, 15 years ago

[root@CNodeHuub /etc/rc.d]# ntpq -c pe

remote refid st t when poll reach delay offset jitter

==============================================================================

proxy1.wLeiden. 82.94.235.106 3 u 5 64 1 9.756 248613. 0.015
proxy2.wLeiden. .INIT. 16 u 4 64 0 0.000 0.000 0.000
proxy3.wLeiden. 194.109.22.18 3 u 3 64 1 23.290 248617. 0.015
LOCAL(0) .LOCL. 5 l 2 64 1 0.000 0.000 0.015

[root@CNodeHuub /etc/rc.d]# cat /var/db/ntp.drift
0.000

[root@CNodeHuub /etc/rc.d]# killall ntpd
[root@CNodeHuub /etc/rc.d]# date
Mon Mar 2 13:49:21 UTC 2009

[root@CNodeHuub /etc/rc.d]# ntpdate proxy1

2 Mar 13:53:41 ntpdate[8391]: step time server 172.17.8.68 offset 249.021483 sec

[root@CNodeHuub /etc/rc.d]# date
Mon Mar 2 13:53:46 UTC 2009

[root@CNodeHuub /etc/rc.d]# ./ntpd start
Starting ntpd.
[root@CNodeHuub /etc/rc.d]#

ntpdate corrigeert de tijd dus wel aan de hand van timeserver proxy1 in dit geval (4 minuten vooruit gezet).

comment:2 by tim, 15 years ago

Resolution: fixed
Status: newclosed
version: 1.00.9.2

Probleem waarschijnlijk gerelateerd aan de Soekris NET4521. Opgelost na het toevoegen
van CPU_ELAN kernel optie.


Note: See TracTickets for help on using tickets.