From owner-freebsd-questions Sun Oct 27 6:49:49 2002 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 C640F37B401 for ; Sun, 27 Oct 2002 06:49:47 -0800 (PST) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15C5343E42 for ; Sun, 27 Oct 2002 06:49:47 -0800 (PST) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198] (may be forged)) by be-well.ilk.org (8.12.6/8.12.5) with ESMTP id g9REnjWJ002028; Sun, 27 Oct 2002 09:49:45 -0500 (EST) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.6/8.12.6/Submit) id g9REnjXO002025; Sun, 27 Oct 2002 09:49:45 -0500 (EST) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f To: Dan Kalowsky Cc: freebsd-questions@FreeBSD.ORG Subject: Re: machine disappearance after upgrade 4.7 References: <5EC67568-E81D-11D6-ADD5-000393121960@cs.jhu.edu> From: Lowell Gilbert Date: 27 Oct 2002 09:49:45 -0500 In-Reply-To: <5EC67568-E81D-11D6-ADD5-000393121960@cs.jhu.edu> Message-ID: <444rb89bsm.fsf@be-well.ilk.org> Lines: 32 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dan Kalowsky writes: > Hopefully someone can give me a pointer or two here. A normally > extremely stable machine running FreeBSD has become rather unstable > after upgrading to the 4.7 release. > > By unstable I mean disappearing off the network suddenly, and having > console non-responsive to anything but a nice ctl-alt-del reboot. The > log files only show one thing that may be of issue: > > > Oct 25 01:05:48 x-wing /kernel: arplookup 207.8.132.194 failed: host > > is not on local network > > Oct 25 01:36:27 x-wing /kernel: arplookup 207.8.132.194 failed: host > > is not on local network So is 207.8.132.194 on the local subnet or not? > Right before the machine disappears, these messages start repeating > rather rapidly to the tune of one about ever 5 seconds. This behavior > was not seen in any of the earlier FreeBSD releases. The said IP > address is the IP for the nameserver of the cluster group, which is > responding just fine to requests. A quick search of the archives > reveals nothing thats of any help to me so... > > Have I somehow misconfigured my upgrade, and if so any suggestions on > what to fix or where to begin looking? Or have I stumbled upon a > legit bug? Those messages generally indicate a networking configuration problem, but locking up a machine with such a problem would be hard (not impossible, though, because that part of the IP stack is inside the kernel). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message