From owner-freebsd-ports@FreeBSD.ORG Mon Oct 15 16:54:24 2007 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 165AA16A4E8 for ; Mon, 15 Oct 2007 16:54:19 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from mindcrime.bit0.com (bit0.com [207.246.88.211]) by mx1.freebsd.org (Postfix) with ESMTP id BCCC613C459 for ; Mon, 15 Oct 2007 16:54:18 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from localhost (localhost.bit0.com [127.0.0.1]) by mindcrime.bit0.com (Postfix) with ESMTP id 6E32D1E3340; Mon, 15 Oct 2007 12:54:17 -0400 (EDT) X-Virus-Scanned: amavisd-new at bit0.com Received: from mindcrime.bit0.com ([127.0.0.1]) by localhost (mindcrime.bit0.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7knWw852iKa2; Mon, 15 Oct 2007 12:54:14 -0400 (EDT) Received: from localhost (localhost.bit0.com [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mindcrime.bit0.com (Postfix) with ESMTP; Mon, 15 Oct 2007 12:54:14 -0400 (EDT) Date: Mon, 15 Oct 2007 12:54:14 -0400 (EDT) From: Mike Andrews To: Jeffrey Williams In-Reply-To: <47120E73.1080403@sailorfej.net> Message-ID: <20071015125237.A21749@bit0.com> References: <47120E73.1080403@sailorfej.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: ports@freebsd.org Subject: Re: mysql51-server won't start after upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2007 16:54:24 -0000 On Sun, 14 Oct 2007, Jeffrey Williams wrote: > I just upgraded mysql51-server with cvsup and portupgrade. > > Now it won't start, and the error I am getting is: > [ERROR] /usr/local/libexec/mysqld: unknown variable > 'innodb_log_arch_dir=/var/db/mysql/' > > I have been scanning the release notes, but I haven't found anything yet, > that indicates that this variable has been deprecated, and it still appears > in the example my.cnf files. I ran into this last week, too. I had to poke around in the InnoDB source for this (as far as I can tell this isn't documented anywhere), but apparently innodb_log_group_home_dir has superceded innodb_log_arch_dir since 4.0, so just change the latter to the former and everything works.