From: cl@isbd.net   
      
   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.   
   >   
   I don't think your poblem is with systemd-timesyncd, it's with the   
   network.  You appear to have an unstable connection which is why it   
   keeps saying "Network configuration changed, trying to establish   
   connection."   
      
   Also that IP address doesn't work for me either:-   
      
       chris@bbb$ host 2.debian.pool.ntp.org   
       2.debian.pool.ntp.org has address 162.159.200.123   
       2.debian.pool.ntp.org has address 80.87.128.222   
       2.debian.pool.ntp.org has address 178.62.68.79   
       2.debian.pool.ntp.org has address 134.0.16.1   
       2.debian.pool.ntp.org has IPv6 address 2a00:2381:19c6::200   
       2.debian.pool.ntp.org has IPv6 address 2603:c020:c00d:af00:195:242:99:71   
       2.debian.pool.ntp.org has IPv6 address 2a0f:85c0::50   
       2.debian.pool.ntp.org has IPv6 address 2a00:fd80:aaaa:ffff::eeee:ff1   
       chris@bbb$ host 193.150.34.2   
       2.34.150.193.in-addr.arpa domain name pointer time.rdg.uk.as44574.net.   
       chris@bbb$ ping 193.150.34.2   
       PING 193.150.34.2 (193.150.34.2) 56(84) bytes of data.   
       ^C   
       --- 193.150.34.2 ping statistics ---   
       9 packets transmitted, 0 received, 100% packet loss, time 8172ms   
      
       chris@bbb$   
      
   I don't know why your system is trying 162.159.200.123 and not the   
   alternatives, mine seem to find a working IP OK.  Is your DNS good?   
      
   --   
   Chris Green   
   ·   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)