BIND9 error in FreeBSD - errno2result.c:109: unexpected error?
stevek
stevek at onshore.com
Wed Aug 17 15:20:34 UTC 2005
On Wed, 17 Aug 2005, Mark Andrews wrote:
>
>> I have been having some issues with getting BIND 9.3 to work nicely on a
>> FreeBSD 5.3 box. It's configured to run in a chroot jail under the
>> /chroot directory, and when I run it, it seems to load fine, but during
>> the load process, I get these messages:
>>
>> Aug 16 16:28:36 [PROTECTED] named[13811]: starting BIND 9.3.1 -u named
>> -t /chroot -c /etc/named.conf
>> Aug 16 16:28:36 [PROTECTED] named[13811]: command channel listening on
>> 127.0.0.1#953
>> Aug 16 16:28:36 [PROTECTED] named[13811]: errno2result.c:109: unexpected
>> error:
>> Aug 16 16:28:36 [PROTECTED] named[13811]: unable to convert errno to
>> isc_result: 6: Device not configured
>>
>> While this doesn't appear to be affecting the nameserver, I'm trying to
>> avoid errors at all (especially "unexpected" errors). Has anyone
>> encountered anything like this at all? I've done the standard google
>> searching and only found one instance where there was a similar problem,
>> but that was chroot going to the wrong directory. That doesn't appear to
>> be the case with this one...
>>
>> /Chris
>
> Look at your mount options for the chroot area. In particular
> "nodev".
>
> Mark
I'm jumping in for Chris, as he's out for the next few days.
The vol is mounted normaly:
/dev/da0s1e /chroot ufs rw 2 2
Here is the /dev in chroot:
drwxr-xr-x 2 root named 512 Aug 16 14:48 .
drwxr-xr-x 7 root named 512 Aug 15 11:02 ..
srwxrw-rw- 1 root named 0 Aug 16 14:48 log
crwxrw-rw- 1 root named 1, 3 Aug 12 12:44 null
crwxrw-rw- 1 root named 1, 8 Aug 12 12:44 random
crwxrw-rw- 1 root named 1, 5 Aug 12 12:44 zero
TIA -- Steve
More information about the bind-users
mailing list