Issue with logs not logging

Greetings again all,

I’m having an issue where unbound isn’t writing anything to the log-file I’m specifying.
My end game is doing a short log of each query (for informational purposes and testing)

my truncated config as it stands is this :

I’ve been reading the man pages and the documentation on the website and I believe this is the proper method to create a specific log.

verbosity: 3 * for queries*
logfile: “/etc/unbound/unboundLog.txt”

log-queries: yes

Is there something I’m missing? I’ve also taken ownership of the file through chown for the unbound user.

Thank you in advance ,

here is the full truncated config for perusing:

whitespace is not necessary, but looks cleaner.

verbosity number, 0 is least verbose. 1 is default.

verbosity: 3

print statistics to the log (for every thread) every N seconds.

Set to “” or 0 to disable. Default is disabled.

Needed for munin plugin

statistics-interval: 0

enable cumulative statistics, without clearing them after printing.

Needed for munin plugin

statistics-cumulative: no

enable extended statistics (query types, answer codes, status)

printed from unbound-control. default off, because of speed.

Needed for munin plugin

extended-statistics: yes

number of threads to create. 1 disables threading.

num-threads: 2

specify the interfaces to answer queries from by ip-address.

The default is to listen to localhost (127.0.0.1 and ::1).

specify 0.0.0.0 and ::0 to bind to all available interfaces.

specify every interface on a new ‘interface:’ labelled line.

The listen interfaces are not changed on reload, only on restart.

TRUNCATED

interface: ::0

interface: 192.0.2.153

interface: 192.0.2.154

interface: 2001:DB8::5

Hi Levi,

I'm having an issue where unbound isn't writing anything to the log-file
I'm specifying.

Could it be there are some conflicting options in
  include: /etc/unbound/conf.d/*.conf
?

Regards,
Yuri

Ownership might not be enough. Give us an ls -l
/etc/unbound/unboundLog.txt, also an ls -ld /var/log.

(use-syslog: no *should* be unnecessary, but I also fought with the same
issue and have it in my now working config. Also, log-queries parameter
is duplicated in your conf.)

And, stupid question: Did you restart?

j.