From owner-freebsd-questions@FreeBSD.ORG Thu Sep 23 17:13:40 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67EFB16A4CE for ; Thu, 23 Sep 2004 17:13:40 +0000 (GMT) Received: from ccs.completecomputing.com (completecomputing.com [207.90.211.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1164F43D1F for ; Thu, 23 Sep 2004 17:13:40 +0000 (GMT) (envelope-from kallender@completecomputing.com) Received: from ccs.completecomputing.com (ccs.completecomputing.com [127.0.0.1])i8NHCFpd002478 for ; Thu, 23 Sep 2004 12:12:15 -0500 Received: (from webmstr@localhost) by ccs.completecomputing.com (8.12.8/8.12.8/Submit) id i8NHCFjU002473 for freebsd-questions@freebsd.org; Thu, 23 Sep 2004 12:12:15 -0500 X-Authentication-Warning: ccs.completecomputing.com: webmstr set sender to kallender@completecomputing.com using -f Received: from ns1.prismequine.com (ns1.prismequine.com [199.120.78.141]) by mail.completecomputing.com (IMP) with HTTP for ; Thu, 23 Sep 2004 12:12:15 -0500 Message-ID: <1095959535.415303ef674c3@mail.completecomputing.com> Date: Thu, 23 Sep 2004 12:12:15 -0500 From: kallender@completecomputing.com To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 199.120.78.141 Subject: Bind 9.3.0 startup failure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 17:13:40 -0000 Hello again. I'm still stumped. I thought that perhaps something had gone wrong during the install initially. I performed a clean install without named or Linux compatibility being enabled. I then used the references on this page: http://ezine.daemonnews.org/200303/bind9.html to build a clean copy of Bind9.3.0 over the top of the base distribution that ships with FBSD 5.2.1. It will start manually from the CLI with either: named /usr/sbin/named and properly read the zones and configuration files, inclusive of rndc-key. However, I still can't control named via /etc/rc.d/named and on startup the system spits out several errors with regards to named and being unable to open interfaces. It's as if networking isn't up yet, so named can't start. But if networking were not running, I wouldn't see errors about addresses and interfaces already being in use. I did make one change to /etc/rc.conf, adding this line at the end: /usr/sbin/named The messages log looks like this: Sep 23 12:00:00 bsd named[472]: starting BIND 9.3.0 Sep 23 12:00:00 bsd named[472]: could not listen on UDP socket: permission denied Sep 23 12:00:00 bsd named[472]: creating IPv4 interface de0 failed; interface ignored Sep 23 12:00:00 bsd named[472]: could not listen on UDP socket: permission denied Sep 23 12:00:00 bsd named[472]: creating IPv4 interface lo0 failed; interface ignored Sep 23 12:00:00 bsd named[472]: not listening on any interfaces Sep 23 12:00:00 bsd named[472]: /etc/namedb/named.conf:28: couldn't add command channel 127.0.0.1#953: permission denied Sep 23 12:00:00 bsd named[472]: couldn't open pid file '/var/run/named/named.pid': File exists Sep 23 12:00:00 bsd named[472]: exiting (due to early fatal error) Sep 23 12:02:53 bsd login: ROOT LOGIN (root) ON ttyv0 Sep 23 12:03:28 bsd named[184]: stopping command channel on 127.0.0.1#953 Sep 23 12:03:28 bsd named[429]: exiting Sep 23 12:03:28 bsd named[184]: exiting Sep 23 12:03:34 bsd named[487]: starting BIND 9.3.0 Sep 23 12:03:34 bsd named[487]: command channel listening on 127.0.0.1#953 Sep 23 12:03:47 bsd login: ROOT LOGIN (root) ON ttyv0 Sep 23 12:04:17 bsd named[499]: starting BIND 9.3.0 Sep 23 12:04:17 bsd named[499]: could not listen on UDP socket: address in use Sep 23 12:04:17 bsd named[499]: creating IPv4 interface de0 failed; interface ignored Sep 23 12:04:17 bsd named[499]: could not listen on UDP socket: address in use Sep 23 12:04:17 bsd named[499]: creating IPv4 interface lo0 failed; interface ignored Sep 23 12:04:17 bsd named[499]: not listening on any interfaces Sep 23 12:04:17 bsd named[499]: /etc/namedb/named.conf:28: couldn't add command channel 127.0.0.1#953: address in use Sep 23 12:04:17 bsd named[499]: could not listen on UDP socket: address in use Sep 23 12:04:17 bsd named[499]: creating IPv4 interface de0 failed; interface ignored Sep 23 12:04:17 bsd named[499]: could not listen on UDP socket: address in use Sep 23 12:04:17 bsd named[499]: creating IPv4 interface lo0 failed; interface ignored Note that there is a named.pid file in /var/run/named after a reboot - possibly created by the system on boot? Is the OS trying to start named too early? /etc/defaults/rc.d contains: # # named. It may be possible to run named in a sandbox, man security for # details. # named_rcng="NO" # XXX Temporary. Enable to use new rc # functionality in support of named. See # variables below. named_enable="NO" # Run named, the DNS server (or NO). named_program="/usr/sbin/named" # path to named, if you want a different one. named_flags="-u bind -g bind" # Flags for named named_pidfile="/var/run/named/pid" # Pid file named_chrootdir="" # Chroot directory (or "" not to auto-chroot it) named_chroot_autoupdate="YES" # Automatically install/update chrooted # components of named. See /etc/rc.d/named. named_symlink_enable="YES" # Symlink ${named_pidfile} and /var/run/ndc # to their chrooted counterparts. The /etc/rc.d/named script is unaltered from clean install of the OS. I am _super_ confused here. Can anyone help? Kyle