| Summary: | knot-resolver starts but then stops with a fresh CU203 install | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Adolf Belka <adolf.belka> |
| Component: | --- | Assignee: | Assigned to nobody - feel free to grab it and work on it <nobody> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | - Unknown - | ||
| Priority: | - Unknown - | CC: | stefan.schantl |
| Version: | 2 | ||
| Hardware: | unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 13972 | ||
| Attachments: | screenshot of logs showing knot messages | ||
I tried starting knot-resolver and it again said OK and the status showed it running. After about 15 seconds it stopped running again. This seems to be the same issue I found recently: https://bugzilla.ipfire.org/show_bug.cgi?id=13982 |
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.