Date: Wed, 11 Jul 2007 11:50:13 +0000 (UTC) From: Duane Hill <d.hill@yournetplus.com> To: freebsd-questions@freebsd.org Subject: Re: named listening on LAN Message-ID: <20070711114109.D9624@duane.dbq.yournetplus.com> In-Reply-To: <0afaca5f39036975c53d0da321e208c0@szalbot.homedns.org> References: <4694BA6A.4030608@yourserveradmin.com> <0afaca5f39036975c53d0da321e208c0@szalbot.homedns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <ck@yourserveradmin.com> 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
-----
_|_
(_| |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070711114109.D9624>