Re: [ntp:questions] Time server question
On 2019-06-21, David Woolley wrote: > On 21/06/2019 12:26, Thomas Laus wrote: >> Will either isolation solution have direct access to the computer >> CPU? The GPS clock will need the ability to directly adjust the >> frequency of the CPU to achieve expected results for a Stratum 1 >> serve > > I'm not aware of anything in ntpd that directly adjusts the CPU > frequency and there generally isn't any fine grained way of doing that. > ntpd normally works by adjusting how many cycles of a fixed frequency > represent a certain time period, and that is a software operation. > I guess that I should have stated this reply a little differently. I meant to say that ntpd will need direct access to the hardware that it runs on. That means a hardware serial port for pulse per second and the running system clock frequency. The ntpd program does not perform well when running on a virtual machine nor in a isolated security environment similar to a freebsd jail. My advice to the original poster is to get ntpd running as a stratum 1 source and then connect it to the internet with the fewest number of inter- mediate hops in between. I doubt that this is possible if the Stratum 1 time source can be connected through any buffer device to the internet and still serve Stratum 1 time. -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Time server question
On 2019-06-20, Chris wrote: > Have a couple of surplus gps based ntp servers that have been > used for time sync in the lab for few years. They are on a UPS > with several hours backup and seems like a good idea to use > them to contribute to the ntp global network. > > Don't want to expose them directly to the net, so plan to > isolate them, either via a Solaris zone or > FreeBSD jail. This will have 2 network interfaces, ntp subnet > facing and the other to internet via the firewall. The ntp > side will run ntp client, internet side runs ntp server. > Will either isolation solution have direct access to the computer CPU? The GPS clock will need the ability to directly adjust the frequency of the CPU to achieve expected results for a Stratum 1 server. > Question is, will such an intermediate machine degrade the > time served, or will it still be reported as a stratum 1 > source. Seems a waste otherwise. > > ntpq -p currently reports: > > remote refid st t when poll reach delay offset disp >= > *chronos .GPS. 1 u 23 64 377 0.18 -0.0180.03 > +nts100.GPS. 1 u 21 64 377 0.46 -0.0710.08 > That looks like a good billboard and should make a good S1 time server if you can resolve your concerns about making it available as an internet host. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] Refclock Oncore Driver Change
Group: The Motorola Oncore receiver has recently become non-usable because of the recent GPS week rollover. The receiver year field is limited by the receiver to the years from 1988 to 2018. The current driver is not able to write the year 2019 successfully. I have looked overr the refclock_oncore.c driver program and have some thoughts. The is a section of the code that makes a conversion of Unix time to GPS time. There is a 70 year constant applied to the message sent to the receiver and received from the refclock. I think that this constant could be 'fudged' to either add or subtract hex 0x24ea (decimal 619315200) for the number of seconds in a 1024 GPS week. I looked at the date in my Oncore and converted it to Unix time. I subtracted this factor from my system date and the numbers matched. I send an email to the person that last made a change to the refclock_oncore driver program and have not received a reply yet. I ask this group if my idea has any hidden 'gotchas'. The Oncore driver already has sections for the different models. I am proposing using the conversion factor for the 6 and 8 channel receivers and leave the code alone for the M12 receiver. Are there any model VT, VP, GT, UT receivers that handled the recent rollover correctly? Are there any M12 receivers that need this fix? The code is a little complicated in ntp_unixtime.h because of the size of the number is greater than a 32 bit INT and my 'C' skills are a little rusty. I plan on working on this next week and see if my idea is valid. It would be great to have my Oncore back in operation for another 19 years and not requiring a replacement receiver. I am going to concentrate on making the chage to the ntp_unixtime.h file because other refclocks might require a similar fix. Am I on the right path or is there a better way? The receiver will still think that the year is in the correct range, but all date in and out of ntp will be correct. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Mu whole Internet crashes when server is in the pool rotation
On 2019-04-27, jelisko...@gmail.com wrote: > NTP server is working properly, I wanted to join the official pool. My score > is 19.2 which is excellent, but my whole internet crashes ! > > Even if I choose the lowest speed it is same. If I make schedule for deletion > the server I presume is immediately remove from pool rotation everything is > back to normal. > > > My router is properly configured (Linksys E4200 with DDWRT) for the server, > the server is Fedora installed on VMware ESXi 6.7 U2. > > It is like UDP flood of NTP requests that crashes my Internet. > > In config file I have the lines that prevents KOD (Kiss of Death) > > restrict -4 default kod notrap nomodify nopeer noquery limited > restrict -6 default kod notrap nomodify nopeer noquery limited > > > Have someone dealt with this or similar issue ? > In general, timekeeping accuracy does not do well on virtual machines. NTP prefers direct control of the CPU frequency and not through a VM. VMware has published papers on timekeeping for local clients, but I have never seen any reports on the performance of any pool servers that are running on VM's. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] does this make sense?
On 8/13/18 10:09 AM, Steven Sommars wrote: > Search for: CDMA shutdown > > CDMA NTP servers lack an automated leap second mechanism, as far as I > can tell. > My CDMA experience dealt with an Endrun Tempus LX receiver only. It received and used the leap second information that was sent along with the rest of the CDMA time broadcast transmissions. It has been a long time since setting up that receiver and my memory might be a little foggy. I seem to remember that there was also a way to enter the IERS file manually. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] What is the mean of below output?
On 2018-08-06, ashishchugh@gmail.com wrote: > This time i made some changes and i can see below output at this time i am > using aws time sync ip on my ntp.conf > > ntpa -p > > output - > > remote refid st t when poll reach delay offset jitter >== > *169.254.169.123 10.25.3.142 3 u 350 512 3770.2250.372 0.120 > pugot.canonical .STEP. 16 u- 102400.0000.000 0.000 > That billboard indicates that your ntp server has reached and synchronized with 169.254.169.123. The other server 'pugot.canonical' has not been seen by your instance. It's reach number is 0. You have a good start on your ntp operation. You should have a minimum of 4 servers for good timekeeping so that a bad poll reply can be out voted by the other servers. The pool server directive is designed to give you a fair number of good servers automatically and will dynamically replace them as needed. One 'pool' directive is all that is required. It will be fanned out at the other end to supply a minimum of 4 IP addresses for your server to synchronize. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] What is the mean of below output?
On 2018-08-06, ashishchugh@gmail.com wrote: > Hi > > I am facing time drifting problem in my linux , i install ntp. first of all i > am unable to execute ntpstat command as it is saying command not found. > > Then i execute ntpq -p and can see below ouuput > > remote refid st t when poll reach delay offset jitter >== > time.tritn.com .INIT. 16 u- 102400.0000.000 0.000 > ntp1.wiktel.com .INIT. 16 u- 102400.0000.000 0.000 > clocka.ntpjs.or .INIT. 16 u- 102400.0000.000 0.000 > ntp.your.org.INIT. 16 u- 102400.0000.000 0.000 > chilipepper.can .INIT. 16 u- 102400.0000.000 0.000 > > But i am unable to understand what is the mean of this output. > > Is that mean my system time is synced with ntp and at current time there is > no time delay in my local linux. > This billboard shows that none of your ntp servers are reachable from your EC2 instance. Try turning off all of the crypto configuration. You will want to make things operate with a simple configuration first and then add features to a working system. Use just the suggested server: pool pool.ntp.org As your only one and not use the Amazon pool to start. If it works and the associations look good, then there is something incorrect on the EC2 side. > 2- May i execute the ntp every time or it will run at back end automatically. > > > Local time: Mon 2018-08-06 07:15:02 UTC > Universal time: Mon 2018-08-06 07:15:02 UTC > Timezone: Etc/UTC (UTC, +) > NTP enabled: yes > NTP synchronized: no > RTC in local TZ: no > DST active: n/a > NTP is not working on this instance. Get it to syncronize first and then ask your questions/ Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How can i make sure that how much time ntp is adjusting one day
On 2018-08-06, aashish.ch...@fonantrix.com wrote: > here is my ntp.conf file. >... > > and destination ip is (169.254.169.123) > > I am using ntp on my aws ec2 instance. > The IP address 169.254.169.123 is an IANA reserved non-routable internal one. Is this address one that is local to your Amazon EC2 instance region and availability location? When you send a query: ntpq -c as Does the billboard show that address as reachable? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] does this make sense?
On 2018-04-04, Maria Iano wrote: > I'm purchasing ntp appliances to put into three datacenters. Does it make > sense to purchase two that use GPS and two that use WWVB, and configure them > as peers? The USA Bureau of Time Standards has a link for timing receiver vendors: https://www.nist.gov/pml/time-and-frequency-division/time-services/manufacturers-time-and-frequency-receivers There are a few manufacturers of CDMA systems that receive the timing signals from the USA cellphone systems. They have a high degree of accuracy and are a better choice than WWVB in most cases. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] WWV Outage 2/21/2017 & 2/22/2017
NOTICE Due to an electrical up-grade, Radio Station WWV will be off the air on all frequencies on February 21 and 22, 2017. The outages will occur between 7:00 AM and 5:00 PM Mountain Standard Time, and will not exceed 8 hours in duration each day. https://www.nist.gov/pml/time-and-frequency-division/time-services/wwv-broadcast-outages Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Silly question.
On 2013-12-15, Hal Murray hal-use...@ip-64-139-1-69.sjc.megapath.net wrote: But, I don't know, nor can find out where the newly built newer version ntpd was placed, so I can change that variable above. If you built it from a port, it gets installed in /usr/local/bin. The default system built ntp programs go in /usr/bin or /usr/sbin. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Strange refid
On 2013-11-12, David Lord sn...@lordynet.org wrote: Are either WWV(various hf) or WWVB(60kHz) still online? David: Thay are all still on the air. http://www.nist.gov/pml/div688/grp40/wwv.cfm Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Help with Oncore PPS
On 2013-08-25, Ron Hahn (EI2JP) ntp-questi...@dhco.org wrote: Hello, I am trying to get an Oncore GPS board to PPS a FreeBSD 8.3 installation. Originally I was using a Sure GPS board and now I want the better Oncore board to be working. From the log output below I am talking to the Oncore board but it is not in particular listening: 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: ONCORE DRIVER -- CONFIGURING 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: state = ONCORE_NO_IDEA 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: Input mode = 2 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: Initializing timing to Assert. 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: HARDPPS Set. 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: SHMEM (size = 3628) is CONFIGURED and available as /var/log/ntpstats/oncore.0 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: state = ONCORE_CHECK_ID 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: Oncore: Resend @@Cj 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: @@Cj 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: COPYRIGHT 1991-1997 MOTOROLA INC. 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SFTW P/N # 98-P36848P 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SOFTWARE VER # 2 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SOFTWARE REV # 2 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SOFTWARE DATE APR 24 1998 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: MODEL #R5122U1112 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: HWDR P/N # 5 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SERIAL # R02YWM 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: MANUFACTUR DATE 8G25 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: This looks like an Oncore UT with version 2.2 firmware. 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: Channels = 8, TRAIM = ON 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: state = ONCORE_CHECK_CHAN 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: Input says chan = -1 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: Model # says chan = 8 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: Testing says chan = 8 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: Usingchan = 8 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: state = ONCORE_HAVE_CHAN 25 Aug 22:52:58 ntpd[22820]: ONCORE[0]: state = ONCORE_TEST_SENT 25 Aug 22:53:05 ntpd[22820]: ONCORE[0]: GPS antenna: OK 25 Aug 22:53:05 ntpd[22820]: ONCORE[0]: state = ONCORE_INIT 25 Aug 22:53:08 ntpd[22820]: ONCORE[0]: Setting Posn from input data 25 Aug 22:53:08 ntpd[22820]: ONCORE[0]: state = ONCORE_ALMANAC . 25 Aug 22:53:13 ntpd[22820]: ONCORE[0]: Initiating hardware 3D site survey 25 Aug 22:53:13 ntpd[22820]: ONCORE[0]: SSstate = ONCORE_SS_HW 25 Aug 22:53:13 ntpd[22820]: ONCORE[0]: PPS Offset is set to 0 ns 25 Aug 22:53:13 ntpd[22820]: ONCORE[0]: Satellite mask angle is 0 degrees 25 Aug 22:53:19 ntpd[22820]: ONCORE[0]: ONCORE: oncore_get_timestamp, error serial pps 25 Aug 22:53:19 ntpd[22820]: ONCORE[0]: ONCORE: oncore_get_timestamp, error serial pps 25 Aug 22:53:20 ntpd[22820]: ONCORE[0]: ONCORE: oncore_get_timestamp, error serial pps 25 Aug 22:53:21 ntpd[22820]: ONCORE[0]: ONCORE: oncore_get_timestamp, error serial pps --- cut here--- ..and the PPS signal is not being heard either, so it is appearing: Can anyone explain to me what is going wrong? I have googled this error for many times now and have not received an answer. It looks like the you got the Motorola Oncore serial side working on your FreeBSD installation. Have you made the devfs.conf entries to link the pps and serial signal to the correct hardware port? Is your hardware port 'real'? Things don't work well with virtual serial ports and USB to serial converters. This is the contents of my /etc/devfs.conf: linkcuad1 oncore.serial.0 linkcuad1 oncore.pps.0 The .pps. tag in your ntpq billboard doesn't show with this driver, you only get one common .gps. for both signals. The driver gets both pps and serial data from your serial port and uses both in the time solution. Your kernel also requires rebuildingwith the addition of: # Enable support for the kernel PLL to use an external PPS signal, # under supervision of [x]ntpd(8) # More info in ntpd documentation: http://www.eecis.udel.edu/~ntp options PPS_SYNC When it all works, the ntpdc will show: ntpdc -c sysi system peer: GPS_ONCORE(0) system peer mode: client leap indicator: 00 stratum: 1 precision:-22 root distance:0.0 s root dispersion: 0.00034 s reference ID: [GPS] reference time: d5c724b8.37c4ecad Tue, Aug 27 2013 9:14:32.217 system flags: auth monitor ntp kernel stats pps jitter: 0.00 s stability:0.000 ppm broadcastdelay: 0.00 s authdelay:0.00 s and ntpdc -c kern pll offset: 6.69e-07 s pll frequency:14.076 ppm maximum error:0.006233 s estimated error: 1e-06 s status: 2107 pll ppsfreq ppstime ppssignal nano pll time constant:4 precision:1e-09
Re: [ntp:questions] IRIG not working with ALSA
On 2013-08-13, Michael Tatarinov kuk...@gmail.com wrote: the conclusion that the IRIG audio reference clock does not work with OSS emulation provided by ALSA. Is this driver still supported? If it is, who is supporting it? according to the bugzilla - David L. Mills The problem is that for kernel PPS support you need kernel 2.6.39 which no longer supports OSS. are you try NetBSD/FreeBSD/OpenBSD? I don't beleive that OpenBSD has kernel pps time support. I am sure that FreeBSD does because I use it. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Thunderbolt at NTP ref clock.
On 2013-07-30, E-Mail Sent to this address will be added to the BlackLists Null@BlackList.Anitech-Systems.invalid wrote: Dave Baxter wrote: In reference to my other thread. THunderbolt monitor/control on Win7 ? Well, as that device seems happy in it's potential new home. I've been poking about the interweb looking for info as to getting the TB used as a reference clock for NTP. I found this page:- http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver29.html That on the face of it, seems to tell me what I need. So, poking arround (no changes yet) my ntp.conf file, I think I need this:- # Trimble Thunderbolt on /dev/gps1 (first serial port) server 127.127.29.1 mode 2 minpoll 4 maxpoll 4 prefer fudge 127.127.29.1 time1 0.020 Years ago when I used a Thunderbolt to provide a local time reference on a Soekris system I found that the PPS pulse was a little too narrow to trigger the Soekris UART. I had to use one of these: http://www.tapr.org/kits_fatpps.html To stretch the pulse for reliability. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Thunderbolt at NTP ref clock.
On 2013-07-31, Thomas Laus lau...@acm.org wrote: The pulse width wasn't adjustable. It was was just on the ragged edge of what the Soekris UART DCD was able to see for pps kernel discipline. It occasonally missed a pulse and that caused some problems for ntp because it had the time solution from the serial port data, but not the pps timestamp that matched. From the Thunderbolt book: 1 PPS: BNC Connector TTL levels into 50 ohm 10 microseconds-wide pulse with the leading edge synchronized to GPS or UTC within 20 nanoseconds (one sigma) in static, time-only mode. The rising time is 20 nanoseconds and the pulse shape is affected by the distributed capacitance of the interface cable/circuit. My Soekris board could not handle something that narrow. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Thunderbolt at NTP ref clock.
On 2013-07-31, unruh un...@invalid.ca wrote: Years ago when I used a Thunderbolt to provide a local time reference on a Soekris system I found that the PPS pulse was a little too narrow to trigger the Soekris UART. I had to use one of these: http://www.tapr.org/kits_fatpps.html And in all those years they still have not figured out what the price is? The web page says price is TBD. There used to be a price listed, I think cost was around $40. What is the trimble pulse width? Are you sure it is not adjustable? Remember that such a pulse stretcher adds latency. If you one want it to 10s of microseconds it is fine. If you are worried about ns it is not. (I guess if you are using a serial port you cannot care about better than 10s of microseconds anyway). The pulse width wasn't adjustable. It was was just on the ragged edge of what the Soekris UART DCD was able to see for pps kernel discipline. It occasonally missed a pulse and that caused some problems for ntp because it had the time solution from the serial port data, but not the pps timestamp that matched. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] ntpd crashing early in startup (memory corruption?)
On 2013-05-09, Garrett Wollman woll...@bimajority.org wrote: Has anyone else experienced a problem with ntpd crashing very early in startup? It looks like a memory corruption issue, or at least the stack is usually corrupt by the time the core file gets written. Frustratingly, I cannot reproduce the problem when the -n flag is given to ntpd. Setting MALLOC_OPTIONS to ADJ also seems to have a beneficial effect, although not for long, but enabling ElectricFence does not make any difference nor does it report any errors. The platform here is FreeBSD/amd64 9.1 with both net/ntp (4.2.6p5) and net/ntp-devel (4.2.7p364) ports. Are the results any different when using the GENERIC kernel? I have had a similar issue when running a stripped down kernal without any modules built or loaded. I never was able to discover the necessary module that needed to be present for a successful ntp when compiling the system source without building all of the modules. I am also running FreeBSD 9.1 on an amd64 system. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] ntpd locks-up on FreeBSD 8.3
On 2013-02-28, Edward T. Mischanko etm1...@hotmail.com wrote: When ntpd loads via rc.d at system start-up it just locks-up. It doesn't finish loading what is in the rc.conf or give me a login prompt. I have to control c out of it to regain control of the computer, but that terminates ntpd. Any help would be appreciated. Is this the 'stock' ntp that ships with FreeBSD 8.3 or did it come from the ports system? Are you running the GENERIC 8.3 kernel or one that you customized? If it is a custom kernel, are you building all of the modules? Is your system am i386, AMD64 or something else? A lot of questions for information that you did not provide in your original post. FreeBSD 8.3 runs fine on my AMD64 system. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] New 60 KHz WWVB Time Format
I have not seen this information posted to this newsgroup. The US NIST radio station WWVB will be changing it's transmission format. The information can be found at: http://www.nist.gov/pml/div688/grp40/wwvb.cfm The old format is still being sent twice a day until the end of January 2013, but the station will only transmit the new phase modulated time code after this month. It is supposed to be compatible with the existing 'Atomic' clocks, but I have some of the original ones that were made in China that are no longer syncing. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Updating NTP on FreeBSD 8.x
On 2012-11-17, David Taylor david-tay...@blueyonder.co.uk.invalid wrote: Pardon my ignorance, but with FreeBSD if I run: # portmaster -a # portmaster net/ntp-devel I appear to get 4.2.7p304, which is not the latest version. Is there something extra I should be doing to get the latest version, or am I reliant on whoever updates the FreeBSD stuff? The FreeBSD port maintainer is the one that keeps up with updating the port when new versions become available. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Motorola Oncore GPS as Stratum 1 source
On 2012-10-18, Mike S mi...@flatsurface.com wrote: re: using gold caps You may wish to consider rechargeable lithium cells, which will give you a more consistent voltage than a capacitor. I'm not sure how voltage sensitive the Oncore boards are for holding data while powered down, but these are what Motorola used in the ones with the on-board battery option. The high Farad capacitor will charge to just a little under supply voltage in about 24H. My Oncore seems to keep the RTC running and the almanac valid for about a month after power off. That part of the Oncore seems to draw in the very low nano-amp range. The capacitor has enough charge after about 3 hours to be useful for short power blips. I also thought about Lithium rechargables in searching for this solution, but found that the high Farad capacitor was a drop in replacment on my TAPR board. It fit in the exact footprint of the coin cell holder and all that I needed to do is replace one resistor with a jumper wire. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Motorola Oncore GPS as Stratum 1 source
On 2012-10-17, Hahn, Ron ron.h...@fmr.com wrote: Colleagues, I am putting together some Motorola Oncore UT+ boards to replace my Sure boards in my ntp servers. I am using this http://www.tapr.org/gps_vpib.html board as the templat for the interface circuits. The circuit calls for a BR2325 battery which I cannot find in the local parts store. Is there a person on this list with experiences of this board design that can tell me what I can substitute for this part? Or maybe it is not necessary? I am not even sure if the battery is necessary but from my experiences the boards go from a cold start whenever power is interrupting. One of my servers is part of the ntp pool so I am needing the rapid recovery if the power is interrupted. My systems are on the UPS so maybe this battery is not required? Ron: I am also using this same board and made a discovery a few years ago that this backup battery discharges over a period of time, normally less than a year and is not available when 'really' needing it. There is a battery charging current available on Pin 3 of your Oncore that can be used to charge a 1.5F 5.5V Gold Capacitor. I used the Digikey part P11063-ND for mine. It will mount in the same loacation as the coin cell. You will need to jumper out R2 (820K) and just connect the high Farad capacitor between pins 1 3 on your Oncore. Watch the polarity! The charging circuit in the Oncore is current limiting and it will take about 12H for enough charge to hold the almanac between powerups. When the capacitor is fully charged, the almanac stays for about a month. You really can't do without a battery. Your almanac information and current date and time is stored in the Oncore RAM. Your GPS location, and other parameters get saved in Flash, but the Oncore will require about 30-40 minutes to recover from a power outage before it can serve up time again. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Two issues updating FreeBSD 8.2 with portmaster
On 2012-09-26, Ron Hahn ron.h...@dhco.org wrote: cd /usr/ports portsnap fetch update portmaster -L ... to see if ntpd will be updated portmaster -a ... update all packages (subsitute for your command for the packages you want to update) I have seen instances where you have to run a make deinstall first to get a package to install properly. Thanks Ron for suggesting portsnap. I have been using FreeBSD and 'cvsupping' before portsnap was developed and had forgotten about it being in the newer releases. Portsnap is a lot easier and cleaner solution to keeping your local ports tree updated. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Two issues updating FreeBSD 8.2 with portmaster
On 2012-09-26, David Taylor david-tay...@blueyonder.co.uk.invalid wrote: I tried to update my FreeBSD 8.2 to the latest NTP development (in excess of 300), but failed on two counts. Am I doing something wrong? 1 - The version obtained was the same as my installed version: ntp-4.2.7p255, whereas the current development version is in excess of ntp-4.2.7p300. The commands I used were: # cd /usr/ports/ports-mgmt/portmaster # portmaster net/ntp-devel Do I need to do something to tell portmaster to update its list of current versions? I had understood this was automatic. Have you updated your ports tree with either csup or cvsup from one of the update servers? I see: PORTVERSION=4.2.7p304 In the ntp-devel port Makefile on my FreeBSD system. The FreeBSD ports system tree requires updating from time to time. 2 - Although this version appears to compile correctly, I got an error message: Making all in tests === Creating a backup package for old version ntp-4.2.7p255 tar: man/man8/ntpsnmpd.8.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 === Package creation failed for ntp-4.2.7p255! === Ignore this error [i] === Abort [a] whereas when I ran this in February this year I don't recall getting the same error. I'm not at all familiar with FreeBSD to know whether this error can be safely ignored, or whether it indicates a significant problem. I was logged in as root at the time. Have you always used portmaster or have some of your programs been installed from packages? It is not a good idea to mix and match because of the way the package builder configures the dependancy options. When you configure a port, the system saves your confiuration options in /var/db/pkg and remembers it the next time that port is built by you. The packages are normally built to include the most common options. You may not want IPV6 support or the docs for the port and 'de-select' it. At a later date you may rebuild the port that was first installed as a package and not have selected the same options as the packager did. This leads to messages like yours. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Public NTP server supporting authentication
On 2012-09-14, anots...@fastmail.fm anots...@fastmail.fm wrote: Some people are interested to use authenticated NTP for their linux distributions. [1] [2] Obviously an identity scheme, where NTP server has its own private and public key and all users need to have the the NTP public keys is required. Typical private/public key scheme, just like gpg. Anything else can not work if the wide public is supposed to verify the NTP replies. Isn't this the purpose of DNSSEC? It allows you to trust the identity of the NTP host domain name. If he is who he says he is, then the time that he serves is what he says it is. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Timing GPS recommendations
On 2012-08-20, unruh un...@invalid.ca wrote: No The sure is 10s of ns device. Unfortunately this is useless as you cannot get the time into your computer to better than usec. The interrupts are not serviced fast enough on any PC to give better than a few us and the interrupt routines get delayed on a working system by more than that at times (eg due to disk priority, or things switching off interrupt processing). You would have to build a special board for your computer to better than usec. I am also using a Thunderbolt with one of Ackermann's Clock-Block boards to replace my motherboard clock. The 10 MHz output from the GPS receiver is divided by the Clock-Block board. This sync's the PC with the GPS constellation and without requiring an interrupt from the CPU. The installation requires removing a surface mount part from the motherboard and a connection to the divider board. There are ways to bypass the CPU interrupt requirements if you have the proper tools. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP + PPS on Atom motherboards
On 2012-08-01, Hahn, Ron ron.h...@fmr.com wrote: Colleagues, I have used exactly the same recipe on a Core 2 Duo Tyan server and the times are maximally off by only +4uS/-2uS from PPS. So I am thinking there is something fundamental wrong with the Atom boards. I have repeated the experiments with a Pentium 4 server in another location and I am also seeing excellent timekeeping too. I am thinking that maybe the Atom clock on the board is too consumer for these uses?? Has others experienced these difficulties with Atom motherboards as Stratum 1 servers? I have been using several Intel D510MO boards for the last few years along with Oncore receivers. The ntpq billboards are in the +2us./ -4 us offset range at all times. I am also using FreeBSD 8.3 on all of my time serverrs. My jitter numbers are also in that same very low range. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP + PPS on Atom motherboards
On 2012-08-01, Hahn, Ron ron.h...@fmr.com wrote: Chris, Thank you for these helpful advises. I am recalling many years ago there were such things as line transceivers that converted the signals from TTL-RS232 and backwards. Do these still exist in the world and have you perhaps these part numbers? I am thinking this is the only thing left to try. Except possibly changing the PPS pulse width. Maybe with the Fat PPS board? This is reminding me of the old days. Printers and Terminals! :) Ron: All of my Oncore / Atom installations are using various TAPR interface boards to go from TTL to 'true' RS-232. You never stated that your Atom boards were not running at RS-232 levels. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP + PPS on Atom motherboards
On 2012-08-01, Hahn, Ron ron.h...@fmr.com wrote: the PPS pulse width. Maybe with the Fat PPS board? This is reminding me of the old days. Printers and Terminals! :) Ron: All of my TAPR boards also drive the RS-232 PPS pin with a 'low-z' output. They use 4 sections in parallel from a 74AC04N that gets it's input from the PPS output pin on the Oncore. This may stretch the pulse a little, but the pulse is very sharp! Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] NTP 4.2.7p255 drops core on FreeBSD 8.2
Something with NTPD has changed between version 4.2.7p249 and version 4.2.7p255 that causes the ntp daemon to exit on a signal 11 and drop core. My configur- ation files have not changed in several months and the FBSD base system ntpd will still start after the 4.2.7p255 aborts. I tried starting ntpd with a debug flag and I see the dialog with my Oncore receiver and every other line is a 'interrupted system call' message. My system information: Feb 4 17:04:48 mail kernel: FreeBSD 8.2-STABLE #0: Sat Feb 4 16:56:56 EST 2012 Feb 4 17:04:48 mail kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Feb 4 17:04:48 mail kernel: CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1672.67-MHz K8-class CPU) Feb 4 17:04:48 mail kernel: Origin = GenuineIntel Id = 0x106ca Family = 6 Model = 1c Stepping = 10 Feb 4 17:04:48 mail kernel: Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Feb 4 17:04:48 mail kernel: Features2=0x40e31dSSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE Feb 4 17:04:48 mail kernel: AMD Features=0x20100800SYSCALL,NX,LM Feb 4 17:04:48 mail kernel: AMD Features2=0x1LAHF Feb 4 17:04:48 mail kernel: TSC: P-state invariant Feb 4 17:04:48 mail kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs Feb 4 17:04:48 mail kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads Feb 4 17:04:49 mail ntpd[1011]: ntpd 4.2.7p249@1.2483 Tue Jan 24 20:04:47 UTC 2012 (1) Feb 4 17:04:49 mail ntpd[1011]: proto: precision = 1.676 usec (-19) This is the system message log for ntpd 4.2.7p255: Feb 18 17:24:00 mail ntpd[994]: ntpd 4.2.7p255@1.2483 Wed Feb 8 16:48:02 UTC 2012 (1) Feb 18 17:24:00 mail kernel: pid 995 (ntpd), uid 0: exited on signal 11 (core dumped) I don't know what additional information can I gather before filing a bug report. Is anyone else able to start ntpd version 4.2.7p255 on FreeBSD? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP 4.2.7p255 drops core on FreeBSD 8.2
On 2012-02-21, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote: Tom, It's running fine on my FreeBSD 8.2 system. That's with: ntpd 4.2.7p255@1.2483 Fri Feb 10 06:04:36 UTC 2012 (1) built from source. If you need any ntpq output from this system please let me know just what. That's with a Garmin GPS 18 LVC. David: Did you use the 'ports system' to build your NTP? Another question is your FreeBSD system hardware. Is your system multi-core and 64 bit? I used the ports system to build mine and if you did not, then it might be an issue to be addressed by the Port Maintainer and not the NTP development team. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Second attempt at GPS-18 based NTP server
On 2012-02-03, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote: The generic BSD kernel does not enable PPS support by default. You must recompile to enable PPS. The page you quoted says the following in the section System software customization (about 45% down the page in the Software section): System software customisation Need to add one line to the Kernel configuration: options PPS_SYNC and recompile the Kernel. On my 133MHz/48MB system this can take several hours. Note the configuration suggestions below before you recompile the kernel. But that was FreeBSD 5.4 and some six years ago. Note that I did not make the same remark about FreeBSD 8 - so whether that does or does not need recompiling is something I don't currently know. The need to make a custom kernel that includes option PPS_SYNC is still true on the recently released FreeBSD 9.0. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Second attempt at GPS-18 based NTP server
On 2012-02-02, Paul Duncan p...@noc.ac.uk wrote: So, I *think* that everything is okay, and it is using the PPS signal. There is one slight worry, which is what I see in /var/log/messages: Feb 2 09:50:16 tock ntpd[1573]: refclock_nmea: time_pps_kcbind failed: Operation not supported Please note, I have not done any recompiling of the kernel at this stage - just using the GENERIC kernel, because after reading the comments from Per Hederland in the System software customisation section of the above web page, it seemed unnecessary. Comments? I think that you will need to recompile uour kernel with the following option added. # Enable support for the kernel PLL to use an external PPS signal, # under supervision of [x]ntpd(8) # More info in ntpd documentation: http://www.eecis.udel.edu/~ntp options PPS_SYNC Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] No PPS FreeBSD with NMEA flag1 1 ntpd Ver. 4.2.6p5
On 2012-02-07, Mark C. Stephens ma...@non-stop.com.au wrote: [root@NTP ~]# ntpdc -c kerninfo pll offset: 3.243e-05 s pll frequency:106.791 ppm maximum error:0.011957 s estimated error: 8.8e-05 s status: 2001 pll nano pll time constant:4 precision:1e-09 s frequency tolerance: 496 ppm pps frequency:119.790 ppm pps stability:0.000 ppm pps jitter: 0 s calibration interval: 4 s calibration cycles: 0 jitter exceeded: 0 stability exceeded: 0 calibration errors: 0 AFAIK I have done everything exactly as my friend Google said, Any other information that can assist us to track down the issue? You never stated whether you added option PPS_SYNC to your kernel configuration file, built and loaded the PPS enabled kernel. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Very large jitter and offsets on GPS ref clock after upgrade to p5
On 2012-01-06, Chris Albertson albertson.ch...@gmail.com wrote: I know you are going to ask so here are the config files MODE 4 LAT33 51 54.315 LONG -118 23 01.782 HT 25.56 M DELAY 50 NS ASSERT SHMEM /var/log/ntpstats/ONCORE POSN3D MASK 0 Cris: Re-reading your ntp.oncore configuration file, something jumped out at me. Your MODE 4 setting means that your Oncore is performing a site survey each time time you restart ntp. From the Oncore driver source code: * Five Choices for MODE *(0) ONCORE is preinitialized, don't do anything to change it. *nb, DON'T set 0D mode, DON'T set Delay, position... *(1) NO RESET, Read Position, delays from data file, lock it in, *go to 0D mode. *(2) NO RESET, Read Delays from data file, do SITE SURVEY to get position, *lock this in, go to 0D mode. *(3) HARD RESET, Read Position, delays from data file, lock it in, *go to 0D mode. *(4) HARD RESET, Read Delays from data file, do SITE SURVEY to get *position, lock this in, go to 0D mode. * * NB. If a POSITION is specified in the config file with mode=(2,4) * [SITE SURVEY] then this position is set as the INITIAL position of * the ONCORE. This can reduce the time to first fix. * * Perfoming the site survey may affect your offset and jitter numbers. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Very large jitter and offsets on GPS ref clock after upgrade to p5
On 2012-01-06, Chris Albertson albertson.ch...@gmail.com wrote: I just upgraded to?4.2.6p5@1.2349-o and I'm getting some odd results. NTPD has been running for about 12 hours not on a Linux system. ?The following three peers displays were taken about one minute?apart. How do I go about debugging this? ? Where to start? ? The PPS coming from the Oncore has less jitter on it than I can measure with an HP5328 counter. ?I shows a period of exactly 1,000,000 uSec. ?I look at clockstats and I know you are going to ask so here are the config files MODE 4 LAT33 51 54.315 LONG -118 23 01.782 HT 25.56 M DELAY 50 NS ASSERT SHMEM /var/log/ntpstats/ONCORE POSN3D MASK 0 Cris: The Oncore driver has had a few recent syntax changes and it is possible that your PPS input is not being seen or works different than it had in the past. Here is my Oncore configuration file. HARDPPS PPS_CAPTUREASSERT MODE 1 LON -84.2017844758 LAT 40.7762210511 HT 223.445 MASK 20 DELAY 92.1 ns Look at the information presented with the ntpq -c kern command: associd=0 status=0415 leap_none, sync_uhf_radio, 1 event, clock_sync, pll offset:-0.002089 pll frequency: -10.0246 maximum error: 0.002239 estimated error: 1e-06 kernel status: pll ppsfreq ppstime ppssignal nano pll time constant: 4 precision: 1e-06 frequency tolerance: 495.911 pps frequency: -10.0246 pps stability: 0.0134583 pps jitter:0.002 calibration interval 256 calibration cycles:4614 jitter exceeded: 3690 stability exceeded:0 calibration errors:8 The keywords are ppsfreq, ppstime, ppssignal and nano. That should tell you if pps is working on your system. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Very large jitter and offsets on GPS ref clock after upgrade to p5
On 2012-01-06, unruh un...@invalid.ca wrote: Ssure a pulse can go missing. Eg, your encore pluse is a TTL level pulse (0-3 volt transition) and your serial port is marginal with that ( the standard for serial ports is basically -5 to +5 volt transition) So occasionally the hardware misses the transition. Or there could be some high resistance in the line from the encore which meant that the voltage level transition was too small. Of the receiver decided that the sattelite data was just not good enough to send out a pulse. So yes, pulses could go missing. What worries me more is that 999 ms offset at one point, which suggests that the nmea sentence came too late and the pulse got associated with the wrong second. (The garmin 18x had this trouble a lot apparently). The Oncore Driver 30 does not use the NMEA protocol. It uses one of those 'special' non-generic type of commands unique to Motorola receivers. Reg Clements is the Type 30 maintainer and is very helpful sharing his knowledge of Motorola binary in solving problems. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] ntp-keygen not working
On 2011-12-20, Arpan Gujarati arpancas...@gmail.com wrote: I am trying to generate keys for to enable autokey option with NTP. But I am getting a Floating point exception when I try it on Free-BSD machine. can anyone please point what may be the possible problem? root@ns# ntp-keygen Using OpenSSL version OpenSSL 0.9.7e-p1 25 Oct 2004 Using host ns group ns Generating RSA keys (512 bits)... Floating point exception: 8 (core dumped) It works for me on a FreeBSD 8.2 system: FreeBSD 8.2-STABLE Welcome to FreeBSD! # ntp-keygen Using OpenSSL version 90811f Random seed file /root/.rnd 1024 bytes Generating RSA keys (512 bits)... RSA 0 6 9 1 11 24 3 1 2 Generating new host file and link ntpkey_host_x.xx-ntpkey_RSAkey_xxx.xxx.xx.3533465390 Using host key as sign key Generating certificate RSA-MD5 X509v3 Basic Constraints: critical,CA:TRUE X509v3 Key Usage: digitalSignature,keyCertSign Generating new cert file and link ntpkey_cert_.xxx.xxx-ntpkey_RSA-MD5cert_xxx.xx.xx.3533465390 My OpenSSL is a lot newer than the one from October 2004. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Offset Jumps with Motorola Oncore UT+
On 2011-12-09, Miguel Gon?alves m...@miguelgoncalves.com wrote: Hi! This morning my FreeBSD 7.4 Oncore UT+ NTP server exhibited a strange behaviour... Note the huge jump in offset from 854 ns to 596 us and then the highest offset at 159 ms. loop stats file: 55904 33635.224 0.01230 -1.282 0.00888 0.001755 4 55904 33651.224 0.00854 -1.282 0.00807 0.001642 4 55904 33667.224 -0.000596143 98.718 0.000167778 35.355334 4 55904 33683.227 -0.002127304 98.718 0.000187390 33.071886 4 55904 33699.227 -0.003561445 98.718 0.000176065 30.935917 4 55904 33715.228 -0.004910077 98.718 0.000165214 28.937901 4 55904 33731.231 -0.006175330 98.718 0.000155121 27.068927 4 55904 33747.230 -0.007362986 98.718 0.000145378 25.320663 4 55904 33763.231 -0.008479146 98.718 0.000136915 23.685311 4 55904 33779.232 -0.009525378 98.718 0.000128152 22.155580 4 55904 33795.233 -0.010508291 98.718 0.000120356 20.724648 4 55904 33811.233 -0.011431854 98.718 0.000113179 19.386133 4 55904 33827.236 -0.012298303 98.718 0.000106061 18.134067 4 55904 33843.235 -0.013111000 98.718 0.99472 16.962866 4 55904 33859.235 -0.013875647 98.718 0.93789 15.867308 4 55904 33875.246 -0.014592572 98.718 0.87576 14.842508 4 55904 33891.236 -0.015265789 98.718 0.82514 13.883895 4 55904 33907.237 -0.015897754 98.718 0.77516 12.987194 4 55904 33923.237 -0.015990842 -1.281 0.000113346 37.383905 4 55904 33939.235 -0.015012221 -1.281 0.000119575 34.969441 4 clock stats file: 55904 33650.223 127.127.30.0 3532411249.99141 2011 343 9 20 50 49 rstat 08 dop 0.0 nsat 9,7 traim 1,0,0 sigma 41 neg-sawtooth -34 sat 3888 55904 33651.223 127.127.30.0 3532411250.99704 2011 343 9 20 51 50 rstat 08 dop 0.0 nsat 9,7 traim 1,0,0 sigma 41 neg-sawtooth -49 sat 3888 The machine is running 4.2.6p4. What might have caused this? This machine does nothing else providing NTP to the network. The most likely cause for the offset change that you observed was related to the satellite position relationship taking a bad track. This is minimized by setting a higher mask angle in your Oncore configuration and not use satellites below 10 degrees above the horizon. If you have trees or other obstuctions in the area, use an even higher angle. GPS satellites have their maximum accuracy when their path to you is 'high in the sky' and without obstructions. It is unfortunate that you chopped off the portion of your clockstats file that coincided with 'something interesting' being recorded in your loopstats file. This occurred at 55904 33667.224 in the log. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Motorola Oncore UT+ problems
On 2011-11-16, Miguel Gon?alves m...@miguelgoncalves.com wrote: Hi guys! Here's the problem: I have one particular Oncore UT+ receiver (2.2 firmware revision) that only works in mode 3, i.e., I need to reset it (losing the almanac) everytime I restart the NTP daemon. As you might imagine this is a major problem. If I don't use mode 3 it just hangs at 55881 34932.888 127.127.30.0 ONCORE[0]: Have now loaded an ALMANAC 55881 34932.888 127.127.30.0 ONCORE[0]: state = ONCORE_RUN 55881 34932.888 127.127.30.0 ONCORE[0]: SSstate = ONCORE_SS_DONE 55881 34932.958 127.127.30.0 ONCORE[0]: ONCORE: Detected TRAIM, TRAIM = ON 55881 34932.958 127.127.30.0 ONCORE[0]: Input says TRAIM = 1 55881 34932.958 127.127.30.0 ONCORE[0]: Model # says TRAIM = 1 ,, My first guess would be that you have a hardware problem with this particular Oncore UT+. Is your Oncore battery good? I think that the battery voltage measurement point is pin 1 and the ground reference is pin 3. Does your RS-232 cable have continuity end to end for at least pins 1, 2, 3 and 5? Does your Oncore receiver operate normally when using any other programs? The NTP Oncore reference clock driver talks a lot during startup. My last startup looked like this: Nov 12 17:48:26 mail ntpd[1169]: ntpd 4.2.7p225@1.2483-o Thu Oct 27 20:01:41 UTC 2011 (1) Nov 12 17:48:26 mail ntpd[1170]: proto: precision = 1.676 usec Nov 12 17:48:26 mail ntpd[1170]: ONCORE[0]: ONCORE DRIVER -- CONFIGURING Nov 12 17:48:26 mail ntpd[1170]: ONCORE[0]: state = ONCORE_NO_IDEA Nov 12 17:48:26 mail ntpd[1170]: ONCORE[0]: ONCORE: Can't open SHMEM file Nov 12 17:48:26 mail ntpd[1170]: ONCORE[0]: ONCORE: Can't open shmem Nov 12 17:48:26 mail ntpd[1170]: ONCORE[0]: state = ONCORE_CHECK_ID Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: Oncore: Resend @@Cj Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: @@Cj Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: COPYRIGHT 1991-1997 MOTOROLA INC. Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: SFTW P/N # 98-P36848P Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: SOFTWARE VER # 2 Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: SOFTWARE REV # 2 Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: SOFTWARE DATE APR 24 1998 Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: MODEL #R5122U1152 Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: HWDR P/N # 5 Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: SERIAL # R09E3D Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: MANUFACTUR DATE 0H08 Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: Nov 12 17:48:27 mail ntpd[1170]: ONCORE[0]: state = ONCORE_CHECK_CHAN Nov 12 17:48:32 mail ntpd[1170]: ONCORE[0]: state = ONCORE_HAVE_CHAN Nov 12 17:48:33 mail ntpd[1170]: ONCORE[0]: state = ONCORE_TEST_SENT Nov 12 17:48:40 mail ntpd[1170]: ONCORE[0]: GPS antenna: OK Nov 12 17:48:40 mail ntpd[1170]: ONCORE[0]: state = ONCORE_INIT Nov 12 17:48:43 mail ntpd[1170]: ONCORE[0]: Oncore: Resend @@Cj Nov 12 17:48:43 mail ntpd[1170]: ONCORE[0]: state = ONCORE_ALMANAC Nov 12 17:48:52 mail ntpd[1170]: ONCORE[0]: Have now loaded an ALMANAC Nov 12 17:48:52 mail ntpd[1170]: ONCORE[0]: state = ONCORE_RUN Nov 12 17:48:52 mail ntpd[1170]: ONCORE[0]: SSstate = ONCORE_SS_DONE Nov 12 17:48:52 mail ntpd[1170]: ONCORE[0]: ONCORE: Detected TRAIM, TRAIM = ON If all else fails, remove the receiver battery for at least 30 minutes before reinstalling. Try another program to see if it gets any other usable data to post on this site. I have also posted questions to the tapr.org timing group mailing list. There are a lot of Oncore users subscribed to that list. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Loop Frequency and Offset
On 2011-09-27, Miguel Gon?alves m...@miguelgoncalves.com wrote: One had 180 ppm sand the other 46 ppm without fiddling with machdep.tsc_freq sysctl variable. After the correction I am getting -0.041 ppm for the first and -0.045 ppm for the second. Embedded machines running NanoBSD and they don't do anything else besides running NTP. They sit in a temperature controlled room at 20 ?C. Power management has been disabled. I checked the BIOS and did not see any reference to spectrum clocks. Miguel: There are a lot of links off of the leapsecond.com of home made methods that improve clock stability. I am using one of these PC clock crystal replacement boards in my Intel Atom. http://www.leapsecond.com/ptti2003/index.htm http://www.tapr.org/~n8ur/Clock-Block_Manual.pdf Installation is meant for someone with better than average soldering skills. This device replaces your motherboard clock crystal with something that is more stable. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Motorola Oncore Surveyed Position
On 2011-09-06, Miguel Gon?alves m...@miguelgoncalves.com wrote: I switched again to mode 4 and started again to see if I missed something. I believe I'll only have to wait 1 seconds = 2 hours and 46 minutes... not much. :-) Unfortunatelly clockstats doesn't show position, only time. I believe this is because it's in position lock (0D?) mode. Here's a sample: By the way... I was looking at the clockstats file and noticed that when I switched to mode 4 as I said earlier I got this 55810 40560.366 127.127.30.0 ONCORE[0]: Loading Posn from SHMEM 55810 40560.367 127.127.30.0 ONCORE[0]: Setting Posn and Time after Loading Almanac 55810 40562.091 127.127.30.0 ONCORE[0]: Posn: 55810 40562.091 127.127.30.0 ONCORE[0]: Lat = N 41.1745319deg,Long = W 8.6560764deg,Alt = 146.72m (481.36ft) GPS 55810 40562.091 127.127.30.0 ONCORE[0]: Lat = N 41deg 10.4719m, Long = W 8deg 39.36458m, Alt = 146.72m ( 481.36ft) GPS 55810 40562.091 127.127.30.0 ONCORE[0]: Lat = N 41deg 10m 28.32s, Long = W 8deg 39m 21.88s, Alt = 146.72m ( 481.36ft) GPS 55810 40564.365 127.127.30.0 ONCORE[0]: Waiting for Almanac 55810 40567.365 127.127.30.0 ONCORE[0]: Have now loaded an ALMANAC 55810 40567.365 127.127.30.0 ONCORE[0]: state = ONCORE_RUN It seems this is my location... :-) Now you know where I live! :-) So the position is stored in the shared memory and when I reset the unit (mode 4) it uses the position stored in there. Anyone help care to comment this? This is from the refclock_oncore.c file. /* * If we don't find any then we don't have the cable delay or PPS * offset and we choose MODE (4) below. * * Five Choices for MODE *(0) ONCORE is preinitialized, don't do anything to change it. *nb, DON'T set 0D mode, DON'T set Delay, position... *(1) NO RESET, Read Position, delays from data file, lock it in, *go to 0D mode. *(2) NO RESET, Read Delays from data file, do SITE SURVEY to get *position, lock this in, go to 0D mode. *(3) HARD RESET, Read Position, delays from data file, lock it *in, go to 0D mode. *(4) HARD RESET, Read Delays from data file, do SITE SURVEY to *get position, lock this in, go to 0D mode. * NB. If a POSITION is specified in the config file with * mode=(2,4) [SITE SURVEY] then this position is set as the INITIAL position of the * ONCORE. This can reduce the time to first fix. * --- * Note that an Oncore UT without a battery backup retains NO information if it is power cycled, with a Battery Backup it remembers the almanac, etc. For an Oncore VP, there is an eeprom that will contain this data, along with the option of Battery Backup. * So a UT without Battery Backup is equivalent to doing a HARD RESET on each power cycle, since there is nowhere to store the data. If we open one or the other of the files, we read it looking for MODE, LAT, LON, (HT, HTGPS, HTMSL), DELAY, OFFSET, ASSERT, CLEAR, HARDPPS, STATUS, POSN3D, POSN2D, CHAN, TRAIM then initialize using method MODE. For Mode = (1,3) all of (LAT, LON, HT) must be present or mode reverts to (2,4). */ Your ntp.oncore.0 file will need to list your location: This is from my file HARDPPS PPS_CAPTUREASSERT MODE 1 LON -84.2017844758 LAT 40.7762210511 HT 223.445 DELAY 92.1 ns This skips the receiver reset and loads my coordinates. Once the receiver has a valid almanac, it will serve time. I am also using FreeBSD, but don't use SHMEM. You should be able to just link your serial port to the correct device using devfs.conf oncore.pps.0 -cuau0 oncore.serial.0 -cuau0 Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Getting PPS to work with Oncore ref clock
On 2011-02-17, Hal Murray hal-use...@ip-64-139-1-69.sjc.megapath.net wrote: Some devices put out a narrow (10 microsecond) pulse. I don't know what the Oncore does. I have one PC that works fine with a narrow pulse and another PC that doesn't see it. I kludged together a pulse stretcher (diode, R, C) and it started working. Well, I thought it was working. It turns out that it only sees some of the pulses. My copy of the Oncore Engineering Note shows a 200 ms. pulse width for the PPS signal. It all may depend on the original poster's Oncore version. My book only covers the VP, VT and UT. The newer 12 channel ones may be different. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] serialPPS+gpsd+ntpd large offset jitter
On 2011-01-12, Chris Albertson albertson.ch...@gmail.com wrote: I had a motherborad fail a few weeks ago, (big black burned hole where a voltage regulator caught fire) so before dumping the thing in the trash I looked it over for good salvage.I found two TCXOs that were used for the CU clock and for the graphic system but the real time clock chip had a cheep 32Khz watch crystal on it. These sell for maybe 10 cents each. Seems to me that if you want to build a first class NTP server it would not be hard to unsolder the watch crystal and replace it with a length of coax cable that heads off to a precision oscillator.I had little to loose as the board was already dead and found the watch crystal comes off very easy. Some day I'll build a 32K oscillator that is locked to the 10Mhz laboratory frequency reference Since you are going to perform some circuit board repairs, there is a TAPR kit you might have interest: http://www.tapr.org/~n8ur/Clock-Block_Manual.pdf The clock crystal is removed and replaced with this board and the PC will be phase locked with the GPS broadcasts. The designer, N8UR, has a lot of time related information on his website as well. He has replaced the motherboard clock on a low powered Intel Atom with this kit. SMT board soldering is not for everyone, but since you are already planning on replacing your motherboard clock chip, you might want to review this site for various ideas: http://www.febo.com Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] What version of ntpd am I really running??
On Tue, Jan 4, 2011 at 23:30 UTC, Edward T. Mischanko etm1...@hotmail.com wrote: On my FreeBSD system have built and installed ntp-dev-4.2.7p108. But, when I type: ntpd --version It returns: ntpd - NTP daemon program - ver 4.2.4p5 What is the prper way to determine the current version of ntpd that you have installed or are running? After building and installing the ported version of NTP, you will need to edit your /etc/rc.conf startup script to point to the ported ntp version in /usr/local/bin instead of the default system version. I don't try to overwrite the system version of any of the ported programs, because they will only get replaced back with any system updates. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT
On 2010-05-05, Hal Murray hal-use...@ip-64-139-1-69.sjc.megapath.net wrote: In article 4be025aa.4050...@signaturealpha.com, Marc Leclerc marc-lecl...@signaturealpha.com writes: I am trying to have NTP use the trimble resolution SMT gps module, I have tried other trimble clock driver without success so I assume that one specific to the module has to be used. Unfortunately there does not seems to be any way to search the mailing list to see if this was discuss before. I would appreciate if anyone with information could get back to me. I am trying to make this work on an embedded linux platform, I already have the linuxpps driver installed and have the /dev/pps0 node available. the module is wired to /dev/ttyS1. Using the clock driver for the palisade lead to wrong answer format messages. The Palisade driver supports several different variations of Trimble products. Which one(s) did you try? The data sheet says it speaks TISP and NMEA. I don't know which one is the default. You might try running some helper code before starting ntpd to switch it to NMEA mode, and then telling ntpd that it's a NMEA device. There might be some issues with your serial port connection to the receiver. You might want to pipe the serial I/O to your console and monitor what is being sent and received from the serial port. I have used a Trimble Thunderbolt for NTP and it also uses the TSIP protocol. The Palasades driver worked for me, but I had issues with getting the Thunderbolt to serve the time after a NTP poll instead of whenever it chose. My receiver came with a RS-232 interface, but a lot of Trimble OEM products are RS-422 single ended and require a converter to RS-232 standard serial port. Since your clock is supposed to understand TSIP, there might be a program from Trimble that lets you talk directly to your clock to make sure that it is operational, has a valid position and your serial level converter is working. If your module does not have a diagnostic utility, you may try the one for the Thunderbolt. The Trimble website has these utilities. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How to debug GPS PPS?
On 2010-03-09, xyz-2041 xyz2...@gmail.com wrote: Forgot to add the changes to /etc/ntp.conf: Thanks Tom, et. al. for helping me get this going. The box is now running as Stratum 1. # Links for NTP Oncore GPS(0) link cuad0 pps0 link cuad0 oncore.pps.0 link cuad0 oncore.serial.0 Added a 2nd group: # GPS Oncore driver 0 server 127.127.30.0 fudge 127.127.30.0 refid GPS0 # PPS driver: server 127.127.22.0 fudge 127.127.22.0 refid PPS0 # ntpq -c pe remote refid st t when poll reach delay offset jitter == GPS_ONCORE(0) .GPS.0 l- 1600.000 0.000 0.000 PPS(0) .PPS.0 l- 6400.000 0.000 0.000 oGPS_ONCORE(1) .GPS.0 l5 16 3770.000 -0.001 0.002 xPPS(1) .PPS.0 l 53 64 3770.000 -0.001 0.002 192.168.2.255 .BCST. 16 u- 6400.000 0.000 0.002 The Oncore 0 and PPS 0 entries are not doing anything for your ntp installation. They both show a '0' in the reach column. This means that NTP is not using either of those two devices for timekeeping. You can delete them from your configuration files. You are also not getting any benefit from your broadcast client. There are many references in the NTP Documenatiuon about broadcast client configuration, especially in the area of authentication and key exchange. I hope that you also include some Internet timeservers in your installation to check the sanity of your GPS clock. The recomendation is to have at least 4 time sources, including your GPS clock. That lets the majority outvote a 'falseticker'. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Tutorial for setting up Garmin 18 LVC on FreeBSD 8.0
On 2010-02-22, ryandoyle r...@ryandoyle.net wrote: For anyone interested in setting up a Garmin 18 LVC GPS receiver on FreeBSD 8, I wrote up a fairly detailed tutorial of my experiences here: http://blog.doylenet.net/?p=145 If there are any comments or errors, please let me know My comments are all on your FreeBSD configuration. I believe that the FreeBSD base version of ntp is the same one that you installed from the port system. That seemed a little redundant. That version is much older than the /usr/ports/net/ntp-devel version. The development version is very well tested and debugged by the time that the maintainer commits it to the ports system. The reference clock support is probably the one area of NTP that is continuously being evolved. Someone with a Garmin 18 problem that asks a question to this group is most likely asked to install the development version to see if the problem is still present. Configuring the min and max poll for a reference clock sort of goes against the grain of how ntp is supposed to work. Let the daemon adjust things according to how the clock is performing in relation to the it's other sources of information. It needs to have the maximum degree of freedom in order to converge on the best solution! Most admins cringe at the thought of allowing root logins from any location other than the local console. The better advice is to create another user on your BSD computer and put them into the 'wheel' group. That user can use SSH from anywhere and 'su' to gain root privleges. Better yet, is to install the 'sudo' port and that user never needs to know the root password! You don't need to install either bash or vim in order to successfully install and operate ntp. The default shell on FreeBSD and the vi editor are more than sufficient. I'll let the Garmin wizards comment on that part of the instruction. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Tutorial for setting up Garmin 18 LVC on FreeBSD 8.0
On 2010-02-22, ryandoyle r...@ryandoyle.net wrote: All the sample ntp.conf files had max and mix poll configured, I was just following these. Should these not be entered? Thanks for the info on the ntp-devel port. If the ntp-dev port is used instead of the one that is included in the base software, the startup script in /etc/rc.conf will need to be changed to point at /usr/local/bin instead of the location of ntpd listed in the base installation. FreeBSD always installs port software in the /usr/local directories and puts base software in /usr/bin, /usr/sbin. There have been questions sent to this group from inexperienced FreeBSD users that have built ntp from a port and still see the base version of ntpd running. The /etc/rc.conf file requires changing the location of the ntp installation to /usr/local/bin. Min and max polling rates should not be entered unless you have a specific problem that will be solved by changing them from the default of letting ntpd set them dynamically. I also agree, I guess it is the responsibility of the user to know the implications of either way. You should state this in your writeup. Someone new to FreeBSD could be using your instructions as a cookbook recipe. The deviations from the default and best practice defaults should have an explaination of the benefits and tradeoffs of doing something. I could have left this out, but I chose to include it as bash makes the average Linux user feel more at home. A bit of bash and vim with Linux-like bindings and no one will even notice you are using FreeBSD! But yes, definitely don't _need_ bash or vim to run ntp. Another good point is to get ntp and the reference clock playing well together from the local console with the minimum configuration files before adding all of the 'restrict' flags that you see in most of the Internet writeups. Adding them without knowing what they all mean spells disaster for someone new to FreeBSD and ntp. Your writeup on how to integrate ntp with FreeBSD is good and can be used by someone comming from more than a Linux background. There are a lot more operating systems 'in the wild' than Windows, Linux and 'BSD'. Making your writeup less 'Linux-like' might also help the VMS, QNX, OS9 and Amiga guy. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Tutorial for setting up Garmin 18 LVC on FreeBSD 8.0
On 2010-02-22, Terje Mathisen terje.mathisen at tmsw.no wrote: ryandoyle wrote: You might consider trying a bleeding edge (dev tree) version of ntpd, directly from ntp.org, instead of the ports version: That is not a good idea on Freebsd to not use the ports system, especially for someone writing a 'how-to' for someone new to the OS and trying to make a reference clock play well with his new OS. There are FreeBSD specific patches to the tarball that gets downloaded from the archives at ntp.org. The ntp-dev port has these patches and was tested by the port maintainer to work well enough to get committed to the repository. You'll also need to get rid of the default ntp* executables in order for the new ones in /usr/local/* to be found. Just point the /etc/rc.conf startup script entries for the location of the executable in /usr/local/bin. I suppose that the other utilities that get installed with the port need to come first in the path search order. Modifying or creating an /etc/make.conf might be a little too far along the learning curve for a newbie to the OS to not make the default ntp programs as a part of making the rest of his 'world'. I usually leave the default ntp support binaries alone and just start the development ntpd binary in /etc/rc.conf. If something appears 'strange' when issuing ntpq requests, I will try the command again with the /usr/local prefix to see if something has been changed in the development version of the program. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How to debug GPS PPS?
On 2010-02-16, xyz-2041 xyz2...@gmail.com wrote: Thanks, Tom and guys. I really appreciate your help! Looks like something is going on with the Oncore: # ntpq -c pe remote refid st t when poll reach delay offset jitter == GPS_ONCORE(0) .GPS.0 l- 1600.000 0.000 0.000 xPPS(0) .PPS.0 l 11 64 3770.000 -3.085 0.017 192.168.2.255 .BCST. 16 u- 6400.000 0.000 0.001 # ntpq -c rv assID=0 status=0615 leap_none, sync_ntp, 1 event, event_clock_reset, version=ntpd 4.2.7...@1.2108-o Mon Feb 15 20:10:40 UTC 2010 (1), processor=i386, system=FreeBSD/7.2-RELEASE, leap=00, stratum=2, precision=-20, rootdelay=44.827, rootdisp=44.339, refid=192.43.244.18, reftime=cf25709c.1130eea8 Tue, Feb 16 2010 13:29:32.067, clock=cf257657.3d54896e Tue, Feb 16 2010 13:53:59.239, peer=54924, tc=10, mintc=3, offset=-4.877, frequency=-49.876, sys_jitter=1.658, clk_jitter=2.179, clk_wander=0.056 precision=-20 how does one interpret this? Why wouldn't the PPS be taken as preferred? /var/log/ntp/clockstats: http://www.a7h.com/~stuph/var--log--ntp--clockstats-2010-Feb-16.txt Contained in /etc/ntp.conf: ~~ # GPS Oncore driver # server 127.127.30.0 prefer One note about your configuration, I don't think that you can have two 'prefer' statements. It was discussed recently in this newsgroup and my memory of recent events is not as good as it used to be. Try restarting your Oncore without the pps driver. Mine seems to see the receiver pps without having that statement in my /etc/ntp.conf file. It still looks like your Oncore receiver is not seeing the data being requested by the ntp refclock driver. Can you post the Oncore related lines of your syslog? The driver does a lot of setup work after a restart and the results are sent to the log. It may provide some insight into what is happening. Your Oncore pps on the DCD pin is doing something, but the rest of the data is still not getting seen by the daemon. Precision of -20 is what I see on my setup. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How to debug GPS PPS?
On 2010-02-15, David Lord sn...@lordynet.org wrote: Changed back to the Oncore: ~ # GPS Oncore driver # server 127.127.30.0 prefer server 127.127.30.0 fudge 127.127.30.0 refid GPSo # PPS driver: server 127.127.22.0 prefer fudge 127.127.22.0 refid PPS # Generic NMEA GPS Receiver: # server 127.127.20.0 # fudge 127.127.20.0 time1 0.752 refid NMEA ~ Pin 1 = PPS (Light is blinking once per second for about 200 ms) Pin 2 = Data: GPS - PC(Light blinks once per second--after pin 1-- for about 300-400 ms) Pin 3 = Data: PC - GPS Pin 5 = Ground Installed: pkg_info | grep gpsd gpsd-2.90 Daemon that monitors one or more GPSes attached to a host c # ls -lta /dev | grep cua crw-rw 1 uucp dialer 0, 41 Feb 15 00:33 cuad0 lrwxr-xr-x 1 root wheel5 Feb 14 15:42 gps0 - cuad0 lrwxr-xr-x 1 root wheel5 Feb 14 15:42 oncore.pps.0 - cuad0 lrwxr-xr-x 1 root wheel5 Feb 14 15:42 oncore.serial. 0 - cuad0 lrwxr-xr-x 1 root wheel5 Feb 14 15:42 pps0 - cuad0 lrwxr-xr-x 1 root wheel5 Feb 14 15:42 refclock-0 - cuad0 crw-rw 1 uucp dialer 0, 42 Feb 14 15:42 cuad0.init crw-rw 1 uucp dialer 0, 43 Feb 14 15:42 cuad0.lock gpsd outputs nothing at all: The PPS and data lights blinking show that your Oncore is working. One thing to keep in mind is that the serial baudrate changes from 9600 when defaulted in Motorola binary to 4800 when defaulted in the NMEA mode. Is gpsd looking for Motorola binary protocol or NMEA sentences? The HEX output that you are seeing when you look at /dev/cuad0 tells me that your Oncore is sending Motorola binary. # /usr/local/sbin/gpsd /dev/cuad0 # # /usr/local/bin/gpscat -s 9600N1 /dev/cuad0 Get some HEX output once per second: \x08'\xa2\x03\x08#\xa2\x06\x00\x00 \x08\x081\xa2\x17\x00\x00\x00\x1c \x00\x00\x00\x08* @@Ea\x02\x0f\x07\xda\x004+\x00\x02\xea\xb1\x08\xce,\xbf\xec \x0f0\x00\x00N\xb3\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01 The \0x08'\ is not in my book. The \@@Ea\xa2\x03\ line is a position status message in Motorola binary. It is sending month, day, year, hours, minutes, seconds, fractional seconds. The rest of the line is supposed to show your position (latitude followed by longitude). Your message seems to be showing zero's. I would guess that your receiver has not yet found itself. The Oncore driver executes a receiver self test when started and then looks for a position and a valid almanac. It will put the receiver in the 'site survey' mode for about 2 hours to get an idea of your antenna current position. The receiver will wait for a valid almanac before starting the site survey. If your /ntp/oncore file has a mode statement and the results of a previous site survey, the receiver only requires a valid almanac before ntp uses it for a reference. This could take 30 minutes if there isn't one in your receiver. The latest development version of the ntp software is a lot more verbose than the released version. All of the Oncore startup events are now sent to the syslog. You can see when the self test is complete and when it grabs the almanac and completes the self survey. Reg Clements has done a good job in making the Oncore driver send more reports for receiver problem troubleshooting. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How to debug GPS PPS?
On 2010-02-15, xyz-2041 xyz2...@gmail.com wrote: On Feb 15, 9:03?am, Thomas Laus lau...@acm.org wrote: receiver. ?The latest development version of the ntp software is a lot more verbose than the released version. ? Installed: 15 Feb 14:37:36 ntpd[680]: ntpd 4.2.7...@1.2108-o Mon Feb 15 20:10:40 UTC 2010 (1) No reach: remote refid st t when poll reach delay offset jitter == GPS_ONCORE(0) .GPS.0 l- 1600.000 0.000 0.000 PPS(0) .PPS.0 l- 6400.000 0.000 0.000 All of the Oncore startup events are now sent to the syslog. ? # find / -name syslog # Where is that? Something to set up? The system log syslog is the default destination for all event logs that don't otherwise have a home. It gets displayed when you read the contents of '/var/log/messages'. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Befuddled and confused, again...
On 2010-02-14, Dave Baxter s...@goes.nowhere.com wrote: I *Need* PPS support, as I have an app that needs mS accruacy. See:- http://www.dxatlas.com/Faros/ for details of what I have running, that needs such data. Plus, for whatever reason, my ISP (Demon/Thus/CW) seem unable to provide a stable NTP service these days. I am not aware that just configuring your system for PPS without actually using some hardware that provides a UTC synchronized signal will gain any higher accuracy than just running ntpd that is synchronized to Internet servers. I've been at it (trying to get FreeBSD working again) this time for over 3 weeks! And am about to lob the thing out of the window. It should just require booting from the install disk, taking the defaults when partitioning your hard drive, giving the PC a hostname, and providing a root password when prompted. That will get your computer running. Once it runs, configure your /etc/ntp.conf to look for at least 4 internet servers. That should bring you ms. accuracy traced to UTC. I find that there is just way too much documentation spread all over the web etc, all poorly indexed (as a noob sees it at least.) There also seems to be an assumption, that anyone looking at the info, already knows what they are looking at. (This is not alone in that respect of course.) The FreeBSD Handbook gets installed if selected during the install process, you can always add it later. It is 'The Source' of accurate answers to questions. Don't use someone elses interpretation of what should be there or how something is supposed to work! One huge dificulty I have, is that I do not know how to get it to remember the prompt = settings, or that I use a UK keyboard! I have to change those settings each and every boot at the moment. This depends on your shell. It should be in either .login or .profile in your home directory. I hear what you are saying re using a later version, but as I have the install CD's here for this, and it's purely for a local never-to-be-on- the-web server, on a relatively low powered machine, unless someone says otherwise, and as I had it working before, I'd prefer at this time to stick with what I have. Use it if you really want to. That version is several years old and you are more likely to get questions answered if you had the last released version loaded. There have been changes made and stuff might not work the same, if you ask a question about a 5. version and get an answer from someone using a 8. release. Oh, you still didn't indicate the exact full path to the 'make.conf' file. I know it's in /etc, but what directory should that spawn from? I don't have notes showing I had to create that file, only that I edited what was already there last time. (failing to make a record as to it's exact location I admit!) You will need to create a file in the /etc directory called make.conf if you need to override something that is default. That file does not need to be created if you don't have a requirement to have something built that is different that the default action in the default system. As to the FreeBDS lists/forums etc. Out of the 100's that there are, which one is recomended? I've been on one or two recently, finding them somewhat unfriendly to newbies. The comp.unix.bsd.freebsd.misc is a good catchall for newbie questions. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How to debug GPS PPS?
On 2010-02-12, xyz-2041 xyz2...@gmail.com wrote: OK. Couldn't get the Oncore unit to work in any way shape or form. I bought a DB9 LED tester like this: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemitem=260546635257 Had PPS going to pin 1, DATA OUT to pin 2, and DATA IN to pin 3. Still no good. You didn't mention if your ground wire was connected to pin 5? Did the tester LED's flicker as expected? Was there data passing in both directions from and to the computer? Was the PPS LED flashing one time per second? Your previous post to this group stated that your Oncore was working with the Motorola WinOncore utility. Did the observed satellites ever show 'Locked' in the display? The last time that I had to re-initialize an Oncore, I found that the almanac file that shipped with WinOncore was too old to be of any use with the current constellation. My Oncores seem to grab a new almanac quicker when placed in the NMEA mode. I let my receiver run until all satellites in view showed lock status and then saved the almanac to a disk file. I reinitialized my receiver in the Motorola binary mode and loaded the new almanac that was just saved. The receiver showed that it was locked within about 5 minutes. Once it was working correctly using the Motorola binary protocol, I connected it to my FreeBSD time server and restarted NTPD. Everything worked as expected. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP server can not synchronize with external NTP server
On 2010-01-11, nast linux nastli...@gmail.com wrote: Hai David, Thanks for reply, I already ask to network admin to open udp 123 for time.nist.gov. And I checked my server at firewall log that could send udp 123 to time.nist.gov. But I checked no paket from time.nist.gov. Is the NTP host being used under NAT? Maybe port 123 needs to be directed back from the internet to that host. Is the firewall rule keeping the state of the connection when the port 123 rule is getting used? I guess it is time for a session of tcpdump or wireshark to see just where your NTP packets are going and comming. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How to debug GPS PPS?
On 2010-01-01, xyz-2041 xyz2...@gmail.com wrote: comunicate with your Oncore. ?You might get some insight by enabling some of the statistics. ?You add them to /etc/ntp.conf # NTP Statistics statsdir /var/log/ntp/ statistics clockstats loopstats peerstats filegen clockstats file clockstats type day enable filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable OK, done: cd /var/log mkdir ntp cd /etc nano /etc/ntp.conf Seems to be talking to the unit: http://www.A7H.com/~stuph/clockstats-Edited-2010-Jan-1-1300.txt Nothing in peerstats or loopstats showing anything Oncore-GPS related. The clockstat log looks OK to me. I see that your Oncore GT+ is communicating via the RS-232 port on your PC. Do you know for sure if your GT+ has a valid almanac? When you connect to your Oncore using WinOncore12 under the Navigation window, does the receiver status show that it has a 'bad almanac'? Whenever switching mine from NMEA to Motorola protocol, I have to reload the almanac and re-enter the receiver information using the pushbuttons on the top. They all seem to init themselves in the NMEA mode, but require some manual intervention when switching to Motorola Binary. Does the status show the number of satellites in view and are most of them 'tracked'? Oncore GT+: does it need a pulse stretcher? None of mine ever needed any pulse stretching. Another item to note, when NTP initializes your Oncore, does the PPS LED stop blinking? Mine stops until the other peers get synced and then the Oncore driver sends the receiver command to start polling sequence for the time. I guess this is to allow the receiver to initialize, check the almanac for validity and then put the receiver in the '0D' Mode. About 10 minutes after restarting NTP, my PPS LED starts blinking again. I see that you have a 'real' serial port, this is good. There is a wealth of information on the TAPR website including the Motorola manuals that give meaning to all of those @@x commands. Having those manuals and using WinOncore has allowed me to get all of my problems resolved. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How to debug GPS PPS?
On 2009-12-30, xyz-2041 xyz2...@gmail.com wrote: On Dec 28, 7:59?am, Thomas Laus lau...@acm.org wrote: On 2009-12-28, xyz-2041 xyz2...@gmail.com wrote: Plugged in the GPS unit's serial cable into a Windows computer running WinOncore12 v1.0 (Build 37): ?http://www.google.com/#q=WinOncore12Installation.exe Seemed to work without any problems. ?Generated all sort of graphs and charts. ?Let it run and it told me exact latitude, longitude and height above sea level. Used an analog volt meter and from pin 5 (supposed to be ground), I only noticed voltage on pins 2 and 3. Pin 2 was going erratically negative once a second. I believe that this must be received data as per standards. ?Pin 3 was +5 volts, but dropping to -5 volts once per second. You did not mention how your Oncore receiver was being interfaced to your computer or it's model number. ? GT+. Serial port. I use one of the TAPR boards and Oncore UT+ combination. ?The NTP refclock driver for the Oncore includes the code for receiving the PPS signal on the computer DCD pin. It doesn't need pulse stretching? I've changed my configs a bit, /var/log/ntp.log and /var/log/ntpd.log don't show any errors. However, ntpq -c pe still doesn't show any response: ?GPS_NMEA(0) ? ? .GPS. ? ? ? ? ? ?0 l ? ?- ? 16 ? ?0 ? ?0.000 0.000 ? 0.001 ?PPS(0) ? ? ? ? ?.GPS. ? ? ? ? ? ?0 l ? ?- ? 16 ? ?0 ? ?0.000 0.000 ? 0.001 ?GPS_ONCORE(0) ? .GPS-. ? ? ? ? ? 0 l ? ?- ? 16 ? ?0 ? ?0.000 0.000 ? 0.001 You should not be using GPS_NMEA or PPS. ? OK. Turned both of those off. The type 30 refclock OK. Used WinOncore to default. Made sure that it was set to Motorola/binary. Power cycled. Hooked back up to FreeBSD server. This is what was produced--for a while: remote refid st t when poll reach delay offset jitter == GPS_ONCORE(0) .GPS.0 l 99 16 400.000 192.362 0.002 GPS_ONCORE(0) .GPS.0 l 200 1600.000 192.362 0.002 GPS_ONCORE(0) .GPS.0 l 418 1600.000 192.362 0.002 This does not look like anything is happening when NTP is trying to comunicate with your Oncore. You might get some insight by enabling some of the statistics. You add them to /etc/ntp.conf # NTP Statistics statsdir /var/log/ntp/ statistics clockstats loopstats peerstats filegen clockstats file clockstats type day enable filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable NTP will write events to these files when it runs. The satellites that are in view will be listed by PRN number. It also will show any RS-232 handshaking issues. I had to change the flag for reading the PPS pin because it was triggering on the trailing edge instead of the leading edge. My TAPR board pulsewidth was OK and did not require 'stretching'. Re-defaulted. Now back to this: GPS_ONCORE(0) .GPS.0 l- 1600.000 0.000 0.002 There is still nothing in the 'reach' column, you are not talking at all to your Oncore receiver. Even if the PPS was incorrect, you should still get data from the Oncore as soon as your NTP has synced with your other hosts. Your LED shows that your receiver has an almanac, position and is synced to the satellites. It is just the RS-232 link is not working between your TAPR board and your computer. A breakout box would be handy in this case, but enabling the statistics may give enough insight into the problem. The Oncore / TAPR board is the gold standard of home user time sync using the GPS constellation. Myself and others have been using this combination for many years successfully. Does your PC have a 'real' serial port or are you using a USB to serial adapter? My billboard looks like this: ntpq -c pe remote refid st t when poll reach delay offset jitter == -198.186.191.229 64.147.116.229 2 u 38 64 377 88.338 17.680 0.609 -tantalum.srvcs. 192.43.244.182 u6 64 377 112.759 -29.145 3.168 +null-routed.net 198.153.152.52 2 u 42 64 377 79.3331.590 0.792 +packman-1.isc.o 204.152.184.72 2 u2 64 377 77.789 -8.314 2.418 *GPS_ONCORE(0) .GPS.0 l 10 16 3770.000 -0.016 0.001 Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] How to debug GPS PPS?
On 2009-12-28, xyz-2041 xyz2...@gmail.com wrote: Plugged in the GPS unit's serial cable into a Windows computer running WinOncore12 v1.0 (Build 37): http://www.google.com/#q=WinOncore12Installation.exe Seemed to work without any problems. Generated all sort of graphs and charts. Let it run and it told me exact latitude, longitude and height above sea level. Used an analog volt meter and from pin 5 (supposed to be ground), I only noticed voltage on pins 2 and 3. Pin 2 was going erratically negative once a second. I believe that this must be received data as per standards. Pin 3 was +5 volts, but dropping to -5 volts once per second. You did not mention how your Oncore receiver was being interfaced to your computer or it's model number. I use one of the TAPR boards and Oncore UT+ combination. The NTP refclock driver for the Oncore includes the code for receiving the PPS signal on the computer DCD pin. I've changed my configs a bit, /var/log/ntp.log and /var/log/ntpd.log don't show any errors. However, ntpq -c pe still doesn't show any response: GPS_NMEA(0) .GPS.0 l- 1600.000 0.000 0.001 PPS(0) .GPS.0 l- 1600.000 0.000 0.001 GPS_ONCORE(0) .GPS-. 0 l- 1600.000 0.000 0.001 You should not be using GPS_NMEA or PPS. The type 30 refclock communicates with the receiver using Motorola Binary protocol. You may need to use WinOncore to set your receiver communications to use the binary protocol or even better, reset the receiver to factory defaults. Your config files already have your position defined, so there is no need to have anything in your receiver at startup. The almanac will be received while NTP is settling down after startup. You will need to configure at least 4 other NTP servers to speed up the initial startup. The refclock code wants to have a synchronized NTP server before adding itself to the peer selection. I find about 30 minutes after a cold start my PPS LED will start to flash and I observe that my Oncore gets selected. - Create symbolic links: ln -s /dev/cuad0 /dev/oncore.pps.0 ln -s /dev/cuad0 /dev/oncore.serial.0 ln -s /dev/cuad0 /dev/gps0 ln -s /dev/cuad0 /dev/pps0d - Create /etc/devfs.conf links: link cuad0 pps0 link cuad0 gps0 link cuad0 oncore.pps.0 link cuad0 oncore.serial.0 I think that you will find that the symbolic links in /dev are not required and only the /etc/devfs.conf entries are all you will need. You won't need either pps0 or gps0 entries for anything. Only the oncore* stuff is needed for the refclock type 30. Tom --- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Local (own site) NTP servers.
On 2009-07-23, G8KBV g8kbvd...@googlemail.com wrote: Wonder if this will get posed, or returned to me.. Hi... Been lurking for a while. Also, been messing about trying to get a local (to me) GPS Disciplined NTP server working, based on David Taylor's work with FreeBSD, I think I have one of those configured OK, but I've got other issues with FreeBSD on that machine that sort of prevent me using it for unattended appliance use. It keeps generating system emails for the Root user, and I can't find out why! Other than its something about recovered editor files? Dave: You will probably not find a better timekeeper than using the FreeBSD machine. The resources required are very minimal compared to running any Windows version. You might try logging into the FreeBSD computer as root and reading the mail using the 'mail' command. Select the message number, after the message has been read, press the 'd' key. When all of the messages for root have been read, press the 'q' key to quit. That will clear all of root's unread messages. To redirect your syslog messages to the console instead of a file, edit the '/etc/syslog' file and point all of the entries to 'dev/console'. It is not a good idea to stop the log outputs by directing things to '/dec/null'. You might want to read some of them. The unrecovered editor sessions can be read by starting vi with the '-r' flag. This is really about using FreeBSD for a timekeeper, you really can't go wrong. Your OS related setup questions should really be directed to a FreeBSD newsgroup, they are much better at handling questions and can always point you to a website for more in depth answers. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] GCC-4.2.3 Compiler Error in NTP-4.2.2p4
On 2008-02-10, Douglas Wells [EMAIL PROTECTED] wrote: [I'm replying to the original article rather than later follow-ups in order to include some original error messages.] In article [EMAIL PROTECTED], Thomas Laus [EMAIL PROTECTED] writes: timer_gettime and the associated data structure struct itimerspec are part of the POSIX REALTIME option, and are not supported in FreeBSD 6. (I have seen some documentation that they are available in the imminently available FreeBSD 7 line.) Thus, the issue is almost certainly not with the gcc compiler but rather the configuration of the NTP distribution: it shouldn't have chosen to use timer_create but rather setitimer. In looking at the NTP distribution, it's not clear to me why this should fail. Are you sure that you started with a clean distribution tree? I recently compiled and installed ntp-4.2.4p4 on FreeBSD 6.3-RELEASE using the FreeBSD ports system (and the default gcc 3.4.6), and it compiled and now operates without any obvious errors. I note, however, that the FreeBSD people have provided two small patch files -- both associated with configuring the stock NTP distribution for use on the various release versions of FreeBSD. I just tried configuring that version of ntp using the supplied configuration tools (i.e., w/o the FreeBSD patch files), and it properly detected the lack of timer_create (i.e., it wrote /* #undef HAVE_TIMER_CREATE */ in the top level config.h). It also compiled successfully using gcc 4.3.0 20071221. So, I really would suspect stale configuration files on your system. I'm not sure of the level of your programming experience as this compiler error should have been relatively simple to diagnose given access to the NTP source, the grep command, and the FreeBSD man pages; yet you appear to be running a version of FreeBSD from the source repository (rather than a released system). In any case, I would suggest strongly that you consider using the FreeBSD ports system as it drastically reduces the stress associated with maintaining third-party system software. You could start by reading the FreeBSD handbook and/or the ports man page, both of which are part of the standard FreeBSD installation. Douglas: My update of NTP was via the ports system. The compiler update to GCC-4.2.3_20080130 also was done via the 'portupgrade' system. One of my other applications requires GCC 4.3 instead of the GCC-3.4.6 that is part of the base system. That was why I mentioned that ntp-4.2.2p4 compiled fine on another computer that was running the base system compiler and not GCC-4.2.3xxx. I will contact the maintainer of the NTP port on FreeBSD and see if he has any insight into why the port configuration was not able to detect that I was running FreeBSD 6 and did not have the POSIX Realtime Option. Thanks for the reply. It gives me (and others) some insight into how things work. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] GCC-4.2.3 Compiler Error in NTP-4.2.2p4
I tried to upgrade my ntp version running on a FreeBSD 6.3-STABLE system this morning and received the following error: if cc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I../libopts -I/usr/local/include -O2 -fno-strict-aliasing -pipe -Wall -Wcast-qual -Wmissing-prototypes -Wpointer-arith -Wshadow -Wstrict-prototypes -MT ntp_timer.o -MD -MP -MF .deps/ntp_timer.Tpo -c -o ntp_timer.o ntp_timer.c; then mv -f .deps/ntp_timer.Tpo .deps/ntp_timer.Po; else rm -f .deps/ntp_timer.Tpo; exit 1; fi ntp_timer.c: In function `reinit_timer': ntp_timer.c:104: warning: implicit declaration of function `timer_gettime' ntp_timer.c:105: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:105: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:106: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:108: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:109: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:111: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:111: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:112: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:113: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:115: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:116: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:117: warning: implicit declaration of function `timer_settime' ntp_timer.c: In function `init_timer': ntp_timer.c:170: warning: implicit declaration of function `timer_create' ntp_timer.c:182: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:182: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:183: error: invalid use of undefined type `struct itimerspec' ntp_timer.c:183: error: invalid use of undefined type `struct itimerspec' ntp_timer.c: At top level: ntp_timer.c:91: error: storage size of `itimer' isn't known *** Error code 1 Stop in /usr/ports/net/ntp. ! net/ntp (ntp-4.2.2p4) (new compiler error) The compiler is GCC-4.2.3_20080130 and the ntp version that I was attempting to upgrade to was ntp-4.2.2p4. This version was able to be upgraded using the default GCC compiler on another system. It would appear that GCC-4.2.3 does not like something in the 'ntp_timer.c' program. Is there something that I need to do for the upgrade to complete successfully? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
