It is clear that unbound(8) is not running.
Quote:
Originally Posted by Peter_APIIT
Does anyone know how to troubleshoot? The log file does not contains any things.
|
Output from the daemon, if any, will be stored (via socket) according to the configuration in /etc/syslog.conf. Depending on the type of message, information may appear in
/var/log/messages or in
/var/log/daemon. Look in both files for information. You mention a log file ... there are two. But there may not be any data there.
The rc.d(8) subsystem includes a diagnostic -d option that can show you if there are startup errors. See the man page, and run /etc/rc.d/unbound with this option enabled. You may receive messages which tell you why unbound refuses to start.
Lastly, please read the unbound(8) man page. There are two things in it that I would like you to take note of:
- The unbound command has a -d option. Starting unbound manually, with this option, will show you any messages produced on your console, which, will enable you to make configuration changes and test them rapidly, without resorting to the rc.d(8) subsystem or rebooting, then hunting through log files.
- The SEE ALSO section mentions the unbound-checkconf(8) program. Please use that tool, because I believe your configuration is in error.