Mailinglist Archive: opensuse-bugs (3354 mails)

< Previous Next >
[Bug 982145] New: unbound fails to start chrooted
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 29 May 2016 19:46:38 +0000
  • Message-id: <bug-982145-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=982145


Bug ID: 982145
Summary: unbound fails to start chrooted
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: openSUSE 13.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: darin@xxxxxxxxxx
Reporter: suse-beta@xxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: Beta-Customer
Blocker: ---

I tried to enable chroot in unbound.conf:

chroot: "/var/lib/unbound"

The result is that unbound (to be exact: unbound-checkconf) refuses to start
with

May 29 21:40:58 tux unbound-checkconf[14288]: [1464550858]
unbound-checkconf[14288:0] fatal error: config file /etc/unbound/unbound.conf
is not inside chroot /var/lib/unbound


Full status output:

# rcunbound status
* unbound.service - Unbound recursive Domain Name Server
Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Sun 2016-05-29 21:40:58 CEST; 3s
ago
Process: 14114 ExecStart=/usr/sbin/unbound -d $UNBOUND_OPTIONS (code=exited,
status=0/SUCCESS)
Process: 14288 ExecStartPre=/usr/sbin/unbound-checkconf (code=exited,
status=1/FAILURE)
Process: 14276 ExecStartPre=/usr/bin/sudo -u unbound /usr/sbin/unbound-anchor
-a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem (code=exited,
status=0/SUCCESS)
Main PID: 14114 (code=exited, status=0/SUCCESS)

May 29 21:40:57 tux systemd[1]: Starting Unbound recursive Domain Name
Server...
May 29 21:40:57 tux sudo[14276]: root : TTY=unknown ; PWD=/ ; USER=unbound
; COMMAND=/usr/sbin/unbound-anchor -a /var/lib/unbound/root.key -c
/etc/unbound/icannbundle.pem
May 29 21:40:57 tux sudo[14276]: pam_unix(sudo:session): session opened for
user unbound by (uid=0)
May 29 21:40:58 tux unbound-checkconf[14288]: [1464550858]
unbound-checkconf[14288:0] fatal error: config file /etc/unbound/unbound.conf
is not inside chroot /var/lib/unbound
May 29 21:40:58 tux systemd[1]: unbound.service: Control process exited,
code=exited status=1
May 29 21:40:58 tux systemd[1]: Failed to start Unbound recursive Domain Name
Server.
May 29 21:40:58 tux systemd[1]: unbound.service: Unit entered failed state.
May 29 21:40:58 tux systemd[1]: unbound.service: Failed with result
'exit-code'.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
Follow Ups