From owner-freebsd-security Sun Feb 3 7:37:12 2002 Delivered-To: freebsd-security@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9841937B405 for ; Sun, 3 Feb 2002 07:37:09 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g13Fa4D28870; Sun, 3 Feb 2002 10:36:04 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 3 Feb 2002 10:36:03 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: suporte Cc: freebsd-security@freebsd.org Subject: Re: crashs on 4.5RC In-Reply-To: <008c01c1ab66$b0692820$616156d1@DSGX1WZFFGDP93> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 1 Feb 2002, suporte wrote: > i updated my 4.4 to an 4.5RC the first time that i compiled .. it was > crashing almost everysingle hour .. i booted up again on the old > 4.5PRE-RELEASE .. and recompile the kernel with the new updates from > cvsup .. k so was finally stable again .. now i can't get an uptime more > than 4 days .. so i tryed again yesterday made another update using the > cvsup there was a bunch of things new there .. i compile again .. how > many time do u guys think this thing gonna keep reseting me and a bunch > of friends we're having the same problems .. we really use the machine > is not just a simple for mails .. is for eggdrops/apache/ircds/bncs .. > stuffs like that .. can anybody give me a light ? You need to be more specific. What do you mean by "crash" -- do you get a system panic, a system hang, a reboot without a message? Is any output generated along the way? One common pitfall identified in the release notes was a change in default sizing of socket buffers, which requires some busy sites to increase nmbclusters (either by recompiling with different kernel configuration settings, or simply updating loader.conf to use a larger hard-coded value). Potentially, you could be running into that. If you're getting a panic, this can be debugged using the kernel debugging recommendations in the FreeBSD handbook. You'll either want to enable dumping of system core, or include options DDB in the kernel so you can debug live. You'll also want to build the kernel using debugging symbols so that the results are useful. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message