From owner-freebsd-ports@FreeBSD.ORG Tue Oct 16 22:31:26 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 71E9716A417 for ; Tue, 16 Oct 2007 22:31:26 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from mail.sailorfej.net (mail.sailorfej.net [66.93.72.123]) by mx1.freebsd.org (Postfix) with ESMTP id 50BB013C44B for ; Tue, 16 Oct 2007 22:31:26 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from [127.0.0.1] (c-67-160-132-255.hsd1.or.comcast.net [67.160.132.255]) (authenticated bits=0) by mail.sailorfej.net (8.13.8/8.13.8) with ESMTP id l9GMVINc040252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Oct 2007 15:31:20 -0700 (PDT) (envelope-from jeff@sailorfej.net) Message-ID: <47153BAD.6040700@sailorfej.net> Date: Tue, 16 Oct 2007 15:31:09 -0700 From: Jeffrey Williams User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Mike Andrews References: <47120E73.1080403@sailorfej.net> <20071015125237.A21749@bit0.com> In-Reply-To: <20071015125237.A21749@bit0.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.6 required=6.0 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.sailorfej.net 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: Tue, 16 Oct 2007 22:31:26 -0000 Mike Andrews wrote: > 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. > Hi Mike, Thanks very much, that did the trick. Jeff