Date: Wed, 11 Jul 2007 13:16:54 +0200 From: Zbigniew Szalbot <zbigniew@szalbot.homedns.org> To: CK <ck@yourserveradmin.com> Cc: freebsd-questions@freebsd.org Subject: Re: named listening on LAN Message-ID: <0afaca5f39036975c53d0da321e208c0@szalbot.homedns.org> In-Reply-To: <4694BA6A.4030608@yourserveradmin.com> References: <4694BA6A.4030608@yourserveradmin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Thanks!
Zbigniew Szalbot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0afaca5f39036975c53d0da321e208c0>