Date: Wed, 18 Jan 2017 14:46:04 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 202129] dns/unbound: Can't have any UNBOUND logs with Syslog or Rsyslog Message-ID: <bug-202129-13-4rt8STEX8H@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-202129-13@https.bugs.freebsd.org/bugzilla/> References: <bug-202129-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202129 --- Comment #4 from jaap@NLnetLabs.nl --- Unbound logs always to syslog unless otherwise specified. To separate unbound messages I use in syslog.conf !unbound *.* /var/log/unbound.log and that works fine for years. I agree with Sergey that this is likely a syslog configuration problem. For remote logging on a remote machine I do think your configuration should look like !unbound *.* @remote_machine You can test whether the remote machine accept and process the packets with something like $ logger -h remote_machine -t unbound "Unbound log test" which should work with the standard syslogd. Note that your unbound is old, the current version is 1.6.0 Success! --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202129-13-4rt8STEX8H>