[Bug 262995] dns/unbound: Not recorded in syslogd
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262995] dns/unbound: Not recorded in syslogd"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 02 Apr 2022 01:27:10 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262995 Bug ID: 262995 Summary: dns/unbound: Not recorded in syslogd Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: vfx9as@gmail.com CC: jaap@NLnetLabs.nl Flags: maintainer-feedback?(jaap@NLnetLabs.nl) CC: jaap@NLnetLabs.nl Not recorded in syslog unless local-unbound is restarted unbound-1.14.0.pkg: # pkg install unbound # unbound-control-setup /var/log/console.log kernel: Starting local_unbound. kernel: Waiting for nameserver to start... good -- Unbound can not record log because syslogd has not started kernel: Updating /var/run/os-release done. kernel: Creating and/or trimming log files. kernel: Updating motd:. kernel: Starting syslogd. -- After that, even if syslogd starts, unbound does not reopen the log, so it will continue to fail # sockstat | grep unb unbound unbound 452 3 udp6 ::1:53 *:* unbound unbound 452 4 tcp6 ::1:53 *:* unbound unbound 452 5 udp4 127.0.0.1:53 *:* unbound unbound 452 6 tcp4 127.0.0.1:53 *:* unbound unbound 452 7 stream -> ?? unbound unbound 452 8 stream -> ?? # grep unbou /var/log/all.log kernel: Starting unbound. -- unbound cannot be recorded in syslog # service unbound restart Stopping unbound. Waiting for PIDS: 452. Obtaining a trust anchor... Starting unbound. # sockstat | grep unb unbound unbound 758 3 udp6 ::1:53 *:* unbound unbound 758 4 tcp6 ::1:53 *:* unbound unbound 758 5 udp4 127.0.0.1:53 *:* unbound unbound 758 6 tcp4 127.0.0.1:53 *:* unbound unbound 758 7 dgram -> /var/run/logpriv unbound unbound 758 8 stream -> ?? unbound unbound 758 9 stream -> ?? # grep unbou /var/log/all.log kernel: Starting unbound. kernel: Starting unbound. unbound[758]: [758:0] notice: init module 0: validator unbound[758]: [758:0] notice: init module 1: iterator unbound[758]: [758:0] info: start of service (unbound 1.14.0). -- unbound can be recorded in syslog Where is the best restert? local-unbound also cause the same problem (bug #262844) -- You are receiving this mail because: You are the assignee for the bug.