From owner-freebsd-questions Mon Nov 4 11:59:56 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 430FD37B401 for ; Mon, 4 Nov 2002 11:59:53 -0800 (PST) Received: from blaze.cs.jhu.edu (blaze.cs.jhu.edu [128.220.13.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AD0343E6E for ; Mon, 4 Nov 2002 11:59:52 -0800 (PST) (envelope-from kalowsky@cs.jhu.edu) Received: from masters1.cs.jhu.edu (masters1.cs.jhu.edu [128.220.223.217]) by blaze.cs.jhu.edu (8.12.3/8.12.3) with ESMTP id gA4K27x6016093; Mon, 4 Nov 2002 15:02:07 -0500 (EST) Received: from localhost (kalowsky@localhost) by masters1.cs.jhu.edu (8.11.1/8.11.1) with ESMTP id gA4JxRj04892; Mon, 4 Nov 2002 14:59:27 -0500 (EST) Date: Mon, 4 Nov 2002 14:59:27 -0500 (EST) From: Daniel Kalowsky To: Alex Cc: Subject: Re: machine disappearance after upgrade 4.7 In-Reply-To: <7529585852.20021104204455@dds.nl> Message-ID: 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 Odd that the SMTP server couldn't respond, but thank you Alex. I will try forwarding this to hackers now. Thanks. ~ Your INBOX quakes with fear! kalowsky@cs.jhu.edu For it has a message of mine! On Mon, 4 Nov 2002, Alex wrote: > Hello/Beste Dan, > > I got a message from the smtp server that this mail could not be > send..... > > Friday, October 25, 2002, 2:26:29 PM, you wrote: > > > Hi everyone, > > > 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 > > >> bash-2.05a$ ifconfig -a > >> de0: flags=8843 mtu 1500 > >> inet 207.106.130.84 netmask 0xfffffff0 broadcast 207.106.130.95 > > What the relation between this (207.106.130.84) computer and > 207.8.132.194? > > > 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? > > Perhaps its time to repost this message at the hackers maillist. If it > is a bug, they be better at helping you. Right now i'm guessing that it > is one. > > > By unstable I mean disappearing off the network suddenly, and having > > console non-responsive to anything but a nice ctl-alt-del reboot. > > This especially is strange. > > > If more information is needed, it can be provided. Any and all help > > would be appreciated. > > Hello/Beste Dan, > > Monday, October 28, 2002, 2:09:25 PM, you wrote: > > > 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 > > What kind of server is 207.8.132.194 and what is its relation to this > (207.106.130.84) machine? > > > Output from ifconfig for your review: > > Sorry, this didn't seem relevant after all. Is there a program running > that interfere with the sending of the arp packages? > > Perhaps its time to repost this message at the hackers maillist. If it > is a bug, they be better at helping you. Right now i'm guessing that it > is one. > > > By unstable I mean disappearing off the network suddenly, and having > > console non-responsive to anything but a nice ctl-alt-del reboot. > > This especially is strange. (Way would the machine lockup when not > finding the ip of another computer? > > -- > Best regards/Met vriendelijke groet, > Alex > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message