From owner-freebsd-ports-bugs@freebsd.org  Wed Jan 18 14:46:03 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBB71CB5BE0
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Wed, 18 Jan 2017 14:46:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CAE2E1C19
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 18 Jan 2017 14:46:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0IEk3Dd030693
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 18 Jan 2017 14:46:03 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
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
Date: Wed, 18 Jan 2017 14:46:04 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jaap@NLnetLabs.nl
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2017 14:46:04 -0000

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.=