#994157 ntp: I cannot start a local network dedicated NTP server for some reason. Previosly I had working server. all clients receive 10.19.10.1: Server dropped: strata too high.

Package:
ntp
Source:
ntpsec
Submitter:
richman1000000
Date:
2021-09-13 12:57:02 UTC
Severity:
important
Tags:
#994157#5
Date:
2021-09-12 21:41:45 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***
#994157#10
Date:
2021-09-13 06:19:31 UTC
From:
To:
Hello.
Many years ago i just installed ntp and used it.
but now it is not working.
here is step by step reproduction.

1. on server : apt-get purge ntp
2. on server: apt-get install ntp, openned port 123 in tcp and udp
3. on the client do "ntpdate -vd 10.19.10.1"

Error:

 >10.19.10.1: Server dropped: strata too high
 >server 10.19.10.1, port 123
 >stratum 16, precision -24, leap 11, trust 000


Tried on ntp server:
adding "restrict 10.19.10.0 mask 255.255.255.224 nomodify notrap"
"server 127.127.1.0
fudge 127.127.1.0 stratum 10"

"server 10.19.10.0
fudge 10.19.10.0 stratum 10"

Expected : time will be synced with my own server.

Regards,
Rinat
#994157#15
Date:
2021-09-13 07:47:59 UTC
From:
To:
Am 13.09.21 um 08:19 schrieb richman1000000d@gmail.com:

Hi,

Do you want your ntpd to sync to an internet source or to a local clock
only?

You likely just have to wait for a few minutes before ntpd is fully
synced and stabilized.

On the server run

ntpq

and then enter

peers

Bernhard
#994157#22
Date:
2021-09-13 12:26:46 UTC
From:
To:
Hi.

client machines must sync only with my NTP server. the server itself
syncing with standard pools.

Today I made another vm the new NTP server.
For some reason it work on another machine. version is the same "Ver.
4.2.8p12"

here is output of the failing machine.

ntpq> peers
      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
ntpq>

I think like there is a problem with ipv6 of some sort since failing
machine is the only with IPV6 address internet . But I don't know how to
check this. For now I will use new vm.
I guess if someone will interact with this but too they will report/reopen.

Regards,
Rinat
#994157#27
Date:
2021-09-13 12:52:39 UTC
From:
To:
Am 13.09.21 um 14:26 schrieb richman1000000d@gmail.com:

Hi,

It is obviously not syncing, it should look similar to this.

ntpq> peers
      remote           refid      st t when poll reach   delay   offset
  jitter
==============================================================================
-ec2-3-121-254-2 192.53.103.108   2 u  339 1024   77   16.953   -1.666 
  5.481
+mail.klausen.dk 193.67.79.202    2 u   84 1024  377   15.092   +1.568
  0.580
+time.cloudflare 10.71.14.51      3 u  841 1024  377   15.649   -1.827
  0.534
*time1.hs-augsbu 131.188.3.220    2 u   88 1024  377   26.345   -0.052
  0.849

IPv6 only generally works fine with ntpd, although only
2.debian.pool.ntp.org is carrying IPv6 hosts. But it should sync.

Can you resolve "2.debian.pool.ntp.org" on your system (with host or
ping)? Are you sure your Port 123 is open in the outbound direction?

Bernhard