Bug 13993 - The ipfire.pool.ntp.org servers are not resolved when booting after install
Summary: The ipfire.pool.ntp.org servers are not resolved when booting after install
Status: MODIFIED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - - Unknown -
Assignee: Assigned to nobody - feel free to grab it and work on it
QA Contact:
URL:
Keywords:
Depends on:
Blocks: KRESD
  Show dependency treegraph
 
Reported: 2026-05-27 11:35 UTC by Adolf Belka
Modified: 2026-05-27 15:01 UTC (History)
1 user (show)

See Also:


Attachments
screenshot of messages log showing the ntpdate errors before knot is running (46.33 KB, image/png)
2026-05-27 11:35 UTC, Adolf Belka
Details
Screenshot of messages after a reboot (45.43 KB, image/png)
2026-05-27 11:44 UTC, Adolf Belka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adolf Belka 2026-05-27 11:35:06 UTC
Created attachment 1712 [details]
screenshot of messages log showing the ntpdate errors before knot is running

During the boot completion after doing an install of Development Build: next/9a45c759 the following message gets shown after the line Setting time on boot...

12:40:23 ntpdate[2717]:  Can't find host 0.ipfire.pool.ntp.org: Name or service not known (-2)
12:40:23 ntpdate[2717]:  Can't find host 1.ipfire.pool.ntp.org: Name or service not known (-2)
12:40:23 ntpdate[2717]:  no servers can be used, exiting

Both knot and ntp were found to be running.

Doing a reboot did not show those messages.

Repeated a fresh install and again the same message is shown.

At the first fresh install I ran ping -c4 0.ipfire.pool.ntp.org and got the response that 100% of packets lost. However doing a ping of ipfire.org or archlinux.org worked fine.
I then pressed the manual time update button in the WUI and after around 4 or 5 minutes the ping now worked.

On the second fresh install the ping of the 0.ipfire.pool.ntp.org server worked straight away.

Looking at the messages log it seems to me that the ntpupdate command is running just before know is running but ntp afterwards.
Comment 1 Adolf Belka 2026-05-27 11:44:41 UTC
Created attachment 1713 [details]
Screenshot of messages after a reboot

I just did a reboot and checked the messages log again (in attachment)

The same ntpupdate errors are shown but they did not get displayed in the console as previously.

The ntpupdate lines are now later in the sequence but still not after knot is fully running.
Comment 2 Michael Tremer 2026-05-27 15:01:19 UTC
Hello,

I added an extra script that does nothing else but wait until DNS is ready:

> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=4efa083cab701e199acb6b0b904bdc4278e93a35

It will wait for up to 120 seconds which I hope is enough for even rather slower systems to load all RPZs.

Could you please let me know if this fixes the problem?

As a side note, I have removed the time sync from the ntp initscript and created a hook script that will sync as soon as the system becomes online which seems to be a generally better approach than the "hope for the best":

> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=91a49f02ff9f79e5d11a839951fa47174fd1130e