From owner-freebsd-questions@FreeBSD.ORG Mon Oct 6 17:46:56 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A15D9106568A; Mon, 6 Oct 2008 17:46:56 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id 3D0838FC1B; Mon, 6 Oct 2008 17:46:55 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id m96Hj2kk071252; Mon, 6 Oct 2008 13:45:02 -0400 (EDT) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id m96Hj26C071251; Mon, 6 Oct 2008 13:45:02 -0400 (EDT) (envelope-from jerrymc) Date: Mon, 6 Oct 2008 13:45:02 -0400 From: Jerry McAllister To: Jeremy Chadwick Message-ID: <20081006174502.GB71024@gizmo.acns.msu.edu> References: <1223273047.23248.25.camel@phoenix.blechhirn.net> <20081006171809.GA26368@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081006171809.GA26368@icarus.home.lan> User-Agent: Mutt/1.4.2.2i Cc: freebsd-questions@freebsd.org Subject: Re: analyzing freebsd core dumps X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2008 17:46:56 -0000 On Mon, Oct 06, 2008 at 10:18:09AM -0700, Jeremy Chadwick wrote: > On Mon, Oct 06, 2008 at 08:04:07AM +0200, Mister Olli wrote: > > hi list... > > > > I have a freebsd maschine running for more 6 months without any > > problems. > > the machine's only service is to be an openvpn gateway for a hand of > > users. > > > > 2 weeks ago the first problems started. the openvpn exited with signal > > 11 and 4 and core dumps were written. > > > > the same happend yesterday with the postfix/cleanup process, and the > > suddenly the machine rebooted without any further log messages. > > > > what is the best way to troubleshoot the cause of this problem? > > Signal 11 happening "out of no where" on machines which have been > running fine, most of the time, is a sign of hardware failure (usually > RAM, but sometimes motherboard or PSU). The fact you got a reboot is > also further evidence of this. > > http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11 > > I would recommend taking the machine offline and running something like > memtest86+ on it for 6-7 hours. Any errors seen are a pretty good sign > that you should replace the memory or the motherboard. You can > download an ISO or floppy disk images here: > > http://www.memtest.org/ > > Bottom line is that this is probably a hardware issue. Could also be a contacts if it is not the actual memory or board. A marginal contact where something is plugged in can over time build up deposits that make it fail. Of course, this is still a hardware problem, but can often be cured by reseating everything. If it is bad enough, it could also be exacerbated by reseating everything. ////jerry > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"