Bug 13985 - knot-resolver starts but then stops with a fresh CU203 install
Summary: knot-resolver starts but then stops with a fresh CU203 install
Status: CLOSED DUPLICATE of bug 13982
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 tree / graph
 
Reported: 2026-05-23 13:26 UTC by Adolf Belka
Modified: 2026-05-23 14:14 UTC (History)
1 user (show)

See Also:

Attachments
screenshot of logs showing knot messages (56.00 KB, image/png)
2026-05-23 13:26 UTC, Adolf Belka 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adolf Belka 2026-05-23 13:26:01 UTC 
Created attachment 1711 [details]
screenshot of logs showing knot messages

I downloaded Core-Update 203 Development Build: next/99fe258d and installed it.

As it finished the install it said Starting knot-resolver [OK]

but then later on with starting ntp it failed to find the ipfire.pool.ntp.org locations.

I logged in and knot-resolver was not running.

I then checked the logs and found some failure messages about knot-resolver failing to load config.lua.

As this test system is on my VirtualBox vm and it does not provide text copying in the console window so I had to take a screenshot of the log. This is attached.
Comment 1 Adolf Belka 2026-05-23 13:30:49 UTC 
I tried starting knot-resolver and it again said OK and the status showed it running.
After about 15 seconds it stopped running again.
Comment 2 Stefan Schantl 2026-05-23 13:37:53 UTC 
This seems to be the same issue I found recently:

https://bugzilla.ipfire.org/show_bug.cgi?id=13982
Comment 3 Adolf Belka 2026-05-23 14:14:12 UTC 

*** This bug has been marked as a duplicate of bug 13982 ***