Your message dated Mon, 18 Apr 2022 02:04:01 +0300
with message-id <[email protected]>
and subject line Re: unbound: Fails to start
has caused the Debian Bug report #900028,
regarding unbound: Fails to start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
900028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900028
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: unbound
Version: 1.7.1-1
Severity: important
** I'm reporting this on a different machine that on which it occurs. **
On several -- but not all -- of my kvm instances, unbound 1.7.1-1 fails to
start.
I tried manually invoking start-stop-daemon via:
:; (start-stop-daemon --start --pidfile /run/unbound.pid --name unbound
--startas /usr/sbin/unbound -- "" )
(replicating what /etc/init.d/unbound does) and unbound complained:
usage: unbound [options]
start unbound daemon DNS resolver.
-h this help
-c file config file to read instead of /etc/unbound/unbound.conf
file format is described in unbound.conf(5).
-d do not fork into the background.
-v verbose (more times to increase verbosity)
Version 1.7.1
linked libs: libevent 2.1.8-stable (it uses epoll), OpenSSL 1.1.0h 27 Mar 2018
linked modules: dns64 python subnetcache respip validator iterator
BSD licensed, see LICENSE in source package for details.
Report bugs to [email protected]
I tried again adding "-v" as the $DAEMON_OPTS value, and that avoided
the above notice, but unbound did not run. Switching to '-dvv' got:
[1527191667] unbound[9076:0] notice: Start of unbound 1.7.1.
[1527191667] unbound[9076:0] debug: switching log to syslog
Killed
The syslog output was:
May 24 19:54:27 fine unbound: [9076:0] warning: did not exit gracefully last
time (9071)
May 24 19:54:27 fine unbound: [9076:0] debug: chdir to /etc/unbound
May 24 19:54:27 fine unbound: [9076:0] debug: drop user privileges, run as
unbound
May 24 19:54:27 fine unbound: [9076:0] debug: module config: "subnetcache
validator iterator"
May 24 19:54:27 fine unbound: [9076:0] notice: init module 0: subnet
May 24 19:54:27 fine unbound: [9076:0] debug: subnet: option registered (8)
May 24 19:54:27 fine unbound: [9076:0] notice: init module 1: validator
May 24 19:54:27 fine unbound: [9076:0] info: adding trusted key dlv.isc.org.
DNSKEY IN
May 24 19:54:27 fine unbound: [9076:0] notice: init module 2: iterator
May 24 19:54:27 fine unbound: [9076:0] debug: target fetch policy for level 0
is 3
May 24 19:54:27 fine unbound: [9076:0] debug: target fetch policy for level 1
is 2
May 24 19:54:27 fine unbound: [9076:0] debug: target fetch policy for level 2
is 1
May 24 19:54:27 fine unbound: [9076:0] debug: target fetch policy for level 3
is 0
May 24 19:54:27 fine unbound: [9076:0] debug: target fetch policy for level 4
is 0
One of the kvms didn't have unbound installed. Even there 1.7.1-1, once
installed, will not run.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages unbound depends on:
ii adduser 3.117
ii dns-root-data 2018013001
ii libc6 2.27-3
ii libevent-2.1-6 2.1.8-stable-4
ii libfstrm0 0.3.0-1+b1
ii libprotobuf-c1 1.2.1-2
ii libpython3.6 3.6.5-9
pn libssl1.1 <none>
ii libsystemd0 238-4
ii lsb-base 9.20170808
pn openssl <none>
ii unbound-anchor 1.7.1-1
unbound recommends no packages.
Versions of packages unbound suggests:
pn apparmor <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, 24 May 2018 20:03:36 +0000 [email protected] wrote:
Package: unbound
Version: 1.7.1-1
Severity: important
** I'm reporting this on a different machine that on which it occurs. **
On several -- but not all -- of my kvm instances, unbound 1.7.1-1 fails to
start.
I tried manually invoking start-stop-daemon via:
:; (start-stop-daemon --start --pidfile /run/unbound.pid --name unbound --startas
/usr/sbin/unbound -- "" )
(replicating what /etc/init.d/unbound does) and unbound complained:
usage: unbound [options]
I don't know what to do with this bugreport but to close it now.
Hint: do not run unbound with an empty argument.
Thanks,
/mjt
--- End Message ---
