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"? Thanks for maintaining unbound in Debian. Arne -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-8-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages unbound depends on: ii adduser 3.132 ii init-system-helpers 1.65.2 ii libc6 2.36-9 ii libevent-2.1-7 2.1.12-stable-8 ii libnghttp2-14 1.52.0-1 ii libprotobuf-c1 1.4.1-1+b1 ii libpython3.11 3.11.2-6 ii libssl3 3.0.8-1 ii libsystemd0 252.6-1 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.06-4 Versions of packages unbound recommends: ii dns-root-data 2023010101 Versions of packages unbound suggests: ii apparmor 3.0.8-3 ii openssl 3.0.8-1 -- debconf-show failed
