INTL 3:770/1 3:770/3
REPLYADDR cl@isbd.net
REPLYTO 3:770/3.0 UUCP
MSGID: b6993cf5
REPLY: 5157d6d6
PID: SoupGate-Win32 v1.05
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: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/220
SEEN-BY: 135/225 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1
SEEN-BY: 221/6 360 226/17 30 100 227/114 229/110 111 112 113 200 206
SEEN-BY: 229/307 317 400 426 428 470 550 616 664 700 240/1120 266/512
SEEN-BY: 267/800 282/1038 291/111 292/854 301/1 113 812 310/31 320/219
SEEN-BY: 322/757 335/364 341/66 342/200 396/45 460/58 633/280 712/848
SEEN-BY: 770/1 3 100 330 340 772/210 220 230 5020/400 1042 5058/104
SEEN-BY: 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
