Maintained by: NLnet Labs

[Unbound-users] Unbound not logging

W.C.A. Wijngaards
Tue Feb 4 13:35:51 CET 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Sofia,

Can you set the configuration option
chroot: ""
in unbound.conf?  By default it sets chroot and that only allows file
accesses inside the chroot directory.

Chroot is very good for security but these path issues are
frustrating.  You could locate the unbound.log file inside the chroot
path and specify its location by an absolute path and that should work
too and you then have chroot as well.

Best regards,
   Wouter

On 02/04/2014 01:33 PM, Sofía Silva Berenguer wrote:
> Wouter,
> 
> Thank you for that idea! I did what you said and I see the
> following message:
> 
> Could not open logfile /home/unbound/var/log/unbound.log: No such
> file or directory
> 
> However, the file DOES exist (I touch'd it):
> 
> [unbound at ns2 ~]$ ls -l /home/unbound/var/log total 0 -rw-rw-r-- 1
> unbound unbound 0 Feb  4 09:25 unbound.log
> 
> What's wrong?
> 
> Regards,
> 
> Sofía
> 
> El 04/02/14 09:44, W.C.A. Wijngaards escribió:
>> Hi Sofia,
> 
>> If you start unbound with '-d' from the commandline, it will log 
>> to the console for a while.  Maybe it will say why it cannot
>> log. Then you can ctrl-c unbound.
> 
>> Or you can strace that unbound invocation and see what file it 
>> opens and what happens.
> 
>> Best regards, Wouter
> 
>> On 02/04/2014 12:32 PM, Sofía Silva Berenguer wrote:
>>> Hi!
> 
>>> SELinux is disabled.
> 
>>> I tried touching var/log/unbound.log under the unbound install
>>>  directory /home/unbound/var/log/unbound.log) and changing the
>>>  logfile parameter to the new path and then restarted unbound
>>> and still nothing is being logged.
> 
>>> The permissions of the new log file are as follows:
> 
>>> -rw-rw-r-- 1 unbound unbound
> 
>>> I'm not using chroot. I installed Unbound in the home
>>> directory of the user "unbound". Could chroot be preventing
>>> unbound from logging anyway?
> 
>>> Thank you a lot for your comments!
> 
>>> Kind regards,
> 
>>> Sofía
> 
>>> El 04/02/14 05:51, W.C.A. Wijngaards escribió:
>>>> Hi Sofia,
> 
>>>> On 02/04/2014 03:36 AM, shmick at riseup.net wrote:
>>>>> que tal,
> 
>>>>> Sofía Silva Berenguer:
>>>>>> Hi!
>>>>>> 
>>>>>> I've installed Unbound on a Centos 6.5 server.
>>>>>> 
>>>>>> I've set it up not to use syslog and to log to the file 
>>>>>> /var/log/unbound.log. Verbosity level is 5:
>>>>>> 
>>>>>> use-syslog: no logfile: /var/log/unbound.log verbosity:
>>>>>> 5
>>>>>> 
>>>>>> Permissions for the log file are as follows:
>>>>>> 
>>>>>> -rw-r--r-- 1 unbound unbound
> 
>>>>> it might be a dir perms issue did you try changing to your
>>>>>  conf dir (ie. /usr/local/etc/unbound) ? drwxr-xr-x 4
>>>>> unbound unbound 4096 Feb  4 12:14
> 
>>>> chroot is another thing that could prevent logging.  Or 
>>>> SELinux.
> 
>>>> Best regards, Wouter
> 
>>>>>> 
>>>>>> However, the log file is empty. Unbound is not logging 
>>>>>> anything to the file.
>>>>>> 
>>>>>> Is there anything else I should set up?
>>>>>> 
>>>>>> Thank you a lot in advance for any help.
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> Sofía _______________________________________________ 
>>>>>> Unbound-users mailing list Unbound-users at unbound.net 
>>>>>> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
>>>>>>
>>>>>
>>>>>> 
_______________________________________________ Unbound-users
>>>>> mailing list Unbound-users at unbound.net 
>>>>> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
> 
> 
>>>> _______________________________________________ Unbound-users
>>>>  mailing list Unbound-users at unbound.net 
>>>> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
> 
> 
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJS8N6nAAoJEJ9vHC1+BF+Nb88P/RXb/uglBVPtKCMVIJcNz6H7
BygCGAsHqcPO/JSHeESv5PnerkBtPyzSQxws2+c30LL9Lcf1OSp5091Qej9vawXe
L03+C/fOxcXB83jqNeGG7mnYtryotmHuBjAAunzQT2moadESm7JAvUJ+2r0TuZ2i
f176vL6SgrcwFGNbmX9Iz/maEsVmO2JUg7HnMHCMnO9H9xnvtLN6es9ak5l2+Ykv
7oW7htK9re5eIHLtlM7yybNh9070r7ZhRMppGuLwhm6zxQ6JDZZR+Ne59QIAbxBz
8kb64sC/sOxe5pdvsQBwvreftxxAL5mP7Fw4iAPyc1MfRRTrVtd4z2qTU7d5jGLT
R8MYJo0Fug+xJoyRGPdIOBPLrWqcPC3BrXufUdqjzNZKDBs4MCerwC1UM/xsMPEW
zbyBN8lU/5b15rw+sXZzLG2NNbvODhsun+dwt7bvyYxSWB9Xzto0Qv4sxNzdYh31
sEx5hPWKRczddLHdT6WQ4bBXhSEOehCt9X1tmyVtt3UhdE5EW22Skp0wVtRrxqsy
X6MMQNRLcB1rJBpUXF8ZIjdREgZlBAvfqI3R71/7py3TdKzFLYaF9Riy/mNGj/Ll
73CdTbpoZSdDuJyTM/RWyIi2vz/K8pQEY0B6oMsvrKlots4vj+xFr3At1Ld+Xx6M
tmEnnvTl9nt5Ujh4B8iZ
=tpJv
-----END PGP SIGNATURE-----