Re: bind fails with sig11 on start

On Tue, Feb 16, 2010 at 10:40:37AM -0800, Doug Barton wrote:
> 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?

I needed to take care about gdb to run.
See my other mail about it.
gdb and ktrace on ARM are still tools which tend to fail quite often :(

> > [66]# cat /etc/rc.conf 
> > hostname="Please.tell.me.who.am.I"
> 
> Bonus points here for not ending in .am. :)

That's just a template entry.

> > 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.

Thanks for the pointer - I should disable it.
The system just has 64MB RAM, so large memory filesystems are out of
question.

> > 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.

This is a bit old - I will compare it with new features.

> > 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?

I need to recompile the kernel for this, because the  board has an
embedded switch which is setup hardcoded inside the kernel.
But I use this type of setup since a very long time including 7.0 on
the same board type.

> > /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.

Originally I used the default and just switched for testen.
[61]Please.tell.me.who.am.I# ls -al /etc/namedb/
total 32
drwxr-xr-x  6 root  wheel    512 Feb 16 18:47 .
drwxr-xr-x  3 root  wheel    512 Feb 15 19:30 ..
drwxr-xr-x  2 bind  wheel    512 Feb 15 18:07 dynamic
drwxr-xr-x  2 root  wheel    512 Feb 15 18:09 master
-rw-r--r--  1 root  wheel  13969 Feb 15 18:09 named.conf
-rw-r--r--  1 root  wheel   3015 Feb 15 18:09 named.root
-rw-------  1 bind  wheel     97 Feb 15 19:30 rndc.key
drwxr-xr-x  2 bind  wheel    512 Feb 15 18:07 slave
drwxr-xr-x  2 bind  wheel    512 Feb 15 18:07 working
[62]Please.tell.me.who.am.I# ls -al /etc/namedb
lrwxr-xr-x  1 root  wheel  21 Feb 15 20:36 /etc/namedb -> /var/named/etc/namedb

-- 
B.Walter <bernd_at_bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.