CEST time is not correct

Mahmood Naderan <[email protected]>
Newsgroups gmane.comp.time.chrony.user
Message-ID <CADa2P2XmGkvHdv-x_-9TQtrTVySocHU+UgJZHejPO37FpGeBfQ@mail.gmail.com>
Hi,
I have a problem with the time set on my Ubuntu 20.04 which uses chrony.
As you can see below

$ sudo hwclock --systohc
$ date
Wed 19 Oct 2022 09:04:03 PM CEST
$ timedatectl status
               Local time: Wed 2022-10-19 21:04:54 CEST
           Universal time: Wed 2022-10-19 19:04:54 UTC
                 RTC time: Wed 2022-10-19 19:04:54
                Time zone: Europe/Brussels (CEST, +0200)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
$ cat </dev/tcp/time.nist.gov/13
59871 22-10-19 17:06:38 19 0 0 388.9 UTC(NIST) *


The date command says 9 PM CEST while the correct CEST time on my watch
(Brussel time) is 7 PM. So, although the time zone is set to Brussels CEST,
the time is +2 hour ahead.


Below, you can see that chrony is running while ntp is masked.

$ sudo systemctl status chrony
● chrony.service - chrony, an NTP client/server
     Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor
preset: enabled)
     Active: active (running) since Mon 2022-10-17 13:09:20 CEST; 2 days ago

$ sudo systemctl status ntp
● ntp.service
     Loaded: masked (Reason: Unit ntp.service is masked.)
     Active: inactive (dead) since Mon 2022-10-17 13:04:47 CEST; 2 days ago
   Main PID: 1773 (code=exited, status=0/SUCCESS)

$ cat /etc/chrony/chrony.conf
pool ntp.ubuntu.com        iburst maxsources 4
pool 0.ubuntu.pool.ntp.org iburst maxsources 1
pool 1.ubuntu.pool.ntp.org iburst maxsources 1
pool 2.ubuntu.pool.ntp.org iburst maxsources 2
keyfile /etc/chrony/chrony.keys
driftfile /var/lib/chrony/chrony.drift
logdir /var/log/chrony
maxupdateskew 100.0
rtcsync
makestep 1 3

So, I was wondering why chrony is not correctly synchronized.
Any idea about that?


Regards,
Mahmood
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.