From owner-freebsd-current@FreeBSD.ORG Wed Mar 31 19:10:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 413FF16A4CE for ; Wed, 31 Mar 2004 19:10:37 -0800 (PST) Received: from web9602.mail.yahoo.com (web9602.mail.yahoo.com [216.136.129.181]) by mx1.FreeBSD.org (Postfix) with SMTP id F0F6243D45 for ; Wed, 31 Mar 2004 19:10:36 -0800 (PST) (envelope-from chancedj@yahoo.com) Message-ID: <20040401031036.77156.qmail@web9602.mail.yahoo.com> Received: from [24.170.136.111] by web9602.mail.yahoo.com via HTTP; Wed, 31 Mar 2004 19:10:36 PST Date: Wed, 31 Mar 2004 19:10:36 -0800 (PST) From: Daryl Chance To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: FBSD 5.2.1-p4 and mysqld problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: chancedj@yahoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Apr 2004 03:10:37 -0000 we are having a couple problems with mysql on FreeBSD 5.2.1 the dmesg is located here: http://sql.tribalwar.com/dmesg.today It's just a generic config with IPv6 removed and the ix86 stuff removed (just i686 left). one of the problems we are having is that there is 1 specific table in the db (and it's only 1 database too that this happens) is getting corrupted and forcing us to have to repair it. This one could just be a problem with mysql and it's just accelerated w/ using it on FreeBSD 5.x. We haven't nailed any specific time that this happens nor any specific insert/select/update that could cause it. Is there any way to verify (through FreeBSD userland commands or ports that you may know of) that this isn't a drive problem? Is there something I can run on FBSD that will help me to track this problem down (perhaps some sort of GEOM logging)? the other problem we are having is that mysql will lock up. 1 of the mysqld processes freezes (uses up all the cpu) and it won't allow anymore queries against it until we shutdown. Is there any way for me to debug this and find out where it is hanging? Is there a working alternative to truss? Or should I just compile option PROCFS in and use it next time it locks? I realize that we shouldn't be running this as a production server, but other then these issues with mysql, the server and it's webserver counterpart are rock solid. Should I upgrade to 5-CURRENT and run it for a couple days before trying to assuming these are new issues :)? also, we are running against linuxthreads but also get this problem with the default threading in FBSD (libc_r?) for 5.2.1 Daryl __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/