On Mon, 19 Oct 2009 16:30:47 -0700
John Oliver <joliver@stripped> wrote:
> I have a problem with MySQL passwords... I set them, write them
> down... and they stop working. I have to go in and manually reset
> Right now, I have a database that, even after resetting the password,
> I still cannot access it.
> /var/log/mysql.log doesn't give me any useful information. How can I
> get MySQL to tell me what it's unhappy about, or get more information
> from the client other than it just didn't work?
> I also have problems with MySQL resolving names, or not resolving
> names, or ??? I usually add 'user'@'ip.address' and
> 'user'@'host.name' But, more and more often, I've had to put
> skip-name-resolve in my.cnf, but with my current problem, I'm still
> seeing that 'user'@'host-name' is being rejected, even when I use -h
> ip.address on the command line
> And when I add those two users, and go to reset passwords, it doesn't
> want to let me specify 'user'@'ip.address' or 'user'@'host.name' but
> just 'user' I *think* it's resetting the password for both... the
> hashes are always the same. But I just don't know.
> What am I missing?
Are you accessing MySQL from the same host? If so, you don't need the
-h option unless that's the only entry in your grant table under that
username (i.e. 'user'@'ip-address').
Can you give us an example of how you're setting the username and their
permissions? Here's a typical example that gives access to an entire
database to a single user provided they're accessing it on the same
GRANT ALL on <database-name>.* to 'user'@'localhost' identified by
The username, password AND hostname have to match up for
authentication to be successful: 'user'@'localhost' may be different
than 'user'@'ip-address' even if they're intended to be the same person.
Office: 250.412.9651 || Mobile: 250.886.4577
Skype: websage.ca || GTalk IM: gmarus
GnuPG-ID: 0x4309323E, http://pgp.mit.edu