[fli4l] chrony funktioniert nicht.

Kay Martinen kay at martinen.de
Sa Sep 28 16:44:12 CEST 2019


Hallo

Meine Chrony Konfig sieht so aus:

> OPT_CHRONY='yes'                # enable ntp time daemon (client/server)
>                                
> CHRONY_TIMESERVICE='no'         # enable additional rfc 868 compliant time
>                                 # service on port 37 (udp/tcp). Only needed if
>                                 # local clients don't speak ntp.
>                                 
>                                 # For advanced options see documentation.
>                                 # But in most cases you won't need this.
> CHRONY_TIMESERVER_N='3'
> CHRONY_TIMESERVER_1='192.168.1.1'
> CHRONY_TIMESERVER_2='192.168.1.2'
> CHRONY_TIMESERVER_3='pool.ntp.org'

Ergebnis im webUI

activity
> 0 sources online
> 0 sources offline
> 0 sources doing burst (return to online)
> 0 sources doing burst (return to offline)
> 0 sources with unknown address

sources
> 210 Number of sources = 0
> 
>   .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
>  / .- Source state '*' = current synced, '+' = combined , '-' = not combined,
> | /   '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
> ||                                                 .- xxxx [ yyyy ] +/- zzzz
> ||                                                /   xxxx = adjusted offset,
> ||         Log2(Polling interval) -.             |    yyyy = measured offset,
> ||                                  \            |    zzzz = estimated error.
> ||                                   |           |                         
> MS Name/IP address         Stratum Poll Reach LastRx Last sample
> ===============================================================================

sourcestats sieht genau so aus.

tracking
> Reference ID    : 127.127.1.1 ()
> Stratum         : 8
> Ref time (UTC)  : Thu May 31 12:19:05 2001
> System time     : 0.000000000 seconds fast of NTP time
> Last offset     : +0.000000000 seconds
> RMS offset      : 0.000000000 seconds
> Frequency       : 0.000 ppm fast
> Residual freq   : +0.000 ppm
> Skew            : 0.000 ppm
> Root delay      : 0.000000 seconds
> Root dispersion : 0.000001 seconds
> Update interval : 0.0 seconds
> Leap status     : Not synchronised

rtc.data
> RTC ref time (UTC) : Thu May 31 12:19:10 2001
> Number of samples  : 14
> Number of runs     : 9
> Sample span period :  851
> RTC is fast by     :     0.715362 seconds
> RTC gains time at  :   190.492 ppm

uptime sind hier 15 minuten. Das war aber auch früher nach Stunden das
gleiche Bild.

Mit chronyc auf der konsole bekomme ich

> chronyc> add server 192.168.1.1
> 501 Not authorised
> chronyc> allow all 192.168.1.0/24
> 501 Not authorised
> chronyc> cmdallow 192.168.1.0/24
> 501 Not authorised
> chronyc> cmdallow 127.0.0.1
> 501 Not authorised

Mache ich da was falsch?

Kay

-- 
Sent via SN (Eisfair-1)


Mehr Informationen über die Mailingliste Fli4L