Re: ntpq: No association ID's returned (while ntp/ntpq from Debian binaries works fine)

[Ottavio Caruso <ottavio2006-usenet2012%yahoo.com@localhost>]

On 08/10/2020 14:41, Ottavio Caruso wrote:
> Warning! Long post.
>
> $ uname -a
> Linux e130 4.9.0-13-amd64 #1 SMP Debian 4.9.228-1 (2020-07-05) x86_64 
> GNU/Linux
>
>
> Thanks Sijmen et al for fixing the net/ntp4 which now build and installs 
> fine.
>
> However, I'm running into trouble launching ntpd, both as deamon and 
> from the command line.

I just wanted to add that I've built ntp from source the canonical way 
(./configure && make) and it works as intended.


oc@e130:~/test/ntp-4.2.8p15$ sudo pkill ntpd
oc@e130:~/test/ntp-4.2.8p15$ sudo ./ntpd/ntpd  -c /usr/pkg/etc/ntp.conf 
-p /var/run/ntpd.pid -f /var/lib/ntp/ntp.drift -l /tmp/ntp-log
oc@e130:~/test/ntp-4.2.8p15$ ./ntpq/ntpq -p
     remote           refid      st t when poll reach   delay   offset 
 jitter
==============================================================================
 0.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000 
  0.000
 1.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000 
  0.000
 2.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000 
  0.000
 3.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000 
  0.000
 85.199.214.100  .GPS.            1 u    2   64    1   21.365   +0.905 
  0.442
 51.155.16.62 (5 .GPS.            1 u    2   64    1   42.678   +0.914 
  0.000


oc@e130:~/test/ntp-4.2.8p15$ cat /tmp/ntp-log
 8 Oct 15:37:53 ntpd[28266]: ntpd 4.2.8p15@1.3728-o Thu Oct  8 14:32:08 
UTC 2020 (1): Starting
 8 Oct 15:37:53 ntpd[28266]: Command line: ntpd/ntpd -c 
/usr/pkg/etc/ntp.conf -p /var/run/ntpd.pid -f /var/lib/ntp/ntp.drift -l 
/tmp/ntp-log
 8 Oct 15:37:53 ntpd[28266]: 
----------------------------------------------------
 8 Oct 15:37:53 ntpd[28266]: ntp-4 is maintained by Network Time 
Foundation,
 8 Oct 15:37:53 ntpd[28266]: Inc. (NTF), a non-profit 501(c)(3) 
public-benefit
 8 Oct 15:37:53 ntpd[28266]: corporation.  Support and training for 
ntp-4 are
 8 Oct 15:37:53 ntpd[28266]: available at https://www.nwtime.org/support
 8 Oct 15:37:53 ntpd[28266]: 
----------------------------------------------------
 8 Oct 15:37:53 ntpd[28268]: proto: precision = 0.123 usec (-23)
 8 Oct 15:37:53 ntpd[28268]: basedate set to 2020-09-26
 8 Oct 15:37:53 ntpd[28268]: gps base set to 2020-09-27 (week 2125)
 8 Oct 15:37:53 ntpd[28268]: Listen and drop on 0 v6wildcard [::]:123
 8 Oct 15:37:53 ntpd[28268]: Listen and drop on 1 v4wildcard 0.0.0.0:123
 8 Oct 15:37:53 ntpd[28268]: Listen normally on 2 lo 127.0.0.1:123
 8 Oct 15:37:53 ntpd[28268]: Listen normally on 3 wlp3s0 192.168.2.201:123
 8 Oct 15:37:53 ntpd[28268]: Listen normally on 4 lo [::1]:123
 8 Oct 15:37:53 ntpd[28268]: Listen normally on 5 wlp3s0 
[fe80::c5bd:65b2:fe0c:2417%3]:123
 8 Oct 15:37:53 ntpd[28268]: Listening on routing socket on fd #22 for 
interface updates
 8 Oct 15:37:53 ntpd[28268]: kernel reports TIME_ERROR: 0x2041: Clock 
Unsynchronized
 8 Oct 15:37:53 ntpd[28268]: kernel reports TIME_ERROR: 0x2041: Clock 
Unsynchronized
 8 Oct 15:37:54 ntpd[28268]: Soliciting pool server 81.21.65.168
 8 Oct 15:37:55 ntpd[28268]: Soliciting pool server 85.199.214.100
 8 Oct 15:37:55 ntpd[28268]: Soliciting pool server 129.250.35.250
 8 Oct 15:37:56 ntpd[28268]: Soliciting pool server 176.58.127.165
 8 Oct 15:37:56 ntpd[28268]: Soliciting pool server 134.0.16.1
 8 Oct 15:37:57 ntpd[28268]: Soliciting pool server 176.58.109.199
 8 Oct 15:37:57 ntpd[28268]: Soliciting pool server 51.155.16.62
 8 Oct 15:37:57 ntpd[28268]: Soliciting pool server 178.79.145.244
 8 Oct 15:37:58 ntpd[28268]: Soliciting pool server 185.83.169.27
 8 Oct 15:37:58 ntpd[28268]: Soliciting pool server 193.150.34.2
 8 Oct 15:37:59 ntpd[28268]: Soliciting pool server 85.199.214.101
 8 Oct 15:37:59 ntpd[28268]: Soliciting pool server 217.114.59.66
 8 Oct 15:38:00 ntpd[28268]: Soliciting pool server 178.62.16.103
 8 Oct 15:38:00 ntpd[28268]: Soliciting pool server 129.250.35.251



Please note that the long is not spitting those "syntax error"s despite 
it being the same config file.


--
Ottavio Caruso