-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Matthijs,
> Wouter enjoys his christmas holidays at the moment, so let me answer > your e-mail. And a deserved one i guess :) > It seems to work fine on Linux. Could you increase the verbosity level > to 4 (debug logs), or provide actual debugger output (for example, gdb > --args unbound -d -vvvv; then 'run' and 'bt'), so we can see what is > actual going wrong? I'm running Unbound on OpenBSD 4.4. And I think I know whats happening: it has something to do with the chrooted environment. This is the debug output: #unbound -d -vvvv >output.log [1230032843] unbound[22786:0] notice: Start of unbound 20081218. [1230032843] unbound[22786:0] warning: increased limit(open files) from 128 to 300 [1230032843] unbound[22786:0] debug: creating udp4 socket 127.0.0.1 53 [1230032843] unbound[22786:0] debug: creating tcp4 socket 127.0.0.1 53 [1230032843] unbound[22786:0] debug: creating tcp4 socket 127.0.0.1 953 [1230032843] unbound[22786:0] debug: switching log to syslog /etc/unbound.conf:32: error: cannot open include file '/sidn/unbound/etc/unbound-sidn-overrides.conf': No such file or directory read /etc/unbound.conf failed: 1 errors in configuration file We have absolute paths in the unbound.conf, but the reload command work in the chrooted invironment. How to solve this? Regards, Marc -----BEGIN PGP SIGNATURE----- Version: 9.6.3 (Build 3017) wj8DBQFJUNBubp5Jj0JFvnwRAk67AJ9viFCeitbfP2ZUYjdbkz+5Fv82bACg65Hv 9xFUTS5Pi3dDxellvywBAKg= =TMVI -----END PGP SIGNATURE----- _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
