Named 9.3.0 && weird error at bootup

[Samuel Trommel]

Doug i appreciate your help, but it has nothing to with my config file... 

I migrated BIND 9.2.3 (Builded from ports) to the integrated BIND 9.3.0. The
problem is that my chrootpoint is setup wrong.

[23:57:06][root at freebsd:/var/named/etc/namedb]# ls -alF
total 18
drwxr-xr-x  9 root  wheel  512 Nov 15 21:02 ./
drwxr-xr-x  3 root  wheel  512 Nov 15 21:12 ../
drwxr-x---  2 root  wheel  512 Jul 13 13:53 bin/
drwxr-x---  2 bind  bind   512 Nov 15 19:22 dev/
drwxr-x---  2 root  wheel  512 Jul 14 18:31 etc/
drwxr-xr-x  2 bind  bind   512 Nov 16 21:55 log/
drwxr-x---  2 bind  bind   512 Jul 14 10:46 master/
drwxrwx---  2 bind  bind   512 Sep 21 14:33 slave/
drwxrwx---  4 bind  bind   512 Jul 13 13:53 var/

I mounted /var/named/etc/namedb, instead /var/named/. I will do some
maintance at the end of the week. I just need to create some devices with
'mknod' like null and random.

Greet,

Samuel Trommel

-----Original Message-----
From: owner-freebsd-stable at freebsd.org
[mailto:owner-freebsd-stable at freebsd.org] On Behalf Of Doug Barton
Sent: dinsdag 16 november 2004 3:29
To: Samuel Trommel
Cc: freebsd-stable at freebsd.org
Subject: Re: Named 9.3.0 && weird error at bootup

On Mon, 15 Nov 2004, Samuel Trommel wrote:

> Hello,
>
> Recently I upgraded from 5.2.1-release to 5.3-release. When I try to start
> named I get a weird error:
>
>
>
> Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t
> /var/named/etc/namedb/ -c /etc/named.conf

I'm assuming from these command line params that you have customized 
your local configuration? If so, that's fine, just wanted to be sure.

> Nov 15 19:23:12 freebsd named[1152]: command channel listening on
> 0.0.0.0#953
>
> Nov 15 19:23:12 freebsd named[1152]:
>
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:109
> : unexpected error:
>
> Nov 15 19:23:12 freebsd named[1152]: unable to convert errno to
isc_result:
> 6: Device not configured

This is indicative that you have an error in your config somewhere. I'd 
try named-checkconf, and make sure what you're specifying in the conf 
file matches the interfaces on your system.

Doug

-- 

     This .signature sanitized for your protection

_______________________________________________
freebsd-stable at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"