bind fails with sig11 on start

Doug Barton dougb at FreeBSD.org
Tue Feb 16 18:40:38 UTC 2010


On 2/15/2010 1:39 PM, Bernd Walter wrote:
> [62]# uname -a
> FreeBSD  9.0-CURRENT FreeBSD 9.0-CURRENT #0 r203927: Mon Feb 15 19:12:36 CET 2010     ticso at cicely14.cicely.de:/data/builder/arm-current/head/sys/arm/compile/FBOX  arm
> [64]# /etc/rc.d/named start
> Starting named.
> /etc/rc.d/named: WARNING: failed to start named
> 1.000u 0.000s 0:03.94 54.0%     7446+33509k 0+0io 17pf+0w
> Exit 1

Are you getting a core file? If so can you do a backtrace?

> [66]# cat /etc/rc.conf 
> hostname="Please.tell.me.who.am.I"

Bonus points here for not ending in .am. :)

> tmpmfs="AUTO"
> tmpsize="4m"
> tmpmfs_flags="-S -M"

FYI, that size of /tmp will probably not allow your periodic/weekly
process to generate a locate.database. IME you need a /tmp at least 2.5
times the size of that file in order for it to complete successfully.

> ntpdate_enable="YES"
> ntpdate_program="ntpdate"

IMO you'd be better off with a full path here, although this will
probably work for /usr/sbin/ntpdate. However you're actually better off
with the ntpd_sync_on_start option in any case.

> cloned_interfaces="vlan0 vlan1 vlan2 vlan3"
> ifconfig_vlan0="192.168.53.1/24 vlan 256 vlandev ate0"
> ifconfig_vlan1="vlan 257 vlandev ate0"
> ifconfig_vlan2="vlan 258 vlandev ate0"
> ifconfig_vlan3="vlan 259 vlandev ate0"

This is the only area that I have real questions about, since I haven't
done any work with vlans I'm not sure how named will respond to it. Is
it possible for you to try starting named with a plain vanilla network
setup?

> /etc/namedb isn't changed from distribution yet

Ok, since you're not chroot'ing it have you checked to make sure that
directory is populated? It shouldn't segfault even if it isn't, but nice
to cover all the bases.


hth,

Doug

-- 

	... and that's just a little bit of history repeating.
			-- Propellerheads

	Improve the effectiveness of your Internet presence with
	a domain name makeover!    http://SupersetSolutions.com/



More information about the freebsd-current mailing list