From owner-freebsd-fs@FreeBSD.ORG Thu Feb 2 11:24:46 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEA7D106566B for ; Thu, 2 Feb 2012 11:24:46 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by mx1.freebsd.org (Postfix) with ESMTP id 9AC668FC17 for ; Thu, 2 Feb 2012 11:24:46 +0000 (UTC) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta14.westchester.pa.mail.comcast.net with comcast id UzJU1i0010vyq2s5EzQmGt; Thu, 02 Feb 2012 11:24:46 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta05.westchester.pa.mail.comcast.net with comcast id UzQm1i0011t3BNj3RzQm4C; Thu, 02 Feb 2012 11:24:46 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7ED80102C1E; Thu, 2 Feb 2012 03:24:44 -0800 (PST) Date: Thu, 2 Feb 2012 03:24:44 -0800 From: Jeremy Chadwick To: Shelm Message-ID: <20120202112444.GA16854@icarus.home.lan> References: <1328001527003-5444043.post@n5.nabble.com> <20120131095525.GA67112@icarus.home.lan> <1328004542281-5444145.post@n5.nabble.com> <1328179206463-5450286.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1328179206463-5450286.post@n5.nabble.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: Hast Unable to listen on address X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2012 11:24:46 -0000 On Thu, Feb 02, 2012 at 02:40:06AM -0800, Shelm wrote: > why the same value on two servers kern.hostuuid Please read the code in /etc/rc.d/hostid to understand. You will also need to look at /etc/defaults/rc.conf to know what $hostid_file is. kern.hostuuid and kern.hostid are generated on-the-fly when the system does not have /etc/hostid. You can reset this simply by removing the file and rebooting, or by running "/etc/rc.d/hostid reset". I do not believe a reboot will be needed after doing the latter, but you will almost certainly have to restart daemons. If you read the above script it should (mostly) make sense. Likely root cause: When you made these two systems, you probably mistakingly copied /etc/hostid from one to the other (or you copied /etc from one to the other). Administrator error. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |