> > Did I just FUBAR my grant tables?
>
> Dunno, but you can always fix them by starting mysqld with --skip_grants.
> Review your grants, fix your passwords, then FLUSH PRIVILEGES.
Yeah, I tried this already, but tried it again now just for ha-ha's.
1. kill mysqld and safe_mysqld (is there a cleaner way to do this than
<kill> since I can't use <mysqladmin shutdown>?)
2. start mysqld (or safe_mysqld) with the -Sg option
3. start mysql, update the password for root in the user table, flush
priveleges
4. exit mysql, kill and restart mysqld
5. try to start mysql (using -p for root)
6. get no love (Found invalid password for user: 'root@localhost';
Ignoring user)
Oddity 1: when I start mysqld from the command line (disabled init.d
startup for now), I lose the cursor... Is this normal, since safe_mysqld
runs as root? Does the system effectively just grab that login and keep
me from using it now that it's running safe_mysqld? (I'm ssh'ing to the
machine and accessing SQL using the root account on the machine)
Oddity 2: mysql was installed on this machine when it used to have a
different dns name (though it's hostname has remained the same). There
are two entries in the user table for root - one for root@localhost and
one for root@stripped (where oldDomain.com is the old
network it used to be on).
Since there are two entries in the user table for root, and one of them
lists the hostname with the old domain, could that be fudging up the
works? Again, I'm not accessing SQL remotely - rather, I'm ssh'ing to
the machine and issuing mysqladmin commands, starting mysqld, and
running mysql on the machine from the system's root login.
Sincerely,
-Confused
