Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I've created a database and a user, and allowed access via the following:

create user 'someuser'@'%' identified by 'password';
grant all privileges on somedb.* to 'someuser' with grant option;

however, when I try to connect to MySQL I get the following error:

$ mysql -u someuser -p
> Enter Password:
> ERROR 1045 (28000): Access denied for user 'someuser'@'localhost' (using password: YES)

If "%" is the wildcard, then wouldn't it also enable localhost? However, if I do not specify that I want to use a password, then I can connect just fine to the database, which makes no sense because I'm specifying a password when I created the user.

share|improve this question

5 Answers 5

I'm pretty sure you need the following:

grant all privileges on somedb.* to 'someuser'@'%' with grant option;

Your GRANT statement lacks a hostname declaration.

share|improve this answer
    
A location should be specified: GRANT ALL ON somedb.* TO 'someuser'@'10.1.10.1'; –  nojak Nov 21 '12 at 20:17

Try connecting with mysql -u someuser -p -h 127.0.0.1.

If you can connect without a password, either you have saved credentials in a .my.cnf or you have created an account that allows access without a password.


This comment from the mysql docs may also be related.

http://dev.mysql.com/doc/refman/5.1/en/access-denied.html

If you cannot figure out why you get Access denied, remove from the user table all entries that have Host values containing wildcards (entries that contain '%' or '_' characters). A very common error is to insert a new entry with Host='%' and User='some_user', thinking that this allows you to specify localhost to connect from the same machine. The reason that this does not work is that the default privileges include an entry with Host='localhost' and User=''. Because that entry has a Host value 'localhost' that is more specific than '%', it is used in preference to the new entry when connecting from localhost! The correct procedure is to insert a second entry with Host='localhost' and User='some_user', or to delete the entry with Host='localhost' and User=''.

share|improve this answer
    
+1 including host definition & ~/.my.cnf reference –  Andy Mar 15 '10 at 23:20

My understanding, and I'm prepared to be corrected on this, is that MySQL treats localhost separately to %. i.e. localhost is not included in the wildcard.

share|improve this answer
    
The examples provided in dev.mysql.com/doc/refman/5.1/en/connection-access.html lead me to believe this may not be accurate. Do you have references otherwise? –  Warner Mar 15 '10 at 13:24
    
My understanding of this matter is based on others reporting the same issue, both in print and verbally, and resolving it by creating 2 users, using the "%" and "localhost". I can't recall ever actually seeing it officially documented though. –  John Gardeniers Mar 15 '10 at 21:37
    
This seems to be correct on Ubuntu 12.04 LTS at least –  Dex May 31 '13 at 2:09

Have you run flush privileges; after creating the user? If you don't, changes to users/permissions won't take until after the server is restarted.

Then, check you don't have a '%'@'localhost' entry.

share|improve this answer
2  
using 'create user' and 'grant' automatically flushes privileges. You should only need to flush privileges if you are directly manipulating the mysql database. –  Zoredache Mar 15 '10 at 5:59

If you are unable to connect to mysql using someuser@'%' where '%' is the wildcard for the hostname, then make sure you don't have ''@localhost entry in your user table. Confirm using the following SQL statement:

    mysql> SELECT * FROM user WHERE user='' AND host='localhost';

If ''@localhost is existing, then remove it by issuing the following SQL statement:

    mysql> DELETE FROM user WHERE user='' AND host='localhost';

then lastly

    FLUSH PRIVILEGES;

Now someuser@'%' will connect to the database.

share|improve this answer
    
Granting 'username'@'localhost' privileges will not cause grants on the same user from a different location to not work. –  nojak Nov 21 '12 at 20:11

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.