RPI 4B.
Rebooted. Clock wrong.
1hr later, clock still wrong?
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
RPI 4B.
Rebooted. Clock wrong.
1hr later, clock still wrong?
WTF?
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.
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
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.
Make sure that the route to the internet isn't
blocked.
timesyncd is looking for time.
/etc/systemd/timesyncd.conf.
doing.
druck <news@druck.org.uk> wrote:
On 09/04/2024 17:00, The Natural Philosopher wrote:I have bookworm running on two systems, one is a 2Gb Pi 4B and the
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.
other is an ancient Beaglebone Black. Both show the right time
without any intervention from me. I checked and the Pi 4B is running systemd-timesyncd. ...., and the BBB is also running systemd-timesyncd.
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.
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 restoreYes, bookworm is surpisingly unstable.
the way I did things in Bullseye.
If possible Id like to get systemd working properly
---druck
And none of this is well documented. As someone remarked about CMAKE, "software that cannot be used because *no one knows how it works*, is useless"
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.
timesyncd works fine. Make sure that the route to the internet isn't blocked. Use the command timedatectl show-timesync --all to see where timesyncd is looking for time. You can always specify NTP servers in /etc/systemd/timesyncd.conf. Use timedatectl status to see what it is doing.
systemd should just stick to being an init system.
---druck
Yes, bookworm is surpisingly unstable.
If possible Id like to get systemd working properly
The Natural Philosopher <tnp@invalid.invalid> writes:
And none of this is well documented. As someone remarked about CMAKE,
"software that cannot be used because *no one knows how it works*, is
useless"
Who remarked that and why? I fairly like cmake but I can't say I've used
it a lot.
If you upgrade in place from Bullseye, despite the warnings, it is rock solid.
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?
timesyncd works fine.
On 09/04/2024 23:32, Knute Johnson wrote:
timesyncd works fine.
Perhaps, but I prefer to run NTP everywhere, even on my Windows PCs.
One management UI, not several. I've seen other issues with bookworm, too.
I installed BIND which normally works out of the box.
On 4/11/24 04:10, The Natural Philosopher wrote:
I installed BIND which normally works out of the box.
I'm curious why you did that and why you didn't mention it in your first post?
On 11/04/2024 14:46, Knute Johnson wrote:
On 4/11/24 04:10, The Natural Philosopher wrote:I had no idea thåt there was a DNS issue. I haven't modified BINDS configuration, but now its *working*.
I installed BIND which normally works out of the box.
I'm curious why you did that and why you didn't mention it in your
first post?
???
On 4/11/24 11:21, The Natural Philosopher wrote:
On 11/04/2024 14:46, Knute Johnson wrote:
On 4/11/24 04:10, The Natural Philosopher wrote:I had no idea thåt there was a DNS issue. I haven't modified BINDS
I installed BIND which normally works out of the box.
I'm curious why you did that and why you didn't mention it in your
first post?
configuration, but now its *working*.
???
So I'm still curious, why did you install bind?
On 11/04/2024 21:49, Knute Johnson wrote:
On 4/11/24 11:21, The Natural Philosopher wrote:
On 11/04/2024 14:46, Knute Johnson wrote:
On 4/11/24 04:10, The Natural Philosopher wrote:I had no idea thåt there was a DNS issue. I haven't modified BINDS
I installed BIND which normally works out of the box.
I'm curious why you did that and why you didn't mention it in your
first post?
configuration, but now its *working*.
???
So I'm still curious, why did you install bind?
I wanted a proper caching DNS server on my home network. One that I
could use to put local machines on. This PI is to be the house server. Storage. Media. DNS. TV.
I've always used bind to do that. Usually it just works.
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 915 |
Nodes: | 10 (1 / 9) |
Uptime: | 20:04:11 |
Calls: | 12,168 |
Calls today: | 4 |
Files: | 186,520 |
Messages: | 2,233,909 |