From owner-freebsd-questions Wed Aug 23 16:52:49 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id BD3BF37B61F; Wed, 23 Aug 2000 16:52:40 -0700 (PDT) Received: from sharky (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id SAA62397; Wed, 23 Aug 2000 18:42:32 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200008240042.SAA62397@mail.fpsn.net> From: "Simon" To: "Chris Byrnes" Cc: "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Date: Wed, 23 Aug 2000 19:56:17 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: WTF Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From your description, I have to put a high bet on a faulty hardware you added or issues it has with existing hardware. If I were you, I would change the hardware exactly to what it was before and see if stays up for a week - that would eliminate the OS (which i doubt anyway). Then replace RAM and see if it crashes within another week. Then finally add the CPU. Or do this quick by stress testing the system. Of course if this a production box, you're pretty much stuck ;-( -Simon On Wed, 23 Aug 2000 18:46:27 -0500 (CDT), Chris Byrnes wrote: >SWAP usage has been high lately. It happened RIGHT after I upgraded the >system to a new CPU, board, and RAM, and to 3.50STABLE. I >thought maybe there was a OS issue with my SUP or something (I >was hoping). That's when it started >happening. God, I dont have TIME to weed thru trying new boards and new >CPUs. > >I wish there was a quick fix. > >------------------------------------------------- >Chris Byrnes, Owner NSI NIC HANDLE CB5820 >Jeah Communications http://www.jeah.net >------------------------------------------------- > >On Wed, 23 Aug 2000, Simon wrote: > >> it can be anything! and i mean anything! bad RAM, bad harddrive, bad CPU, etc... and i know EXACTLY how it feels >> when shit like this happens. Unfortunately, it's not always easy to determine the cause. Are you using %100 certified >> RAM for your motherboard? just because it's new doesn't mean jack. I had servers go wild with brand new out of the box >> RAM and harddrives. You said it only started recently, try to remember after what? some change you made? more load? >> do you have logs enabled? anything in there? do you monitor this machine? what's the load average like? swap usage, >> etc... what is it doing most of the time? >> >> -Simon >> >> On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: >> >> >I'm running 3.5-STABLE. >> > >> >Recently, my server has started rebooting, at random times, usually >> >actually quite religiously about every 2 days. >> > >> >I thought it might be a RAM problem. Replaced with brand new RAM. >> >Same problem. >> > >> >Any ideas, at all? Pllllllllllllease. >> > >> >Chris >> > >> > >> >To Unsubscribe: send mail to majordomo@FreeBSD.org >> >with "unsubscribe freebsd-stable" in the body of the message >> > >> >> >> >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message