<div dir="ltr"><div>Thanks, guys!</div><div>I'm running chroot on /etc/unbound.</div><div><br></div><div>I followed this guide to compile unbound on my machine: <a href="https://pastebin.com/UUjss5aY">https://pastebin.com/UUjss5aY</a></div><div>Some initial values there made use of /etc/unbound instead of /var/log/unbound so after I compiled unbound-1.13.0, I changed the paths to point to /var/log/unbound</div><div><br></div><div>The log file user is set to unbound with write permissions, but seems it's not aware of its location (?)</div><div>The <i>unbound-checkconf</i> command is failing as well. It feels like the solution is not complicated, yet I'm unsure how to fix it or if I should try to compile all over again.</div><div>I'd rather try to fix it, if it's ok to ask for such type of help over this thread. <br></div><div><br></div><div><span style="font-family:monospace"><b>pi@raspberrypi:/etc/unbound $</b> <span style="color:rgb(0,0,255)">grep chroot unbound.conf</span><br> <b><span style="color:rgb(255,0,0)">chroot</span></b>: "/etc/unbound"<br><b><br></b></span></div><div><span style="font-family:monospace"><b>pi@raspberrypi:/etc/unbound $</b> <span style="color:rgb(0,0,255)">ls -l /var/log/unbound/unbound.log</span><br>-rw-r--r-- 1 unbound unbound 5553 Oct 21 00:16 /var/log/unbound/unbound.log<br><b><br></b></span></div><div><span style="font-family:monospace"><b>pi@raspberrypi:/etc/unbound $</b> <span style="color:rgb(0,0,255)">unbound-checkconf</span><br>/etc/unbound/var/log/unbound: <b>No such file or directory</b><br>[1609510296] unbound-checkconf[2288:0] <b><span style="color:rgb(255,0,0)">fatal error</span></b>: logfile directory does not exist<br><b><br></b></span></div><div><span style="font-family:monospace"><b>pi@raspberrypi:/etc/unbound $</b> <span style="color:rgb(0,0,255)">sudo systemctl status unbound</span><br>● unbound.service - Unbound DNS resolver<br> Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)<br> <b><span style="color:rgb(56,118,29)">Active: active</span></b> (running) since Sat 2021-01-02 00:46:44 AEDT; 25min ago<br> Process: 457 ExecStartPre=/usr/sbin/unbound-anchor -r /etc/unbound/root.hints -a /etc/unbound/root.key (code=exited, status=0/SUCCESS)<br> Main PID: 483 (unbound)<br> Tasks: 1 (limit: 2063)<br> CGroup: /system.slice/unbound.service<br> └─483 /usr/sbin/unbound -c /etc/unbound/unbound.conf -d<br><br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 199.7.83.42 port 53<br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 198.41.0.4 port 53<br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 199.7.91.13 port 53<br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 198.97.190.53 port 53<br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 199.7.91.13 port 53<br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 193.0.14.129 port 53<br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 199.7.91.13 port 53<br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 192.33.4.12 port 53<br>Jan 02 00:46:49 raspberrypi unbound[483]: [1609508809] unbound[483:0] error: udp connect failed: Network is unreachable for 192.58.128.30 port 53<br>Jan 02 00:46:50 raspberrypi unbound[483]: [1609508810] unbound[483:0] info: generate keytag query _ta-4f66. NULL IN<br><b><br></b></span></div><div><span style="font-family:monospace"><b>pi@raspberrypi:/etc/unbound $</b> <span style="color:rgb(0,0,255)">sudo lsof -i :53</span><br>COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME<br>pihole-FT 829 pihole 4u IPv4 27749 0t0 UDP *:domain<br>pihole-FT 829 pihole 5u IPv4 27750 0t0 TCP *:domain (LISTEN)<br>pihole-FT 829 pihole 6u IPv6 27751 0t0 UDP *:domain<br>pihole-FT 829 pihole 7u IPv6 27752 0t0 TCP *:domain (LISTEN)</span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 2 Jan 2021 at 01:05, Jaap Akkerhuis <<a href="mailto:jaap@nlnetlabs.nl" target="_blank">jaap@nlnetlabs.nl</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Joe Abley via Unbound-users writes:<br>
<br>
<br>
><br>
> On Jan 1, 2021, at 14:15, Gil Levy via Unbound-users <<a href="mailto:unbound-users@lists.nlnetlabs.nl" target="_blank">unbound-users@lists.nlnetlabs.nl</a>> wrote:<br>
><br>
> >> Are you running unbound in a chroot(8)?<br>
> > I don't know how to check that.<br>
><br>
> man chroot<br>
><br>
> for a better description of what chroot does, and how the interpretation of<br>
> absolute pathnames differs inside and outside the chroot namespace.<br>
><br>
> man man<br>
><br>
> if you're unfamiliar with how manual pages are organised. If you don't have<br>
> manual pages installed and can't add them as a package, it should not be hard<br>
> to find collections of manual pages for your particular distribution if you<br>
> search for them.<br>
><br>
> grep chroot unbound.conf<br>
<br>
For a running unbound, do<br>
<br>
unbound-control get_option chroot<br>
<br>
to get the value it is using.<br>
<br>
> seems like a reasonable place to start to find configuration options in your<br>
> environment that relate to chroot. You might also refer to the unbound <br>
> documentation to understand the defaults and the specific meaning of individual <br>
> parameters.<br>
<br>
Especially take notice what<br>
<br>
man unbound.conf<br>
<br>
tells you about the interaction between chroot and absolute path names. <br>
<br>
><br>
> Another common error is to try and write log files to places where the process<br>
> generating them does not have the necessary permissions. Determine the<br>
> user that unbound is running as and check the permissions in the filesystem.<br>
<br>
Or the directories are missing after the chroot took place...<br>
<br>
jaap<br>
<br>
</blockquote></div>