Control: tag -1 + confirmed
On Tue, 09 May 2023 13:01:37 +0200 Arne Nordmark <nordm...@mech.kth.se> wrote:
Package: unbound
Version: 1.17.1-2
Severity: normal
Dear Maintainer,
When booting with resolvconf installed and the resolvconf update script
(/etc/resolvconf/update.d/unbound) executable, the unbound-resolvconf service
fails:
maj 09 10:47:20 systemd[1]: Started unbound-resolvconf.service - Unbound
asyncronous resolvconf update helper.
maj 09 10:47:20 unbound-helper[1291]: run-parts:
/etc/resolvconf/update.d/unbound exited with return code 1
maj 09 10:47:20 systemd[1]: unbound-resolvconf.service: Main process exited,
code=exited, status=1/FAILURE
maj 09 10:47:20 systemd[1]: unbound-resolvconf.service: Failed with result
'exit-code'.
At this point in booting, the network is not fully configured yet, and no file
in /run/resolvconf/interface contains any non-local nameserver info.
If the unbound-resolvconf service is restarted after nameserver info has been
added, it starts normally.
Could this behaviour be due to the exit code from "egrep -v" causing the script to fail,
since the script is started with "#!/bin/sh -e"?
This grep is exactly the cause here. I'll fix this part.
/mjt
