I just moved PBS (v2.2-7) to new hardware, and I've been fighting chrony trying to get it to sync the time.
Everything else in my network syncs to the same server just fine, and even a PVE host also using chrony syncs just fine to it. But for some reason PBS won't
It is receiving response back fron the NTP server, as seen above. But its just not taking the time ?
/etc/chrony/chrony.conf
Despite the clock not saying its synchronized, the reported OS time is spot on to my local workstation clock.
What is going on here? Why isn't chrony taking the time?
Code:
root@pbs:/var/log# chronyc activity
200 OK
1 sources online
0 sources offline
0 sources doing burst (return to online)
0 sources doing burst (return to offline)
0 sources with unknown address
root@pbs:/var/log# chronyc sourcestats -V
Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
==============================================================================
pi.hole 0 0 0 +0.000 2000.000 +0ns 4000ms
root@pbs:/var/log# chronyc ntpdata
Remote address : 172.20.5.2 (AC140502)
Remote port : 123
Local address : 172.20.25.2 (AC141902)
Leap status : Not synchronised
Version : 4
Mode : Server
Stratum : 0
Poll interval : 6 (64 seconds)
Precision : -24 (0.000000060 seconds)
Root delay : 0.000000 seconds
Root dispersion : 0.000000 seconds
Reference ID : 7F000001 ()
Reference time : Thu Jan 01 00:00:00 1970
Offset : +0.000000000 seconds
Peer delay : 0.000000000 seconds
Peer dispersion : 0.000000000 seconds
Response time : 0.000000000 seconds
Jitter asymmetry: +0.00
NTP tests : 111 101 0000
Interleaved : No
Authenticated : No
TX timestamping : Kernel
RX timestamping : Kernel
Total TX : 9
Total RX : 9
Total valid RX : 9
root@pbs:/var/log# chronyc serverstats
NTP packets received : 0
NTP packets dropped : 0
Command packets received : 13
Command packets dropped : 0
Client log records dropped : 0
NTS-KE connections accepted: 0
NTS-KE connections dropped : 0
Authenticated NTP packets : 0
Local time: Wed 2022-11-23 18:52:40 EST
Universal time: Wed 2022-11-23 23:52:40 UTC
RTC time: Wed 2022-11-23 23:52:40
Time zone: America/New_York (EST, -0500)
System clock synchronized: no
NTP service: active
RTC in local TZ: noEverything else in my network syncs to the same server just fine, and even a PVE host also using chrony syncs just fine to it. But for some reason PBS won't
It is receiving response back fron the NTP server, as seen above. But its just not taking the time ?
/etc/chrony/chrony.conf
Code:
# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usable directives.
# Include configuration files found in /etc/chrony/conf.d.
confdir /etc/chrony/conf.d
# Use Debian vendor zone.
server 172.20.5.2 prefer iburst
# Use time sources from DHCP.
sourcedir /run/chrony-dhcp
# Use NTP sources found in /etc/chrony/sources.d.
sourcedir /etc/chrony/sources.d
# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys
# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift
# Save NTS keys and cookies.
ntsdumpdir /var/lib/chrony
# Uncomment the following line to turn logging on.
#log tracking measurements statistics
# Log files location.
logdir /var/log/chrony
# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
maxdistance 16.0
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can’t be used along with the 'rtcfile' directive.
rtcsync
# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3
# Get TAI-UTC offset and leap seconds from the system tz database.
# This directive must be commented out when using time sources serving
# leap-smeared time.
leapsectz right/UTCDespite the clock not saying its synchronized, the reported OS time is spot on to my local workstation clock.
What is going on here? Why isn't chrony taking the time?
Last edited:
