From owner-freebsd-questions@FreeBSD.ORG Mon Jan 31 18:25:45 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 663E116A4CE for ; Mon, 31 Jan 2005 18:25:45 +0000 (GMT) Received: from harlie.americanlowlife.com (bastion.americanlowlife.com [216.250.95.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 272AB43D2F for ; Mon, 31 Jan 2005 18:25:45 +0000 (GMT) (envelope-from ejs@americanlowlife.com) Received: from [216.250.95.226] (bastion [216.250.95.226]) j0VIPhW1065387 for ; Mon, 31 Jan 2005 10:25:44 -0800 (PST) (envelope-from ejs@americanlowlife.com) Message-ID: <41FE7827.9060201@americanlowlife.com> Date: Mon, 31 Jan 2005 10:25:43 -0800 From: Eric S User-Agent: Mozilla Thunderbird 1.0 (X11/20041209) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20050130120119.09BBE16A4EB@hub.freebsd.org> In-Reply-To: <20050130120119.09BBE16A4EB@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.80/664/Thu Jan 13 07:13:05 2005 clamav-milter version 0.80j on harlie.americanlowlife.com X-Virus-Status: Clean Subject: Re: MySQL update from 4.1 to 4.7 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2005 18:25:45 -0000 >From: Phillip Hocking >Subject: MySQL update from 4.1 to 4.7 >To: questions@freebsd.org > >Now it will not allow me to login to the database with any of the >usernames that I remember here is the error in the log 2:58:29 [Warning] >Found 4.1 style password for user 'root@localhost'. Ignoring user. You >should change password for this user. How do I flush the tables to >resolve this issue and change all the passwords around? Any help would >be much appreciated. > > I don't know the answer, but I know where to find it, since I encountered that same problem. When mysql starts up, it logs a message in the log file for that server to the effect that the password table needs to be updated, and includes the command to do just this.