From owner-freebsd-stable@FreeBSD.ORG Tue Jan 4 01:48:45 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F203716A4CE for ; Tue, 4 Jan 2005 01:48:44 +0000 (GMT) Received: from smtpq2.home.nl (smtpq2.home.nl [213.51.128.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DA0C43D2D for ; Tue, 4 Jan 2005 01:48:44 +0000 (GMT) (envelope-from edwin@woudt.nl) Received: from [213.51.128.134] (port=38033 helo=smtp3.home.nl) by smtpq2.home.nl with esmtp (Exim 4.30) id 1CldoQ-0007Yn-TI; Tue, 04 Jan 2005 02:48:42 +0100 Received: from cc718542-a.ensch1.ov.home.nl ([84.31.118.254]:2297 helo=[10.24.64.4]) by smtp3.home.nl with esmtp (Exim 4.30) id 1CldoQ-0004Fc-4x; Tue, 04 Jan 2005 02:48:42 +0100 Date: Tue, 04 Jan 2005 02:48:40 +0100 From: Edwin Woudt To: Billy Newsom , freebsd-stable@freebsd.org Message-ID: <8E3B05F1BDF8BE46E9232915@[10.24.64.4]> In-Reply-To: <41D759A2.7020105@leadhill.net> References: <41D759A2.7020105@leadhill.net> X-Mailer: Mulberry/4.0.0a4 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-AtHome-MailScanner-Information: Neem contact op met support@home.nl voor meer informatie X-AtHome-MailScanner: Found to be clean Subject: Re: mysql crashes on 5.3-stable, SMP, linuxthreads X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 01:48:45 -0000 --On 1-1-2005 20:17 -0600 Billy Newsom wrote: > > I have just built a FreeBSD 5.3 box with SMP enabled on a dual processor > machine. I kept having a lot of crashes at some point in the install, > and I believe I now have the cuprit: mysql-server-4.1.7 is doing it. > Lately, when mysql-server is running under no load, it caused lockups of > the system, with no core dumps. I had a similar issue: within one hour after upgrading mysql from 4.0.20 to 4.0.22 on a 4.10 box, my machine crashed. This happened when I asked for a webpage that querys a mysql database. It had been running stable for two years continuously and now it unexpectedly crashed without any available log entry or core dump. On startup the automatig file system check failed because of some unexpected softupdate errors. This could very well be completely unrelated to your problem as my setup is completely different, and all signs suggest a hardware problem. However as the only thing changed was mysql and the thing triggering it was accessing the database, I have my suspicions. As it is a colocated box and someone had to manually run an fsck I've decided not to try to reproduce it, but to disable mysql (all but one application was using postgresql anyway) and the server has been running stable since then. -- Edwin