Thanks for the tips, all. Looks like we've got it restored
via --skip-grant-tables and restoring some missing user rows
(which caused me not to be able to see DBs in 'show databases').
I was also confused about being able to load an empty string ''
into the non-null mysql.user.password field.
Log in as root and run:
set password = '';
OR
update mysql.user set Password='' where User='root';
this is TOTALLY INSECURE but if that's what you want, then it should do the
trick.
Regards,
Darren Cassar
www.mysqlpreacher.com
www.securich.com
On Wed, Aug 26, 2009 at 2:33 AM, Joe wrote:
> I'
Is there a specific reason you cannot do it with --skip-grant-table?
You should theoretically also be able to overwrite the files user.*
(there should be 3) in /var/lib/mysql/mysql/ (replace everything up to
and including teh first mysql in that path with your mysql data dir)
when the server is st
I'm trying to get back to an earlier state where we started
mysqld withOUT --skip-grant-tables but the root user had no
password. Yes, insecure, but we're in restoration mode here.
How do I reset/revert the root password to no password without
running with --skip-grant-tables?
Thanks in advan
