Unboung log empty Topic is solved

[manilx]

No I did not install this, didn't know how. Just followed you instructions. But configured logging to separate file.

Did install this though: https://www.cyberciti.biz/faq/dnstop-mo ... ll-prompt/

It's all very basic now......

[MichaIng]

Okay, I see we have that monitor screenshot in our logs. Probably not the best idea to show something there that requires a lot of additional setup. But we'll anyway tune those logs based on experience/feedback. I meanwhile updated our default config file to sort things and give some more information: https://github.com/MichaIng/DietPi/blob ... bound.conf

[manilx]

True....

I will use the new config file and put my changes in there.

Thank You!

[manilx]

Okay, I see we have that monitor screenshot in our logs. Probably not the best idea to show something there that requires a lot of additional setup. But we'll anyway tune those logs based on experience/feedback. I meanwhile updated our default config file to sort things and give some more information: https://github.com/MichaIng/DietPi/blob ... bound.conf

PS: I edited the dietpi.con file in/etc/unbound/unbound.conf.d

There is an unbound.conf in /etc/unbound. It then refers to the other one....


Which file should I now use? Thinking about a future dietpi update....

[MichaIng]

Ah, this file is installed as /etc/unbound/unbound.conf.d/dietpi.conf. I just gave it the name unbound.conf so that the filename alone in the repository shows what it is for. /etc/unbound/unbound.conf should be kept as it is so that all files from the sub directory are loaded.

[manilx]

After uncomenting the log file option in your new conf: logfile: "/var/log/unbound.log" and restarting the service the log file is not created...

I had to

Code: Select all

touch /var/log/unbound.log

and

Code: Select all

chown unbound /var/log/unbound.log

for it to start working.

[MichaIng]

Yes, this is the natural downside of the usual service setup: Log files and/or directories mostly need to be pre-created so that the service user can access.