On 3/16/2012 2:41 PM, Clemens Eisserer wrote:
Hi Shawn,
I understand the logic behind seperating local and remote users,
postgresql does the same thing in its pg_hba.conf file.
However, what I don't understand is the way this turned out to be such
a huge problem (for me), as it worked already wi
Hi Clemens,
my pleasure!
I forgot, you had to use also -P3306, so using both -h and -P which deny
the lookup for users at localhost,
forcing TCP-IP. and so IPs.
this is also good when the socket file is not in the standard location, you
will have the same problem logging in locally,
using -h and
Hi Shawn,
I understand the logic behind seperating local and remote users,
postgresql does the same thing in its pg_hba.conf file.
However, what I don't understand is the way this turned out to be such
a huge problem (for me), as it worked already with MySQL-5.1 a few
years ago. I've worked with o
Hi Claudio,
> you probably have the anonymous user account taking over: ''@'localhost'
> login as root and:
> mysql> drop user ''@'localhost';
Thanks a lot, that solved the problem (and saved my day :) !).
> when you specify the host with -h you are actually forcing MySQL to use
> TCP/IP so it
On 3/16/2012 7:00 AM, Clemens Eisserer wrote:
Hi Rik,
Hm, is the mysql-client library the same as the mysql-server?
Yes.
And does mysql --host=127.0.0.1 --user=someone -p somedb work (or it's actual
IP-address, forcing the TCP/IP connect instead of possible sockets) ?
This is really strang
> > Hm, is the mysql-client library the same as the mysql-server?
>
> Yes.
Aight...
> > And does mysql --host=127.0.0.1 --user=someone -p somedb work (or it's
> > actual IP-address, forcing the TCP/IP connect instead of possible
> > sockets) ?
>
> This is really strange - with -h127.0.0.1 I get
If you want to verify it is very easy:
$ mysql --user=someone somedb (without -p)
mysql> select user(); select current_user();
cheers
Claudio
2012/3/16 Claudio Nanni
> you probably have the anonymous user account taking over: ''@'localhost'
>
> when you specify the host with -h you
you probably have the anonymous user account taking over: ''@'localhost'
when you specify the host with -h you are actually forcing MySQL to use
TCP/IP so it will authenticate you using your ip address (127.0.0.1)
login as root and:
mysql> drop user ''@'localhost';
and try again
Cheers
Claud
Hi Rik,
> Hm, is the mysql-client library the same as the mysql-server?
Yes.
> And does mysql --host=127.0.0.1 --user=someone -p somedb work (or it's actual
> IP-address, forcing the TCP/IP connect instead of possible sockets) ?
This is really strange - with -h127.0.0.1 I get the same error:
ERR
Hi,
1. FLUSH PRIVILEGES is not needed, the SQL commands to manage user and
grants reload automatically the grant tables,
that was used in the very past when people use to tinker directly the grant
tables.
2. you did not specify the @ part of the 'someone' : GRANT ALL ON
somedb.* TO 'someone
> Hi Rik,
>
> > Have you tried the _full_ user-identification (which is with host)?
> >
> > GRANT ALL ON somedb.* TO 'someone'@'%';
>
> Yes I had (and just tried to verify) but it didn't help.
Oops, didn't use reply-to-list instead of reply-to-author, my apologies...
> Could it be Fedora's mys
Hi Rik,
> Have you tried the _full_ user-identification (which is with host)?
>
> GRANT ALL ON somedb.* TO 'someone'@'%';
Yes I had (and just tried to verify) but it didn't help.
Could it be Fedora's mysql packages are special somehow?
Re-installing mysql after deletig its data-directory didn't
12 matches
Mail list logo
