Chrony won't sync time despite active peer, rrd update failed: time in past

ehammer

New Member
Jan 12, 2022
26
4
3
32
I just moved PBS (v2.2-7) to new hardware, and I've been fighting chrony trying to get it to sync 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: no


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
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/UTC

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?
 
Last edited:

ehammer

New Member
Jan 12, 2022
26
4
3
32
Hi,

did you check what journalctl -u chrony -e says?

Also some random thing I found on the internet regarding "Leap status : Not synchronised" [1]. Maybe this fixes your problem.


[1] https://www.thegeekdiary.com/leap-status-not-synchronised-on-running-chronyc-tracking/

journalctl -u chrony -e
Code:
Nov 25 08:00:56 pbs chronyd[527062]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Nov 25 08:00:56 pbs chronyd[527062]: Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/chrony.drift
Nov 25 08:00:56 pbs chronyd[527062]: Using right/UTC timezone to obtain leap second data
Nov 25 08:00:56 pbs chronyd[527062]: Loaded seccomp filter

Code:
root@pbs:~# chronyd -q 'server 172.20.5.2 iburst'
2022-11-25T13:00:34Z chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
2022-11-25T13:00:42Z No suitable source for synchronisation
2022-11-25T13:00:42Z chronyd exiting

The journal logs don't show any error.

The manual sync fails with the "no suitable source". I did confirm it is still receiving packets back from the ntp server.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!