Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28873 - Unbound Doesn't Allow Log Changes & Stop Causes 'Fail'

Attached to Project: Arch Linux
Opened by Das (DasFox) - Monday, 12 March 2012, 06:25 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 13 March 2012, 07:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Unbound doesn't seem to respect the option 'Logfile:' it will not log to a file of your choice with this.

This is what I have and it does nothing;

logfile: "/var/log/unbound.log"

This is my complete unbound.conf; (I'm just using this with dnssec-trigger)

server:
username: "unbound"
directory: "/etc/unbound"
auto-trust-anchor-file: /etc/unbound/root.key
logfile: "/var/log/unbound.log"
remote-control:
control-enable: yes


Also when Arch reboots or shuts down, the stop commend for /etc/rc.d/unbound does nothing, it just causes a 'Fail' to appear;

root@arch:~# /etc/rc.d/unbound stop

:: Stopping unbound daemon [Fail]

Additional info:
* package version(s)
unbound-1.4.16-1
This task depends upon

Closed by  Gaetan Bisson (vesath)
Tuesday, 13 March 2012, 07:14 GMT
Reason for closing:  Not a bug
Comment by Gaetan Bisson (vesath) - Monday, 12 March 2012, 07:38 GMT
To enable logfile use, you must create /var/log/unbound.log and chown it to unbound.

Stopping the daemon works for me. Are you sure the daemon is running when you attempt to stop it? What is the corresponding portion from unbound's log?
Comment by Das (DasFox) - Tuesday, 13 March 2012, 05:52 GMT
Ok after playing with it the daemon stopped and no more [Fail]

Ahh for the logs ok, I run unbound on Slack as well and just putting logfile: "/var/log/unbound.log" in unbound.conf automatically created the log on it's own, so this is it from Slack;

root@box:/var/log# ls -l unbound.log.old
-rw-r--r-- 1 root root 2415 Mar 12 11:13 unbound.log.old

So in Arch it should be as? (What's wrong with just root root?)

-rw-r--r-- 1 root unbound?


THANKS
Comment by Gaetan Bisson (vesath) - Tuesday, 13 March 2012, 06:28 GMT
The unbound daemon does not run as root but as the unbound user, so the easiest way for it to write logs is to a file owned by that user.

Loading...