From owner-freebsd-current@FreeBSD.ORG Thu Feb 12 08:22:14 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8DEDE1F8 for ; Thu, 12 Feb 2015 08:22:14 +0000 (UTC) Received: from odin.blazingdot.com (odin.blazingdot.com [204.109.60.170]) by mx1.freebsd.org (Postfix) with ESMTP id 73294C7F for ; Thu, 12 Feb 2015 08:22:14 +0000 (UTC) Received: by odin.blazingdot.com (Postfix, from userid 1001) id 2DA21131E86; Thu, 12 Feb 2015 03:22:14 -0500 (EST) Date: Thu, 12 Feb 2015 03:22:14 -0500 From: Marcus Reid To: Poul-Henning Kamp Subject: Re: unbound crashes on bootup Message-ID: <20150212082214.GB12716@blazingdot.com> References: <1264.1423227963@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1264.1423227963@critter.freebsd.dk> X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.23 (2014-03-12) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 08:22:14 -0000 On Fri, Feb 06, 2015 at 01:06:03PM +0000, Poul-Henning Kamp wrote: > I just updated my -current to r278283, and unbound (still) croaks > during bootup: > > Feb 6 13:00:54 critter dhclient: New Broadcast Address (wlan0): 192.168.60.255 > Feb 6 13:00:54 critter dhclient: New Routers (wlan0): 192.168.60.1 > Feb 6 13:00:54 critter kernel: pid 515 (unbound), uid 59: exited on signal 11 > Feb 6 13:00:58 critter ntpd_initres[769]: host name not found: pool.ntp.org > > No core file... You can get unbound to leave a core in /var/unbound by setting kern.sugid_coredump=1 . I found that sometimes (like on a hup and sometimes when interfaces go up/down) unbound would crash, which I tracked down to getpwnam() not having a /etc/pwd.db to use in the chroot. The latest version of unbound appears to have made a lot of changes in that particular place, getpwnam() doesn't even appear in that file anymore. I submitted a bug report for the crash that I found, I don't know if it's related to yours. Marcus