Archlinux current amd64
Unbound 1.71
Try as I might Unbound is not writing to logfile: "/var/log/unbound.log"
and use-syslog: no.
Would appreciate if someone could let me know.
Archlinux current amd64
Unbound 1.71
Try as I might Unbound is not writing to logfile: "/var/log/unbound.log"
and use-syslog: no.
Would appreciate if someone could let me know.
Hi,
Archlinux current amd64
Unbound 1.71Try as I might Unbound is not writing to logfile: "/var/log/unbound.log"
and use-syslog: no.Would appreciate if someone could let me know.
Is unbound chrooted? If so, that would probably prevent it to access
to the /var/log directory. Look for the 'chroot' configuration option
in your unbound.conf file.
Sincerely.
Is unbound chrooted? If so, that would probably prevent it to access
to the /var/log directory. Look for the 'chroot' configuration option
in your unbound.conf file.
It is not chrooted but running in an unprivileged LXC container, though
that should not make a difference for Unbound writing its log inside the
container, or should it perhaps?
It is not chrooted but running in an unprivileged LXC container, though
that should not make a difference for Unbound writing its log inside the
container, or should it perhaps?
Have tried the below variations and each is met with the same outcome ->
error: Could not open logfile /var/log/unbound.log: No such file or
directory
1. no file unbound.log in /var/log and thus expecting unbound to create it
2. created file unbound.log in /var/log manually with mask 0755
3. set logfile: "/var/log/unbound.log"
4. set logfile: /var/log/unbound.log