Re: ntpd not synching
On Wed, 28 Mar 2007, [EMAIL PROTECTED] wrote: hi, On Tue, Mar 27, 2007 at 01:49:16PM +0200, Otto Moerbeek wrote: It looks like your clock drifts more that ntpd can compensate. Please share some details on your setup, like the dmesg. Also, if you remove the drift file, you must reboot, since otherwise the existing frequency compensations stays in effect. ok, i cleared the drift-file and rebooted. as near as i can figure (i had to boot multiple times, and unclean at that) this is what happend slightly bfore/during/after the last boot (the times are so screwed i can't really make it out). Yep, this configrms it. Your clock is drifting so much that ntpd can't keep up. I'm afraid there's not a lot I can do about that. -Otto Mar 28 20:12:46 ntpd[6515]: adjusting local clock by 950.304366s Mar 28 20:17:11 ntpd[6515]: adjusting local clock by 954.223055s Mar 28 22:53:00 ntpd[18691]: ntp engine ready Mar 28 20:49:13 ntpd[14539]: set local clock to Wed Mar 28 20:49:13 CEST 2007 (offset -7427.749161s) Mar 28 20:49:13 ntpd[18691]: reply from 213.246.63.72: negative delay -7427.686509s, next query 3068s Mar 28 20:49:13 ntpd[18691]: reply from 62.220.226.2: negative delay -7427.684053s, next query 3199s Mar 28 20:49:13 ntpd[18691]: reply from 149.156.70.5: negative delay -7427.676747s, next query 3149s Mar 28 20:49:13 ntpd[18691]: reply from 193.11.184.180: negative delay -7427.676303s, next query 3136s Mar 28 20:49:13 ntpd[18691]: reply from 194.215.7.39: not synced, next query 3052s Mar 28 20:49:13 ntpd[18691]: reply from 128.241.238.31: negative delay -7427.633371s, next query 3083s Mar 28 20:49:13 savecore: no core dump Mar 28 20:58:54 ntpd[3522]: peer 80.240.210.253 now valid [peers snipped] Mar 28 20:59:57 ntpd[31863]: adjusting local clock by 2.284285s Mar 28 21:02:37 ntpd[18773]: ntp engine ready Mar 28 21:02:37 ntpd[18773]: reply from 194.215.7.39: not synced, next query 3110s Mar 28 21:02:37 savecore: no core dump Mar 28 21:02:52 ntpd[18773]: peer 217.150.242.8 now valid Mar 28 21:02:59 ntpd[18773]: peer 213.246.63.72 now valid Mar 28 21:02:59 ntpd[18773]: peer 193.11.184.180 now valid Mar 28 21:02:59 ntpd[18773]: peer 128.241.238.31 now valid Mar 28 21:03:00 ntpd[18773]: peer 149.156.70.5 now valid Mar 28 21:03:03 ntpd[18773]: peer 62.220.226.2 now valid Mar 28 21:03:57 ntpd[2354]: adjusting local clock by 6.573991s Mar 28 21:06:04 ntpd[2354]: adjusting local clock by 3.905197s Mar 28 21:08:37 ntpd[2354]: adjusting local clock by 8.475628s Mar 28 21:08:37 ntpd[18773]: clock is now synced Mar 28 21:10:49 ntpd[2354]: adjusting local clock by 8.951453s Mar 28 21:10:49 ntpd[18773]: clock is now unsynced Mar 28 21:15:06 ntpd[2354]: adjusting local clock by 12.813542s Mar 28 21:15:06 ntpd[18773]: clock is now synced Mar 28 21:19:15 ntpd[2354]: adjusting local clock by 15.447946s Mar 28 21:19:15 ntpd[18773]: clock is now unsynced Mar 28 21:23:05 ntpd[2354]: adjusting local clock by 15.624800s Mar 28 21:23:10 ntpd[18773]: peer 213.246.63.72 now invalid Mar 28 21:25:45 ntpd[2354]: adjusting local clock by 16.648412s Mar 28 21:27:49 ntpd[2354]: adjusting local clock by 20.718507s Mar 28 21:31:04 ntpd[2354]: adjusting local clock by 16.498430s Mar 28 21:33:13 ntpd[2354]: adjusting local clock by 20.223130s Mar 28 21:35:57 ntpd[2354]: adjusting local clock by 20.095667s as i write this, the local clock is already 29 seconds behind what 'rdate -p pool.ntp.org' reports. dmesg : OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: VIA Esther processor 1500MHz (CentaurHauls 686-class) 1.51 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3 cpu0: RNG AES AES-CTR SHA1 SHA256 RSA real mem = 468152320 (457180K) avail mem = 418967552 (409148K) using 4256 buffers containing 23511040 bytes (22960K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(d9) BIOS, date 09/15/06, BIOS32 rev. 0 @ 0xfa960, SMBIOS rev. 2.3 @ 0xf (33 entries) apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xcce4 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfcc20/192 (10 entries) pcibios0: bad IRQ table checksum pcibios0: PCI BIOS has 10 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 5 10 11 15 pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT8237 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xfc00 0xd/0x1000 0xd1000/0x1000 0xd2000/0x5000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA CN700 Host rev 0x00 pchb1 at pci0 dev 0 function 1 VIA CN700 Host rev 0x00 pchb2 at pci0 dev 0 function 2 VIA CN700 Host rev 0x00 pchb3 at pci0 dev 0 function 3
Re: ntpd not synching
On Thu, Mar 29, 2007 at 09:13:56AM +0200, Otto Moerbeek wrote: On Wed, 28 Mar 2007, [EMAIL PROTECTED] wrote: hi, On Tue, Mar 27, 2007 at 01:49:16PM +0200, Otto Moerbeek wrote: It looks like your clock drifts more that ntpd can compensate. Please share some details on your setup, like the dmesg. Also, if you remove the drift file, you must reboot, since otherwise the existing frequency compensations stays in effect. ok, i cleared the drift-file and rebooted. as near as i can figure (i had to boot multiple times, and unclean at that) this is what happend slightly bfore/during/after the last boot (the times are so screwed i can't really make it out). Yep, this configrms it. Your clock is drifting so much that ntpd can't keep up. I'm afraid there's not a lot I can do about that. Unless I'm very confused, though, repeated use of something like rdate(8) will work, or, rather, 'work'... Joachim
Re: ntpd not synching
hi, On Tue, Mar 27, 2007 at 01:49:16PM +0200, Otto Moerbeek wrote: It looks like your clock drifts more that ntpd can compensate. Please share some details on your setup, like the dmesg. Also, if you remove the drift file, you must reboot, since otherwise the existing frequency compensations stays in effect. ok, i cleared the drift-file and rebooted. as near as i can figure (i had to boot multiple times, and unclean at that) this is what happend slightly bfore/during/after the last boot (the times are so screwed i can't really make it out). Mar 28 20:12:46 ntpd[6515]: adjusting local clock by 950.304366s Mar 28 20:17:11 ntpd[6515]: adjusting local clock by 954.223055s Mar 28 22:53:00 ntpd[18691]: ntp engine ready Mar 28 20:49:13 ntpd[14539]: set local clock to Wed Mar 28 20:49:13 CEST 2007 (offset -7427.749161s) Mar 28 20:49:13 ntpd[18691]: reply from 213.246.63.72: negative delay -7427.686509s, next query 3068s Mar 28 20:49:13 ntpd[18691]: reply from 62.220.226.2: negative delay -7427.684053s, next query 3199s Mar 28 20:49:13 ntpd[18691]: reply from 149.156.70.5: negative delay -7427.676747s, next query 3149s Mar 28 20:49:13 ntpd[18691]: reply from 193.11.184.180: negative delay -7427.676303s, next query 3136s Mar 28 20:49:13 ntpd[18691]: reply from 194.215.7.39: not synced, next query 3052s Mar 28 20:49:13 ntpd[18691]: reply from 128.241.238.31: negative delay -7427.633371s, next query 3083s Mar 28 20:49:13 savecore: no core dump Mar 28 20:58:54 ntpd[3522]: peer 80.240.210.253 now valid [peers snipped] Mar 28 20:59:57 ntpd[31863]: adjusting local clock by 2.284285s Mar 28 21:02:37 ntpd[18773]: ntp engine ready Mar 28 21:02:37 ntpd[18773]: reply from 194.215.7.39: not synced, next query 3110s Mar 28 21:02:37 savecore: no core dump Mar 28 21:02:52 ntpd[18773]: peer 217.150.242.8 now valid Mar 28 21:02:59 ntpd[18773]: peer 213.246.63.72 now valid Mar 28 21:02:59 ntpd[18773]: peer 193.11.184.180 now valid Mar 28 21:02:59 ntpd[18773]: peer 128.241.238.31 now valid Mar 28 21:03:00 ntpd[18773]: peer 149.156.70.5 now valid Mar 28 21:03:03 ntpd[18773]: peer 62.220.226.2 now valid Mar 28 21:03:57 ntpd[2354]: adjusting local clock by 6.573991s Mar 28 21:06:04 ntpd[2354]: adjusting local clock by 3.905197s Mar 28 21:08:37 ntpd[2354]: adjusting local clock by 8.475628s Mar 28 21:08:37 ntpd[18773]: clock is now synced Mar 28 21:10:49 ntpd[2354]: adjusting local clock by 8.951453s Mar 28 21:10:49 ntpd[18773]: clock is now unsynced Mar 28 21:15:06 ntpd[2354]: adjusting local clock by 12.813542s Mar 28 21:15:06 ntpd[18773]: clock is now synced Mar 28 21:19:15 ntpd[2354]: adjusting local clock by 15.447946s Mar 28 21:19:15 ntpd[18773]: clock is now unsynced Mar 28 21:23:05 ntpd[2354]: adjusting local clock by 15.624800s Mar 28 21:23:10 ntpd[18773]: peer 213.246.63.72 now invalid Mar 28 21:25:45 ntpd[2354]: adjusting local clock by 16.648412s Mar 28 21:27:49 ntpd[2354]: adjusting local clock by 20.718507s Mar 28 21:31:04 ntpd[2354]: adjusting local clock by 16.498430s Mar 28 21:33:13 ntpd[2354]: adjusting local clock by 20.223130s Mar 28 21:35:57 ntpd[2354]: adjusting local clock by 20.095667s as i write this, the local clock is already 29 seconds behind what 'rdate -p pool.ntp.org' reports. dmesg : OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: VIA Esther processor 1500MHz (CentaurHauls 686-class) 1.51 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3 cpu0: RNG AES AES-CTR SHA1 SHA256 RSA real mem = 468152320 (457180K) avail mem = 418967552 (409148K) using 4256 buffers containing 23511040 bytes (22960K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(d9) BIOS, date 09/15/06, BIOS32 rev. 0 @ 0xfa960, SMBIOS rev. 2.3 @ 0xf (33 entries) apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xcce4 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfcc20/192 (10 entries) pcibios0: bad IRQ table checksum pcibios0: PCI BIOS has 10 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 5 10 11 15 pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT8237 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xfc00 0xd/0x1000 0xd1000/0x1000 0xd2000/0x5000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA CN700 Host rev 0x00 pchb1 at pci0 dev 0 function 1 VIA CN700 Host rev 0x00 pchb2 at pci0 dev 0 function 2 VIA CN700 Host rev 0x00 pchb3 at pci0 dev 0 function 3 VIA PT890 Host rev 0x00 pchb4 at pci0 dev 0 function 4 VIA CN700 Host rev 0x00 pchb5 at pci0 dev 0 function 7 VIA CN700 Host rev 0x00 ppb0 at pci0 dev 1 function 0 VIA VT8377 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 VIA S3 Unichrome PRO IGP rev 0x01: aperture at
ntpd not synching
hi, i'm trying to keep my local clock synched through ntpd. i used to do that with ntpdate, but since ntpd is available in a standard install i thought i'd try that. i start ntpd at boot, with added -s to synch the clock right away. however, after that it starts moving the clock backwards. restarting ntpd just makes it repeat the process : [old ntpd, started at boot] Mar 27 08:46:58 ntpd[20919]: adjusting local clock by 9642.320276s Mar 27 08:49:06 ntpd[20919]: adjusting local clock by 2143.405987s Mar 27 08:50:07 ntpd[20919]: adjusting local clock by 2142.248606s Mar 27 08:51:42 ntpd[20919]: adjusting local clock by 9644.027785s Mar 27 08:54:45 ntpd[1871]: ntp_dispatch_imsg in ntp engine: pipe closed Mar 27 08:54:45 ntpd[1871]: ntp engine exiting [restart] Mar 27 08:55:02 ntpd[2426]: ntp engine ready Mar 27 11:35:52 ntpd[16439]: set local clock to Tue Mar 27 11:35:52 CEST 2007 (offset 9649.641093s) Mar 27 11:36:09 ntpd[2426]: peer 194.146.227.112 now valid [some more peers snipped] Mar 27 11:37:33 ntpd[6515]: adjusting local clock by 1.288053s Mar 27 11:40:10 ntpd[6515]: adjusting local clock by 6.464148s Mar 27 11:40:10 ntpd[2426]: clock is now synced Mar 27 11:44:23 ntpd[6515]: adjusting local clock by 10.656797s Mar 27 11:46:36 ntpd[6515]: adjusting local clock by 13.004900s Mar 27 11:46:36 ntpd[2426]: clock is now unsynced Mar 27 11:49:17 ntpd[6515]: adjusting local clock by 11.683026s Mar 27 11:53:39 ntpd[6515]: adjusting local clock by 15.193740s (if left alone, this adjustment will increase perpetually). timezone is set correctly : $ ls -la /etc/localtime lrwxr-xr-x 1 root wheel 36 Dec 2 00:38 /etc/localtime - /usr/share/zoneinfo/Europe/Amsterdam $ date Tue Mar 27 12:25:30 CEST 2007 any ideas ? it _has_ managed to keep the clock synched once, but after a reboot it went completely bonkers. i tried removing the drift-file and restarting it as well, to no avail. i'm running 4.0-release, and the provided ntpd. -- CUL8R, Peter.
Re: ntpd not synching
On Tue, 27 Mar 2007, [EMAIL PROTECTED] wrote: hi, i'm trying to keep my local clock synched through ntpd. i used to do that with ntpdate, but since ntpd is available in a standard install i thought i'd try that. i start ntpd at boot, with added -s to synch the clock right away. however, after that it starts moving the clock backwards. restarting ntpd just makes it repeat the process : [old ntpd, started at boot] Mar 27 08:46:58 ntpd[20919]: adjusting local clock by 9642.320276s Mar 27 08:49:06 ntpd[20919]: adjusting local clock by 2143.405987s Mar 27 08:50:07 ntpd[20919]: adjusting local clock by 2142.248606s Mar 27 08:51:42 ntpd[20919]: adjusting local clock by 9644.027785s Mar 27 08:54:45 ntpd[1871]: ntp_dispatch_imsg in ntp engine: pipe closed Mar 27 08:54:45 ntpd[1871]: ntp engine exiting [restart] Mar 27 08:55:02 ntpd[2426]: ntp engine ready Mar 27 11:35:52 ntpd[16439]: set local clock to Tue Mar 27 11:35:52 CEST 2007 (offset 9649.641093s) Mar 27 11:36:09 ntpd[2426]: peer 194.146.227.112 now valid [some more peers snipped] Mar 27 11:37:33 ntpd[6515]: adjusting local clock by 1.288053s Mar 27 11:40:10 ntpd[6515]: adjusting local clock by 6.464148s Mar 27 11:40:10 ntpd[2426]: clock is now synced Mar 27 11:44:23 ntpd[6515]: adjusting local clock by 10.656797s Mar 27 11:46:36 ntpd[6515]: adjusting local clock by 13.004900s Mar 27 11:46:36 ntpd[2426]: clock is now unsynced Mar 27 11:49:17 ntpd[6515]: adjusting local clock by 11.683026s Mar 27 11:53:39 ntpd[6515]: adjusting local clock by 15.193740s (if left alone, this adjustment will increase perpetually). timezone is set correctly : $ ls -la /etc/localtime lrwxr-xr-x 1 root wheel 36 Dec 2 00:38 /etc/localtime - /usr/share/zoneinfo/Europe/Amsterdam $ date Tue Mar 27 12:25:30 CEST 2007 any ideas ? it _has_ managed to keep the clock synched once, but after a reboot it went completely bonkers. i tried removing the drift-file and restarting it as well, to no avail. i'm running 4.0-release, and the provided ntpd. -- CUL8R, Peter. It looks like your clock drifts more that ntpd can compensate. Please share some details on your setup, like the dmesg. Also, if you remove the drift file, you must reboot, since otherwise the existing frequency compensations stays in effect. -Otto
