Just installed 43 and I can't set my clock with NTP

Ask Fedora
1

I don’t know how to fix this. I tried to search but nothing I read makes any sense to me.

2

I’m sure this is the problem but have no idea how to fix.

I have fedora 42 on the bench right next to this machine, pugged into the same switch on the same subnet and it is fine.

chronyd[4868]: Can't synchronise: no selectable sources (8 unreachable sources)


$ chronyc sources
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^? 139-177-202-26.ip.linode>     0   8     0     -     +0ns[   +0ns] +/-    0ns
^? ntp.sfo.icanbwell.com         0   8     0     -     +0ns[   +0ns] +/-    0ns
^? sushi.ruselabs.com            0   8     0     -     +0ns[   +0ns] +/-    0ns
^? arm1.maxhost.io               0   8     0     -     +0ns[   +0ns] +/-    0ns
^? static.36.62.78.5.client>     0   8     0     -     +0ns[   +0ns] +/-    0ns
^? ip74-208-14-149.pbiaas.c>     0   8     0     -     +0ns[   +0ns] +/-    0ns
^? 155.248.196.28                0   8     0     -     +0ns[   +0ns] +/-    0ns
^? cambria.bitsrc.net            0   8     0     -     +0ns[   +0ns] +/-    0ns

Why does linux have to be like this..? I hate it so much.

4

Getting the unreachable status for all sources indicates it’s a networking issue, e.g. ISP firewall blocking port 123.

You can try mtr -u -P 123 pool.ntp.org and see how far it gets.

5

I’ll try the mtr command later this evening. Port123 is open on my router, I know that much.

I might be going back to 42 though. I have way bigger problems with 43 then just this NTP thing.

1 Like
6

If it worked in F42 in the same network, it’s going to be something else.

Please post your /etc/chrony.conf.

Was this a new installation? Maybe you accidentally clicked the NTS checkbox in the NTP configuration dialog, which doesn’t work with pool.ntp.org servers.

7

Maybe. I could see that happening. NTS sound like NTP. I will look.

8

here is chrony.conf (I cut out the commented lines)

pool 2.fedora.pool.ntp.org iburst
sourcedir /run/chrony-dhcp
driftfile /var/lib/chrony/drift
makestep 1.0 3
rtcsync
ntsdumpdir /var/lib/chrony
leapseclist /usr/share/zoneinfo/leap-seconds.list
logdir /var/log/chrony

Do you see anything?

9

I got nothing when running this command.

10

The config looks good to me.

If mtr doesn’t even print your local gateway, it’s probably a firewall configuration issue on your computer or router. If you remove -u -P 123, does it get further?

11

Well, I ended up installing F42. That went flawlessly including NTP.

I was just having way too many problems with F43. Boot loops, errors, black screens and the NTP. I just got the bad vibs from it, so I went back to the old version.

Sorry for wasting you guys time. I appreciate that you all were trying to help.

12

The same problem here: no clock sync after upgrade.
Contrary to the docs at Making sure you're not a bot! there is no chrony package.
Contrary to the docs at Making sure you're not a bot! there is no ntp package.
My chrony.conf file still points at our on-premise time server, but something is trying to query the NTP.org pool which is not present in any config files.
There is no updated documentation for f43 beyond release notes.
Who created this mess? Why? For what purpose?
WE ARE NOT PLAYING. WHEN YOU DELETE PACKAGES OR RENAME THEM, UPDATE THE DOCS FIRST.

13

Feel free to contributed updated documentation for anything you feel is sub-optimal.

14

Often issues like this are first seen on Fedora but appear on other distros as they move to newer kernels. Fedora packages what upstream provides, so it is faster to work with upstream https://chrony-project.org/. Note that some use cases require ntp or ntpsec.