-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 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@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, [email protected] 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 [email protected] >>>>> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users >>>>> >>>> _______________________________________________ Unbound-users >>>> mailing list [email protected] >>>> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users > > >>> _______________________________________________ Unbound-users >>> mailing list [email protected] >>> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlLw3iwACgkQ6pdkzarU619r9wD/UHO1muP/XhX6u40L7jrv3sgC Cty5iUr9o/U6YndxquUA/3n502aUxVinb4dOCzcwDf0zflbEY3YmaRBApf7f3x8d =M7eB -----END PGP SIGNATURE----- _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
