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: Chris Elvidge <chris@mshome.net>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Buggy bookworm?
Date: Wed, 10 Apr 2024 11:38:49 +0100
Organization: A noiseless patient Spider
Lines: 71
Message-ID: <uv5q7q$tblv$1@dont-email.me>
References: <uv3om7$agu2$1@dont-email.me> <uv49gp$efer$3@dont-email.me>
 <uv5m2f$s7bl$3@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 10 Apr 2024 10:38:51 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="7616467486427571e4badaedae840cdc";
	logging-data="962239"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18tTuwzi20tzzkeB9ptqNeUcB148CdoUSI="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1 Lightning/5.4
Cancel-Lock: sha1:FHtANedEwOQi5dlPcl9F3LIjdrA=
In-Reply-To: <uv5m2f$s7bl$3@dont-email.me>
Content-Language: en-GB
Bytes: 3747

On 10/04/2024 at 10:27, The Natural Philosopher wrote:
> On 09/04/2024 21: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.
>>
> 
> Its very very weird.
> 
> It is systemd.timesyncd, and it sometimes says it cant connect, and very 
> very occasionally seems to connect.
> 
> Apr 09 20:45:51 Coriolanus systemd-timesyncd[547]: Network configuration 
> changed, trying to establish connection.
> Apr 09 20:45:53 Coriolanus systemd-timesyncd[547]: No network 
> connectivity, watching for changes.
> Apr 09 20:45:58 Coriolanus systemd-timesyncd[547]: Network configuration 
> changed, trying to establish connection.
> Apr 09 20:46:08 Coriolanus systemd-timesyncd[547]: Timed out waiting for 
> reply from 193.150.34.2:123 (2.debian.pool.ntp.org).
> Apr 09 20:46:18 Coriolanus systemd-timesyncd[547]: Timed out waiting for 
> reply from 77.104.162.218:123 (2.debian.pool.ntp.org).
> Apr 09 20:46:28 Coriolanus systemd-timesyncd[547]: Timed out waiting for 
> reply from 95.215.175.2:123 (2.debian.pool.ntp.org).
> Apr 09 20:55:54 Coriolanus systemd-timesyncd[547]: Network configuration 
> changed, trying to establish connection.
> Apr 09 20:55:55 Coriolanus systemd-timesyncd[547]: No network 
> connectivity, watching for changes.
> Apr 09 20:56:00 Coriolanus systemd-timesyncd[547]: Network configuration 
> changed, trying to establish connection.
> Apr 09 21:30:38 Coriolanus systemd-timesyncd[547]: Contacted time server 
> 51.89.151.183:123 (0.debian.pool.ntp.org).
> 
> That is, it hasn't actually contacted a time server in 12 hours.
> 
> And the clock is about 2 seconds out.
> 
> 
> 
>> It's one of the many parts of Bookworm I've had to junk and restore 
>> the way I did things in Bullseye.
>>
> Yes, bookworm is surpisingly unstable.
> 
> If possible Id like to get systemd working properly
> 
> 
> 
>> ---druck
>>
> 

I'd tend to agree with Chris Green - it's a network problem. What's the 
default route? Do you have >1 network on the box?

The clock will stay "correct" without time syncronisation for some time. 
One thing I do with every new box is run 'fake-hwclock save' every 
minute (root crontab) so a reboot gets the nearly correct time immediately.

I've got bookworm running on a Model B Plus Rev 1.2 with no problems 
(yet <g>).



-- 
Chris Elvidge, England
TEACHER IS NOT A LEPER