Path: ...!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: The Natural Philosopher <tnp@invalid.invalid>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Buggy bookworm?
Date: Wed, 10 Apr 2024 10:34:47 +0100
Organization: A little, after lunch
Lines: 87
Message-ID: <uv5mfn$s7bl$4@dont-email.me>
References: <uv3om7$agu2$1@dont-email.me> <uv49gp$efer$3@dont-email.me>
 <uv4flu$gbkq$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 10 Apr 2024 09:34:47 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="e74058edfa4524e2cb77282475e8c2ec";
	logging-data="925045"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+I2K/G4WhLvyWWKRI6EfiLqfbx6S/IGuc="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:vEv1EFdlm0UyjV/ZPM0WfYfqFVs=
Content-Language: en-GB
In-Reply-To: <uv4flu$gbkq$1@dont-email.me>
Bytes: 3847

On 09/04/2024 23:32, Knute Johnson wrote:
> On 4/9/24 15:47, druck wrote:
>> On 09/04/2024 17:00, The Natural Philosopher wrote:
>>> RPI 4B.
>>> Rebooted. Clock wrong.
>>> 1hr later, clock still wrong?
>>
>> Probably due to using systemd-timesyncd which I've never seen actuall 
>> working. Install the ntp service and it will work.
>>
>> It's one of the many parts of Bookworm I've had to junk and restore 
>> the way I did things in Bullseye.
>>
>> ---druck
>>
> 
> timesyncd works fine. 

No, it does not

> Make sure that the route to the internet isn't 
> blocked. 

Its fine


  Use the command timedatectl show-timesync --all to see where
> timesyncd is looking for time. 

LinkNTPServers=
SystemNTPServers=
RuntimeNTPServers=
FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 
2.debian.pool.ntp.org 3.debian.pool.ntp.org
ServerName=0.debian.pool.ntp.org
ServerAddress=51.89.151.183
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=34min 8s
NTPMessage={ Leap=0, Version=4, Mode=4, Stratum=2, Precision=-25, 
RootDelay=3.021ms, RootDispersion=106us, Reference=55C7D665, 
OriginateTimestamp=Wed 2024-04-10 10:01:40 BST, ReceiveTimestamp=Wed 
2024-04-10 10:01:40 BST, TransmitTimestamp=Wed 2024-04-10 10:01:40 BST, 
DestinationTimestamp=Wed 2024-04-10 10:01:40 BST, Ignored=no, 
PacketCount=36, Jitter=684us }
Frequency=-804732

  You can always specify NTP servers in
> /etc/systemd/timesyncd.conf.  

I basically uncommented everything that was commented out


Use timedatectl status to see what it is
> doing.
> 
timedatectl status
                Local time: Wed 2024-04-10 10:29:13 BST
            Universal time: Wed 2024-04-10 09:29:13 UTC
                  RTC time: n/a
                 Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
               NTP service: active
           RTC in local TZ: no

In order to get this far I had to edit that file and I disabled wlan0 on 
the Pi 4.
At some point it started working but doesn't seem to be *regularly* 
contacting anything last entry from

$systemctl status systemd-timesyncd.service

Apr 09 21:30:38 Coriolanus systemd-timesyncd[547]: Contacted time server 
51.89.151.183:123 (0.debian.pool.ntp.org)


-- 
     “I know that most men, including those at ease with problems of the 
greatest complexity, can seldom accept even the simplest and most 
obvious truth if it be such as would oblige them to admit the falsity of 
conclusions which they have delighted in explaining to colleagues, which 
they have proudly taught to others, and which they have woven, thread by 
thread, into the fabric of their lives.”

     ― Leo Tolstoy