Re: 1.1.6 build fails on FC30
On 12-04-2020 17:35, Udo van den Heuvel via devel wrote: > On 12-04-2020 17:25, ASSI via devel wrote: >>> # ppswatch /chroot/ntpd/dev/pps0 >>> (shows similar output) >> >> Good, but does ntpd see the same? > > Well, devices look like this: And pps debug messages: # dmesg|grep event [ 408.583301] pps pps0: PPS event at 1586955482.000224958 [ 408.783290] pps pps0: PPS event at 1586955482.200221526 [ 409.583276] pps pps0: PPS event at 1586955483.000216947 [ 409.783279] pps pps0: PPS event at 1586955483.200224550 [ 410.583256] pps pps0: PPS event at 1586955484.000219902 [ 410.783257] pps pps0: PPS event at 1586955484.200224501 [ 411.583231] pps pps0: PPS event at 1586955485.000214265 [ 411.783227] pps pps0: PPS event at 1586955485.200217887 [ 412.583211] pps pps0: PPS event at 1586955486.000214565 [ 412.783209] pps pps0: PPS event at 1586955486.200217559 [ 413.583183] pps pps0: PPS event at 1586955487.000207532 [ 413.783188] pps pps0: PPS event at 1586955487.200214856 [ 414.583161] pps pps0: PPS event at 1586955488.000204200 [ 414.783164] pps pps0: PPS event at 1586955488.200212572 [ 415.583138] pps pps0: PPS event at 1586955489.000201916 [ 415.783140] pps pps0: PPS event at 1586955489.200209170 [ 416.583115] pps pps0: PPS event at 1586955490.000202426 [ 416.783117] pps pps0: PPS event at 1586955490.200206886 We can recognise the 200 ms pulse length of the gps. And some messages: # grep ntp /var/log/messages|grep -v NTSc Apr 15 14:57:52 doos ntpd[13057]: INIT: ntpd ntpsec-1.1.8 2019-08-02T00:00:00Z: Starting Apr 15 14:57:52 doos ntpd[13057]: INIT: Command line: /usr/sbin/ntpd -u ntp:ntp -g -N -p /var/run/ntpd.pid Apr 15 14:57:52 doos ntpd[13058]: INIT: precision = 1.466 usec (-19) Apr 15 14:57:52 doos ntpd[13058]: INIT: successfully locked into RAM Apr 15 14:57:52 doos ntpd[13058]: CONFIG: readconfig: parsing file: /etc/ntp.conf Apr 15 14:57:52 doos ntpd[13058]: AUTH: authreadkeys: reading /etc/ntp/keys Apr 15 14:57:52 doos ntpd[13058]: AUTH: authreadkeys: added 0 keys Apr 15 14:57:52 doos ntpd[13058]: CONFIG: 'monitor' cannot be disabled while 'limited' is enabled Apr 15 14:57:52 doos ntpd[13058]: INIT: Using SO_TIMESTAMPNS Apr 15 14:57:52 doos ntpd[13058]: IO: Listen and drop on 0 v6wildcard [::]:123 Apr 15 14:57:52 doos ntpd[13058]: IO: Listen and drop on 1 v4wildcard 0.0.0.0:123 Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 2 lo 127.0.0.1:123 Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 3 eth0 192.168.10.70:123 Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 4 lo [::1]:123 Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 5 eth0 [fd00:c0a8:a00:1::70]:123 Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 6 eth0 [2001:981:a812:0:b62e:99ff:fe92:5264]:123 Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 7 eth0 [fe80::b62e:99ff:fe92:5264%2]:123 Apr 15 14:57:52 doos ntpd[13058]: IO: Listening on routing socket on fd #24 for interface updates Apr 15 14:57:52 doos ntpd[13058]: SYNC: Found 14 servers, suggest minsane at least 3 Apr 15 14:57:52 doos ntpd[13058]: INIT: MRU 10922 entries, 13 hash bits, 65536 bytes Apr 15 14:57:52 doos ntpd[13058]: INIT: OpenSSL 1.1.1d FIPS 10 Sep 2019, 1010104f Apr 15 14:57:52 doos ntpd[13057]: 2020-04-15T14:57:52 ntpd[13057]: INIT: ntpd ntpsec-1.1.8 2019-08-02T00:00:00Z: Starting Apr 15 14:57:52 doos ntpd[13057]: 2020-04-15T14:57:52 ntpd[13057]: INIT: Command line: /usr/sbin/ntpd -u ntp:ntp -g -N -p /var/run/ntpd.pid Apr 15 14:57:56 doos ntpd[13058]: EX-REP: Count=1 Print=1, Score=0.500, M4 V4 from [2606:4700:f1::1]:123, lng=84 Apr 15 14:57:56 doos ntpd[13058]: EX-REP: e400 4e54534e 68b79e8c 7aba3928 01040024 ab1ba90e 83b3398e b52bc6be 4326e979 982bfea5 f885c05a 718c2243 47483da8 Apr 15 14:59:01 doos ntpd[13058]: EX-REP: Count=2 Print=2, Score=0.996, M4 V4 from [2606:4700:f1::1]:123, lng=84 Apr 15 14:59:01 doos ntpd[13058]: EX-REP: e400 4e54534e fcbd5032 7356fdea 01040024 e445b468 d2d8f320 ea459fd8 86e68505 33cf4112 3f7d5a7d 9f2969df 4627b682 So no error messages about gps/NMEA. ntpq: # ntpq -pn remote refid st t when poll reach delay offset jitter === NMEA(0) .GPS.0 l 15 64 377 0. 0. 0.0019 192.168.10.98 .GPS.1 u 12 16 377 0.3325 0.8299 0.1966 fd00:c0a8:a00:1::1 .GPS.1 u4 64 377 0.3462 0.8608 0.7197 2606:4700:f1::1 .NTS. 16 0- 64 0 0. 0. 0.0019 2405:fc00:0:1::123 .PPS.1 8- 64 377 172.2785 2.9948 0.8281 2001:470:e815::24 .PP
Re: 1.1.6 build fails on FC30
> So no error messages about gps/NMEA. > NMEA(0) .GPS.0 l 15 64 377 > 0. 0. 0.0019 What's the line for that in your ntp.conf? Any fudge lines? What does stty say for the baud rate? What sort of GPS device ? What baud rate is it using? Try stopping ntpd and running cat /dev/whatever That should show some NMEA sentences. The 377 reach shows that something is working but the rest of the line shows that it isn't. The NMEA driver is strange in that it tries to merge both the NMEA and PPS. I guess that's good if it works, but it makes debugging things like this complicated. I run with 2 separate servers. Here is the chunk from my ntp.conf server 127.127.20.0 prefer path /dev/ttyAMA0 mode 0x010011 fudge 127.127.20.0 flag1 0# disable PPS fudge 127.127.20.0 time2 0.600# Fixup offset server 127.127.22.0# PPS signal, needs prefer fudge 127.127.22.0 flag2 0# Rising edge That turns into: *NMEA(0) .GPS.0 l 31 64 377 0. 10.9381 27.6977 oPPS(0) .PPS.0 l 30 64 377 0. 0.0570 0.0004 -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
LOGIF
Anybody object if I remove it? It's used to conditionalize logging of various messages from refclocks. You will see them if your ntp.conf has" logconfig +clockall (and won't see them by default) include/ntp_syslog.h:#define LOGIF(nlog_suffix, msl_args) \ ntpd/refclock_trimble.c:LOGIF(CLOCKINFO, (LOG_NOTICE, "%s open at %s", ntpd/refclock_nmea.c: LOGIF(CLOCKINFO, (LOG_NOTICE, "%s serial %s open at %s bps", ntpd/refclock_nmea.c: LOGIF(CLOCKINFO, (LOG_NOTICE, "%s PPS %s opened", ntpd/refclock_gpsd.c: LOGIF(CLOCKINFO, ntpd/refclock_gpsd.c: LOGIF(CLOCKINFO, ntpd/ntp_wrapdate.c:LOGIF(CLOCKINFO, (LOG_INFO, They are all very low volume that are useful for debugging, especially when somebody asks for help on users@ or devel@ -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: LOGIF
Yo Hal! On Wed, 15 Apr 2020 18:37:50 -0700 Hal Murray via devel wrote: > Anybody object if I remove it? Well, you also said: > They are all very low volume that are useful for debugging, > especially when somebody asks for help on users@ or devel@ Why remove something you think is useful? I'm always happy while debugging when I find a good log message right where I am looking. RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 g...@rellim.com Tel:+1 541 382 8588 Veritas liberabit vos. -- Quid est veritas? "If you can't measure it, you can't improve it." - Lord Kelvin pgpjqdKIeUIA4.pgp Description: OpenPGP digital signature ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: LOGIF
Gary said: >> They are all very low volume that are useful for debugging, >> especially when somebody asks for help on users@ or devel@ > Why remove something you think is useful? Ahh/oops. I didn't want to remove the messages, just remove the LOGIF wrapper so the messages would always appear. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: LOGIF
Yo Hal! On Wed, 15 Apr 2020 18:49:18 -0700 Hal Murray via devel wrote: > Gary said: > >> They are all very low volume that are useful for debugging, > >> especially when somebody asks for help on users@ or devel@ > > > Why remove something you think is useful? > > Ahh/oops. > > I didn't want to remove the messages, just remove the LOGIF wrapper > so the messages would always appear. Sorry, I misread that. Some people want verbose logging, some none. Choice is good. As long as there is an on/off switch of some sort. RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 g...@rellim.com Tel:+1 541 382 8588 Veritas liberabit vos. -- Quid est veritas? "If you can't measure it, you can't improve it." - Lord Kelvin pgpxO3gY4e65B.pgp Description: OpenPGP digital signature ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: LOGIF
Gary said: > Sorry, I misread that. Some people want verbose logging, some none. Choice > is good. As long as there is an on/off switch of some sort. Yes and no. The on/off switch is obscure enough and the amount of logging that can be turned on/off is small enough that the choice isn't worth it in this case. My opinon. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: LOGIF
Yo Hal! On Wed, 15 Apr 2020 19:49:18 -0700 Hal Murray via devel wrote: > Gary said: > > Sorry, I misread that. Some people want verbose logging, some > > none. Choice is good. As long as there is an on/off switch of some > > sort. > > Yes and no. > > The on/off switch is obscure enough and the amount of logging that > can be turned on/off is small enough that the choice isn't worth it > in this case. My opinon. Then hang it off another switch. I love excessive logging, but it does burn out SD cards quickly. UNIX is choice. RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 g...@rellim.com Tel:+1 541 382 8588 Veritas liberabit vos. -- Quid est veritas? "If you can't measure it, you can't improve it." - Lord Kelvin pgpeE64ua_W_n.pgp Description: OpenPGP digital signature ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: LOGIF
Gary said: > Then hang it off another switch. Care to suggest "another switch"? > but it does burn out SD cards quickly. >From my initial message: They are all very low volume I was close to saying they all happened only during initialization, but at least one is termination, and I think the one logging a GPS week roll over can happen in the middle of a run. If that causes troubles with your SD card, you have more serious problems. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
