Date: Fri, 24 Nov 2017 14:04:17 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 223842] dns/bind912: fails to start, stating possibly wrong reason for this Message-ID: <bug-223842-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223842 Bug ID: 223842 Summary: dns/bind912: fails to start, stating possibly wrong reason for this Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: mat@FreeBSD.org Reporter: emz@norma.perm.ru Flags: maintainer-feedback?(mat@FreeBSD.org) Assignee: mat@FreeBSD.org dns/bind912 from recent ports. Fails to start: Nov 24 15:49:53 g1fw1 named[26422]: starting BIND 9.12.0b2 <id:5b1e929> Nov 24 15:49:53 g1fw1 named[26422]: running on FreeBSD amd64 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017=20=20=20=20 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC Nov 24 15:49:53 g1fw1 named[26422]: built with '--localstatedir=3D/var' '--disable-linux-caps' '--disable-symtable' '--with-randomdev=3D/dev/random' '--with-libxml2=3D/usr/local' '--with-readline=3D-L/usr/local/lib -ledit' '--with-dlopen=3Dyes' '--sysconfdir=3D/usr/local/etc/namedb' '--disable-dns= tap' '--disable-filter-aaaa' '--disable-fixed-rrset' '--without-geoip' '--with-idn=3D/usr/local' '--enable-ipv6' '--with-libjson' '--disable-large= file' '--with-lmdb' '--with-python=3D/usr/local/bin/python2.7' '--disable-querytr= ace' '--enable-rpz-nsdname' '--enable-rpz-nsip' 'STD_CDEFINES=3D-DDIG_SIGCHASE= =3D1' '--enable-threads' '--without-gssapi' '--with-openssl=3D/usr' '--disable-native-pkcs11' '--with-dlz-filesystem=3Dyes' '--without-gost' '--prefix=3D/usr/local' '--mandir=3D/usr/local/man' '--infodir=3D/usr/local= /info/' '--build=3Damd64-portbld-freebsd11.1' 'build_alias=3Damd64-portbld-freebsd1= 1.1' 'CC=3Dcc' 'CFLAGS=3D-O2 -pipe -DLIBICONV_PLUG -fstack-protector -isystem /usr/local/include -fno-strict-aliasing' 'LDFLAGS=3D -fstack-protector' 'LIBS=3D-L/usr/l Nov 24 15:49:53 g1fw1 named[26422]: running as: named -t /var/named -u bind= -c /usr/local/etc/namedb/named.conf Nov 24 15:49:53 g1fw1 named[26422]: ---------------------------------------------------- Nov 24 15:49:53 g1fw1 named[26422]: BIND 9 is maintained by Internet Systems Consortium, Nov 24 15:49:53 g1fw1 named[26422]: Inc. (ISC), a non-profit 501(c)(3) public-benefit=20 Nov 24 15:49:53 g1fw1 named[26422]: corporation. Support and training for = BIND 9 are=20 Nov 24 15:49:53 g1fw1 named[26422]: available at https://www.isc.org/support Nov 24 15:49:53 g1fw1 named[26422]: ---------------------------------------------------- Nov 24 15:49:53 g1fw1 named[26422]: found 8 CPUs, using 8 worker threads Nov 24 15:49:53 g1fw1 named[26422]: using 7 UDP listeners per interface Nov 24 15:49:53 g1fw1 named[26422]: using up to 4096 sockets Nov 24 15:49:53 g1fw1 named[26422]: loading configuration from '/usr/local/etc/namedb/named.conf' Nov 24 15:49:53 g1fw1 named[26422]: reading built-in trusted keys from file '/usr/local/etc/namedb/bind.keys' Nov 24 15:49:53 g1fw1 named[26422]: using default UDP/IPv4 port range: [491= 52, 65535] Nov 24 15:49:53 g1fw1 named[26422]: using default UDP/IPv6 port range: [491= 52, 65535] Nov 24 15:49:53 g1fw1 named[26422]: listening on IPv4 interface ix0, 10.0.4.2#53 Nov 24 15:49:53 g1fw1 named[26422]: listening on IPv4 interface ix0, 10.0.4.1#53 Nov 24 15:49:53 g1fw1 named[26422]: listening on IPv4 interface ix1, 92.223.102.252#53 Nov 24 15:49:53 g1fw1 named[26422]: listening on IPv4 interface ix1, 92.223.102.251#53 Nov 24 15:49:53 g1fw1 named[26422]: listening on IPv6 interface lo0, ::1#53 Nov 24 15:49:53 g1fw1 named[26422]: listening on IPv6 interface lo0, fe80::1%5#53 Nov 24 15:49:53 g1fw1 named[26422]: listening on IPv4 interface lo0, 127.0.0.1#53 Nov 24 15:49:53 g1fw1 named[26422]: listening on IPv4 interface gre0, 172.16.0.7#53 Nov 24 15:49:53 g1fw1 named[26422]: generating session key for dynamic DNS Nov 24 15:49:53 g1fw1 named[26422]: sizing zone task pool based on 6 zones Nov 24 15:49:53 g1fw1 named[26422]: none:102: 'max-cache-size 90%' - settin= g to 14553MB (out of 16170MB) Nov 24 15:49:53 g1fw1 named[26422]: set up managed keys zone for view inter= nal, file 'internal.mkeys' Nov 24 15:49:53 g1fw1 named[26422]: none:102: 'max-cache-size 90%' - settin= g to 14553MB (out of 16170MB) Nov 24 15:49:53 g1fw1 named[26422]: set up managed keys zone for view exter= nal, file 'external.mkeys' Nov 24 15:49:53 g1fw1 named[26422]: none:102: 'max-cache-size 90%' - settin= g to 14553MB (out of 16170MB) Nov 24 15:49:53 g1fw1 named[26422]: command channel listening on 127.0.0.1#= 953 Nov 24 15:49:53 g1fw1 named[26422]: the working directory is not writable Nov 24 15:49:53 g1fw1 named[26422]: loading configuration: permission denied Nov 24 15:49:53 g1fw1 named[26422]: exiting (due to fatal error) =3D=3D=3DCut=3D=3D=3D Yup, I know what it looks like. It looks like it cannot load the named.conf= or zones. But the fact is he can - ktrace shows it loads the named.conf (furthermore, when it cannot load named.conf it gives explicit error about inability to load named.conf), but not the zones. Sources search doesn't gi= ve the reason, I even failed to locate the source file saying "loading configuration:" (only "loading configuration from '%s" and "reloading configuration"), and I've tested named.conf opening under bind user tempora= rily given a login shell - it's clear that he can read this file. Furthermore running bind912 without the chroot and under the root user also doesn't resolve this, thus so far I failed to determine the reason, so I'm sending this PR. Also a minor bug: dns/bind911 also requires /var/named directory, and it's = not created automatically inside a chroot. In this case it complains about:=20 error writing NTA file for view %VIEVNAME: permission denied Btw I've tested whether this is the reason of a fatal error - nope, creating /var/named inside a chroot doesn't resolve this. Workaround: use dns/bind911 or dns/bin910 or dns/bind99, - all of them work just fine on the same set of configuration files. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223842-13>