From owner-freebsd-questions@FreeBSD.ORG Wed Jul 11 11:49:04 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8375316A400 for ; Wed, 11 Jul 2007 11:49:04 +0000 (UTC) (envelope-from d.hill@yournetplus.com) Received: from duane.dbq.yournetplus.com (duane.dbq.yournetplus.com [65.124.230.214]) by mx1.freebsd.org (Postfix) with ESMTP id 611DC13C44C for ; Wed, 11 Jul 2007 11:49:04 +0000 (UTC) (envelope-from d.hill@yournetplus.com) Received: from [192.168.1.10] (unknown [192.168.1.1]) by duane.dbq.yournetplus.com (Postfix) with ESMTP id 0FF276D428 for ; Wed, 11 Jul 2007 11:50:14 +0000 (UTC) Date: Wed, 11 Jul 2007 11:50:13 +0000 (UTC) From: Duane Hill X-X-Sender: d.hill@duane.dbq.yournetplus.com To: freebsd-questions@freebsd.org In-Reply-To: <0afaca5f39036975c53d0da321e208c0@szalbot.homedns.org> Message-ID: <20070711114109.D9624@duane.dbq.yournetplus.com> References: <4694BA6A.4030608@yourserveradmin.com> <0afaca5f39036975c53d0da321e208c0@szalbot.homedns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: named listening on LAN X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2007 11:49:04 -0000 On Wed, 11 Jul 2007 at 13:16 +0200, zbigniew@szalbot.homedns.org confabulated: > > Hello, > > On Wed, 11 Jul 2007 14:09:30 +0300, CK wrote: >> Zbigniew Szalbot wrote: >>> Now bind does not die but but it cannot find the log file: >>> logging channel 'simple_log' file '/var/log/named/nlog': file not found >>> >>> ls /var/log/named/* >>> /var/log/named/nlog >>> >>> Why would named not be able to find the log when it is there? The nlog >> file >>> is owned by user bind and grup bind. >> >> As a wild guess, your named may be running in a chrooted jail, so you >> may want to check /var/named/var/log/named > > I did try that before. I do not have /var/named/var/log/named but I do have > /var/named/var/log/ and I created a file there, gave it appropriate > ownership but messages returned the same error about not being able to find > a file > logging{ > channel simple_log { > file "/var/named/var/log/nlog"; > severity info; > print-time yes; > print-severity yes; > print-category yes; > }; > category default{ > simple_log; > }; > }; > > Jul 11 13:06:03 szalbot named[3319]: starting BIND 9.3.3 -t /var/named -u > bind > Jul 11 13:06:03 szalbot named[3319]: command channel listening on > 127.0.0.1#953 > Jul 11 13:06:03 szalbot named[3319]: command channel listening on ::1#953 > Jul 11 13:06:03 szalbot named[3319]: logging channel 'simple_log' file > '/var/named/var/log/nlog': file not found > Jul 11 13:06:03 szalbot named[3319]: isc_log_open '/var/named/var/log/nlog' > failed: file not found I have it working with this: logging { channel namedlog { file "/var/log/nlog"; severity info; print-time yes; print-severity yes; print-category yes; }; category default { namedlog; }; }; When I restarted named, the nlog file was created in /var/named/var/log automatically: home# ls -lo /var/named/var/log/nlog -rw-r--r-- 1 bind wheel - 1253 Jul 11 11:43 /var/named/var/log/nlog If I add the flag into rc.conf to shut off chrooting, logging changes to: /var/log/nlog ----- _|_ (_| |