From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 04:03:48 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE98216A4CE; Tue, 26 Apr 2005 04:03:48 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C11E443D39; Tue, 26 Apr 2005 04:03:48 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id B469372DE5; Mon, 25 Apr 2005 21:03:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id B25ED72DE4; Mon, 25 Apr 2005 21:03:48 -0700 (PDT) Date: Mon, 25 Apr 2005 21:03:48 -0700 (PDT) From: Doug White To: Uzi Klein In-Reply-To: <4263DB52.8020408@bmby.com> Message-ID: <20050425210312.J43358@carver.gumbysoft.com> References: <4263D37E.6070805@bmby.com> <4263D723.6020405@bmby.com> <4263DB52.8020408@bmby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: MySQL signal 11 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2005 04:03:49 -0000 On Mon, 18 Apr 2005, Uzi Klein wrote: > Uzi Klein wrote: > > Uzi Klein wrote: > > > >> > >> Hi > >> > >> I got this message from mysql-error log. > >> Nothing visible on system log, but after it happens, mysql starts > >> acting strange (shoes double fields values as 0 while is still > >> contains the data - visible after restarting mysql) > >> > >> Hardware should be OK, nothing wrong in boot message and its a brand > >> new HP DL380-G4. > >> > >> Any leads or ideas? > >> > > > > eh.. something causing only 1 attachment to appear... sorry... > > > > * mysql-error.log : * > > mysqld got signal 11; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > We will try our best to scrape up some info that will hopefully help > diagnose > the problem, but since we have already crashed, something is definitely > wrong > and this may fail. This is generally indicative of bad memory or nonfunctional cooling. Check the system's environmentals. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org