From: chris@mshome.net   
      
   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 ).   
      
      
      
   --   
   Chris Elvidge, England   
   TEACHER IS NOT A LEPER   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)