/ server and db
using both localhost and 127.0.01 ... it gets the same error :
access denied for user 'root'@'localhost'
the app has a php config page where it fills these info
I am able to connect to it manually too using :
./mysql -h localhost -u root -p mysql-admi
... it gets the same error :
access denied for user 'root'@'localhost'
the app has a php config page where it fills these info
I am able to connect to it manually too using :
./mysql -h localhost -u root -p mysql-admin
but the app keeps geting the access denied error
w
Hello Érico
On 5/29/2014 2:22 PM, Érico wrote:
I have ran the following to test a fix for an app issue :
delete from mysql.user where user='';
2lines got effected
after this I can´t connect through command line anymore :
./mysqladmin -u root password
I get access denied for
well, i am mysql administrator over 10 years now
and never needed the "mysqladmin" command because
the mysql command line client offers anything i
ever needed
mysql -u root -p
[harry@srv-rhsoft:~]$ mysql -u root -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; o
running this :
./mysqladmin -u root -p
at this momento it thorws me to mysqladmin man page
2014-05-29 15:35 GMT-03:00 Reindl Harald :
>
> Am 29.05.2014 20:22, schrieb Érico:
> > I have ran the following to test a fix for an app issue :
> >
> > delete from mysql.user w
root/localhost ... ?
one with pwd filled
and the second with the pwd empty
how can I insert on this table with the mandatory column ssl_cipher as blob
... ? what value must I provide in a insert like :
insert into mysql.user(host,user,ssl_cipher) values('localhost','root' ,
???
#x27;;
> 2lines got effected
>
> after this I can´t connect through command line anymore :
>
> ./mysqladmin -u root password
>
> I get access denied for user 'root'@'localhost" (using password:'NO')
>
> how can I restore the db so I can connect through command line again ?
>
> thks
>
Am 29.05.2014 20:22, schrieb Érico:
> I have ran the following to test a fix for an app issue :
>
> delete from mysql.user where user='';
> 2lines got effected
>
> after this I can´t connect through command line anymore :
>
> ./mysqladmin -u root password
I have ran the following to test a fix for an app issue :
delete from mysql.user where user='';
2lines got effected
after this I can´t connect through command line anymore :
./mysqladmin -u root password
I get access denied for user 'root'@'localhost" (using pas
ok
I have tried these :
ifconfig -a
lo0: flags=8049 mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff00
gif0: flags=8010 mtu 1280
stf0: flags=0<> mtu 1280
fw0: flags=8863 mtu 4078
lladdr 70:cd:60:ff:fe:eb:72:ea
media:
Hi
> > > | | ericomtxmacbookpro.local |
> > *E85DC00A0137C6171923BE35EDD809573FB3AB4F |
> > >
>
mysql> DELETE FROM mysql.user WHERE user='';
mysql> FLUSH PRIVILEGES;
maybe helps?
Cheers
--
Claudio
+
> > | user | host | password
> |
> >
> +--+--+---+
> > | root | localhost|
> *E85DC00A0137C6171923BE35EDD809573FB3AB4F |
> > | root | ericomtx
Am 13.01.2014 21:47, schrieb shawn l.green:
> Hello Reindl,
> We are not saying he is using HTTP commands to log into his database
we excludes obviously the OP or his overall understanding :-)
Am 13.01.2014 18:54, schrieb Érico:
> using both urls I get the same error :
>
> http://localhost/mysql
fer-Encoding: quoted-printable
Please provide the output of the below query.
Select user, host, password from mysql.user;
Thanks
Vikas Shukla
Mail Sent from my Windows Phone From: Reindl Harald
Sent: =E2=80=8E14-=E2=80=8E01-=E2=80=8E2014 01:38
To: mysql@lists.mysql.com
Subject: Re: Access den
validating
his account on one instance but his tools are attempting to connect to a
different instance.
And whether I say
mysql -u root -h localhost (via Unix socket)
or I say
mysql -u root -h 127.0.0.1 (via TCP socket)
they may /both/ be reported as 'localhost' in the err
>>>
>>> look ... isn't this something related to this :
>>>
>>> are you using "localhost" or "127.0.0.1" in the web-application
>>> root@localhost != root@127.0.0.1 = different users
>>>
>>> localhost: Unix-Socket
0.0.1... after I submit the index.php ... it redirects to localhost
> too ..
>
> 2014/1/13 Reindl Harald
>
>>
>>
>> Am 13.01.2014 18:28, schrieb Érico:
>>> ericomtxmacbookpro:bin ericomtx$ ./mysql -u root -p mysql-admin
>>> Enter password:
>&
connect through
command line
Thks
2014/1/13 shawn l.green
> Hello Érico,
>
>
> On 1/13/2014 1:49 PM, Érico wrote:
>
>> Hi
>>
>> didn't work
>>
>> look ... isn't this something related to this :
>>
>> are you using "localhost&qu
Hello Érico,
On 1/13/2014 1:49 PM, Érico wrote:
Hi
didn't work
look ... isn't this something related to this :
are you using "localhost" or "127.0.0.1" in the web-application
root@localhost != root@127.0.0.1 = different users
localhost: Unix-Socket
127.0.0.1:
Hi
didn't work
look ... isn't this something related to this :
are you using "localhost" or "127.0.0.1" in the web-application
root@localhost != root@127.0.0.1 = different users
localhost: Unix-Socket
127.0.0.1: TCP
...
since I am not able to stabilsh a conn
On 13 January 2014 13:25, Érico wrote:
> the granting is not affecting the tables:
>
> mysql> grant all privileges on *.* to root@localhost identified by 'pwd';
> Query OK, 0 rows affected (0.00 sec)
>
> mysql> FLUSH PRIVILEGES;
> Query OK, 0 rows affected (0
the granting is not affecting the tables:
mysql> grant all privileges on *.* to root@localhost identified by 'pwd';
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
...
and if I try the granting in 127.0.0.1 :
mysql> gran
I forgot this. Do it too.
On 13 January 2014 13:01, Erick Ocrospoma wrote:
> I presume your index.php file uses "127.0.0.1". After login to MySQL try this:
>
> $> grant all privileges to *.* 'root'@'127.0.0.1' identified by
> ;
$> flush priv
I presume your index.php file uses "127.0.0.1". After login to MySQL try this:
$> grant all privileges to *.* 'root'@'127.0.0.1' identified by ;
Of course this could not be the best solution, it's just to skip it,
you must look at the query/connection on yo
using localhost the coonection works ...
ericomtxmacbookpro:bin ericomtx$ ./mysql -u root -p mysql-admin -h
localhost -P 3306
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Welcome to the MySQL
ro:bin ericomtx$ ./mysql -u root -p mysql-admin
> > Enter password:
> > Welcome to the MySQL monitor. Commands end with ; or \g.
> > Your MySQL connection id is 31
> > Server version: 5.6.15 MySQL Community Server (GPL)>
> >
> > but in the browser I get the er
>From that error I would suspect you are trying to access to a database
where has not external access. And yeah, try by doing
$> mysql -u root -p -h localhost -P 3306
change localhost by 127.0.0.1 in order to test if both cases work, and
see which of them (localhost/127.0.0.1) is defi
Am 13.01.2014 18:28, schrieb Érico:
> ericomtxmacbookpro:bin ericomtx$ ./mysql -u root -p mysql-admin
> Enter password:
> Welcome to the MySQL monitor. Commands end with ; or \g.
> Your MySQL connection id is 31
> Server version: 5.6.15 MySQL Community Server (GPL)>
>
>
Hi
I have installed mysql admin on my local environment
I am able to connect to mysql through command line :
ericomtxmacbookpro:bin ericomtx$ ./mysql -u root -p mysql-admin
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 31
Server version
Hi Miguel,
I'm confused. Where should I issue those commands?
Yes from the MySQL Administrator.
From what you say it seems that you end up being authenticated as the
''@'localhost' user.
Connect again with the MySQL Administrator and the non-root account and
is
mysql administrator I get the username correctly.
Regards and thanks for the promptly answer
Miguel
De: Claudio Nanni
Para: Miguel Gonzalez
CC: Tim Pownall ; mysql.
Enviado: Miércoles 29 de Mayo de 2013 9:24
Asunto: Re: SSH tunnels and non root accounts get
Miguel,
Probably your non-root user is connecting as the anonymous account.
Try this:
Connect as your (problematic) non-root account and do this:
mysql> SELECT USER();
mysql> SELECT CURRENT_USER();
What do you see?
If it's as I imagine you should see different values and so just
In my email I state quite clearly that tunnel is working with the root account
so it's not a matter of ports.
The error message shows that is trying to get some configuration from the user
account that is not working. Under root account I have found a file called
.my.cnf with a [client]
:05 PM, Miguel González wrote:
> Dear all,
>
> Not sure if this the right mailing list address for asking this.
>
> Server running Centos and MySQL.
>
>Client is a windows xp machine.
>
>I have setup a SSH tunnel with putty and run mysql administrator. It
PM, Miguel González
wrote:
> Dear all,
>
> Not sure if this the right mailing list address for asking this.
>
> Server running Centos and MySQL.
>
>Client is a windows xp machine.
>
>I have setup a SSH tunnel with putty and run mysql administrator. It
> wo
Dear all,
Not sure if this the right mailing list address for asking this.
Server running Centos and MySQL.
Client is a windows xp machine.
I have setup a SSH tunnel with putty and run mysql administrator. It
works fine with the root account.
With a non-root account I get
Hello Round,
On 12/27/2012 5:34 AM, Round Square wrote:
On 12/26/2012 01:25 PM, Igor Shevtsov wrote:
You mysql.user table might be corrupted.
If you have access to it as a root user, try check table mysql.user, and repair
table mysql.user if table corruption was detected.
Alternatively, shut
On 12/26/2012 01:25 PM, Igor Shevtsov wrote:
> You mysql.user table might be corrupted.
> If you have access to it as a root user, try check table mysql.user, and
> repair table mysql.user if table corruption was detected.
> Alternatively, shut down mysql server, cd /var/lib/mysql/my
You mysql.user table might be corrupted.
If you have access to it as a root user, try check table mysql.user, and
repair table mysql.user if table corruption was detected.
Alternatively, shut down mysql server, cd /var/lib/mysql/mysql (to your
$datadir/mysql directory) and run
mysqlcheck -r
Hi all:
Suddenly, after a long, functioning run of the mysql server, all the non-root
accounts went bad, with:
Access denied for user 'non_root_user'@'localhost' (using password:
YES)
Authenticating with "non_root_u...@server.ip.address" still works
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
and -P forces TCP-IP
Cheers!
Claudio
2012/3/16 Clemens Eisserer
> Hi Claudio,
>
> > you probably have the anonymous user account taking over:
> ''@'localhost'
> > login as root and:
> > mysql> drop user ''@'loca
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 wi
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
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
>
> Claudio
>
>
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 ''@&#
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
omedb.* TO 'someone'@'.' IDENTIFIED BY 'somepass';
cheers
Claudio
2012/3/16 Clemens Eisserer
> Hi,
>
> All I would like to do is the create a small database with a non-root
> user which is allowed to access the db, however after hours of trying
> I gave
> 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
Hi,
All I would like to do is the create a small database with a non-root
user which is allowed to access the db, however after hours of trying
I gave up.
I am using MySQL-5.5.20 on Fedora16 .
CREATE USER 'someone'@'%' IDENTIFIED BY 'somepass';
CREATE DATABASE so
::1 is the IPv6 address for localhost.
On 18 Dec 2011, at 09:17, lourenstcc wrote:
Hi,
I installed mysql for mac os x. Now I am inspecting mysql.user and I
see entries for root which I am not to confident with.
On a debian installation there is no host=::1 entry
Can you explain this entry
Am 18.12.2011 18:17, schrieb lourenstcc:
>
> Hi,
>
> I installed mysql for mac os x. Now I am inspecting mysql.user and I
> see entries for root which I am not to confident with.
> On a debian installation there is no host=::1 entry
man network-basics
::1 = IPv6 for lo
Hi,
I installed mysql for mac os x. Now I am inspecting mysql.user and I
see entries for root which I am not to confident with.
On a debian installation there is no host=::1 entry
Can you explain this entry? (Could I have inadvertantly made it myself?)
Here:
mysql> select user, host, passw
>
> I also followed various instructions in the MySQL documentation for
> resetting lost passwords. But the results persuaded me that the problem is
> something else: the installer does not create a root account or a mysql
> account in the user table. Thus the update command for resett
installer does not create a root account or a mysql
account in the user table. Thus the update command for resetting the root
password executes correctly but update 0 rows. And logging in with the
skip-grants-table lets you address some queries to the mysql user table.
"Select count(user)
- Original Message -
> From: "David Lerer"
>
> Thanks Bier. I see what you mean.
> (As a rule we always use SQL SECURITY INVOKER)
Both have their use, although I would very much prefer MySQL to default to
INVOKER if not specified, instead of the extremely annoying-when-migrating
DEFINE
There is no 'root'@'%' registered
error message
- Original Message -
> From: "David Lerer"
>
> Correct me if I am wrong, but my impression is that usage of
> "DEFINER=" in stored procedures has no impact on runtime and
> is actua
- Original Message -
> From: "David Lerer"
>
> Correct me if I am wrong, but my impression is that usage of
> "DEFINER=" in stored procedures has no impact on runtime and
> is actually optional.
> (not to be confused with the clause SQL SECURITY INVOKER which is
> crucial.)
You can also
Correct me if I am wrong, but my impression is that usage of
"DEFINER=" in stored procedures has no impact on runtime and is
actually optional.
(not to be confused with the clause SQL SECURITY INVOKER which is
crucial.)
Note: I use 5.1.32-enterprise-gpl-advanced-log.
David.
--
MySQL General Mail
- Original Message -
> From: "Brent Clark"
>
> I know the answer (well I think I do :) ), but im still going to ask.
> What is the risk if do the "GRANT ALL PRIVILEGES ON *.* TO 'root'@'%'
> IDENTIFIED BY 'mysql' WITH GRANT OPT
Perhaps he could make the stored procedure functional by creating a user
with the EXECUTE permission (somebody please fell free to correct me if I am
mistaken) if it is to be used to execute a stored procedure. You don't want
someone to attempt using the 'root' username with a
It would allow anyone from anywhere to access your server as root with full
access to all databases using the password 'mysql'. Not very secure. I don't
recommend having a root@% defined.
On Aug 17, 2011 8:50 AM, "Brent Clark" wrote:
Hiya
Thank you so much for replyin
Hiya
Thank you so much for replying. I really appreciate it.
I know the answer (well I think I do :) ), but im still going to ask.
What is the risk if do the "GRANT ALL PRIVILEGES ON *.* TO 'root'@'%'
IDENTIFIED BY 'mysql' WITH GRANT OPTION;"
To satisf
Change the definer to one of your registered root accounts. Root@127 or
root@localhost.
On Aug 17, 2011 8:39 AM, "Brent Clark" wrote:
Hiya
Ill be up front my saying my knowledge of store procedures is limited.
A Developer gave me a procedure to load.
It starts off with:
CREATE DEF
Hiya
Ill be up front my saying my knowledge of store procedures is limited.
A Developer gave me a procedure to load.
It starts off with:
CREATE DEFINER=`root`@`%` PROCEDURE
But now, the developer informs me that he gets the following message.
There is no 'root'@
On Mon, 06 Jun 2011 18:54 +0200, "Johan De Meersman"
wrote:
> > Excluding 'performance_schema' appears to eliminate the error. And it
> > seems does NOT cause a reliability-of-the-backup problem.
>
> Hah, no, backing that up is utterly pointless.
that's a useful/final confirmation. thx.
> No,
- Original Message -
> From: ag...@airpost.net
>
> Excluding 'performance_schema' appears to eliminate the error. And it
> seems does NOT cause a reliability-of-the-backup problem.
Hah, no, backing that up is utterly pointless. Never noticed it doing that.
It's basically a virtual schem
On Mon, 06 Jun 2011 12:44 +0200, "Johan De Meersman"
wrote:
>
> I haven't bothered to look for the "bug", but it seems to me to be quite
> reasonable default behaviour to lock the whole lot when you're dumping
> transactional tables - it ensures you dump all tables from the same
> consistent vi
I haven't bothered to look for the "bug", but it seems to me to be quite
reasonable default behaviour to lock the whole lot when you're dumping
transactional tables - it ensures you dump all tables from the same consistent
view.
I would rather take this up with the ZRM people - it should "just
Am 05.06.2011 23:55, schrieb ag...@airpost.net:
> i still have no idea why this is necessary.
take it or not
it is a professional solution which works for
databses with 20 GB every day here with rsync
without interrupt/lock mysqld a second
and it is much faster
> there seems to be a but, prob
i still have no idea why this is necessary.
there seems to be a but, problem, misconfiguration, etc.
wouldn't it make some sense to try to FIX it, rather than setting up a
completely different server?
perhaps someone with an idea of the problem and its solution will be
able to chime in.
--
My
Am 05.06.2011 23:49, schrieb ag...@airpost.net:
>
> On Sun, 05 Jun 2011 23:29 +0200, "Reindl Harald"
> wrote:
>> i would use a replication slave and stop him for consistent backups
>> because dumb locks are not really a good solution independent
>> if this works "normally"
>
> unfortunately, i
On Sun, 05 Jun 2011 23:29 +0200, "Reindl Harald"
wrote:
> i would use a replication slave and stop him for consistent backups
> because dumb locks are not really a good solution independent
> if this works "normally"
unfortunately, i have no idea what that means.
something's apparently broken w
On Sun, 05 Jun 2011 23:30 +0200, "Reindl Harald"
wrote:
> BTW
> WHY is everybody ansering to the list AND the author of the last post?
> this reults in get every message twice :-(
Reply -> sends to ONLY the From == h.rei...@thelounge.net
Reply to all sends to BOTH the From == h.rei...@thelounge.n
ng added as i mentioned above, to the [mysqldump] section of
> /etc/my.cnf, does NOT make a difference for me.
>
>
> On Sun, 05 Jun 2011 23:19 +0200, "Reindl Harald"
> wrote:
>> the grant statements does nobody interest
>> mysql> select * from mysql.user whe
ks to your mysqldump command"
>
> which, having added as i mentioned above, to the [mysqldump] section of
> /etc/my.cnf, does NOT make a difference for me.
>
>
> On Sun, 05 Jun 2011 23:19 +0200, "Reindl Harald"
> wrote:
>> the grant statements does nobody i
-add-locks to your mysqldump command"
which, having added as i mentioned above, to the [mysqldump] section of
/etc/my.cnf, does NOT make a difference for me.
On Sun, 05 Jun 2011 23:19 +0200, "Reindl Harald"
wrote:
> the grant statements does nobody interest
> mysql> select
the grant statements does nobody interest
maybe use phpmyadmin for a clearer display
mysql> select * from mysql.user where user='root&
hi,
On Sun, 05 Jun 2011 22:24 +0200, "Reindl Harald"
wrote:
> have you checked you permissions-table if all privileges are active for root
i've got,
mysql> show grants
have you checked you permissions-table if all privileges are active for root
and have you started "ymsql_upgrade" after all updates?
Am 05.06.2011 22:20, schrieb ag...@airpost.net:
> i use ZRM to do backups of my databases.
>
> with v5.1.x, this works fine,
>
>
e_schema >
"/var/mysql-bkup/manual/20110605131003/backup.sql"
mysqldump: Got error: 1142: SELECT,LOCK TABL command denied to
user 'root'@'localhost' for table 'cond_instances' when using
LOCK TABLES
--> manual:backup:
On 21.12.2010 11:27 CE(S)T, 杨涛涛 wrote:
> Maybe you should give a password to MySQL's root. And I think this note will
> disappear.
I would be extremely dumb not to set any password on MySQL's root
account at all! Of course (I hope I made that clear before) a password
has been set
Maybe you should give a password to MySQL's root. And I think this note will
disappear.
David Yeung, In China, Beijing.
My First Blog:http://yueliangdao0608.cublog.cn
My Second Blog:http://yueliangdao0608.blog.51cto.com
My Msn: yueliangdao0...@gmail.com
2010/12/17 Yves Goergen
> On 14
rver-5.1. It has already asked for a root
password during package configuration and I did enter some password there.
I just tried to grep my whole filesystem for parts of this message but
either grep failed "allocating memory" (there's plenty left!) or it
didn't find the text in
On 13.12.2010 15:26 CE(S)T, who.cat wrote:
> try /mysql_bin_path/mysql_secure_installation !
> Hope it helpfu!
I already followed that path and it doesn't quite help. I've done the
checks that the install script does and my installation is secure by
those means. But I don't want to install things
Hi,
I find the following line in my syslog events:
Daemon Error mysqld
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
followed by a whole lot of notes, advice and web links. I do have set a
custom password for root, root is not accessible from remote, the
anonymous user does not
Appreciate any help on this.
Any alternative of mysqldump is also fine with me to take backup while
restricting root login access from localhost only.
Thanks in advance.
Regards,
Tanmay
On Wed, Oct 20, 2010 at 10:14 AM, Tanmay Pradhan wrote:
> Yes, r...@localhost entry is still present in u
Yes, r...@localhost entry is still present in user table. Only
root@'%' is deleted. So it's not obvious to fail.
Hi yu.zou,
The r...@localhost entry already had all privileges, except this entry
had empty password column.
u...@localhost ent
Hellpo Krishna,
On 10/19/2010 8:40 AM, Krishna Chandra Prajapati wrote:
Hi Pradhan,
Obviously, it should fail. Since you have deleted the root user which is
used by mysqldump for making connection to mysql server for taking backup
Not true. The utility mysqldump is just a client like any
Of course you know you did not delete r...@localhost, just root @ '%'
which generally should not matter to mysqldump.
What I suspect is the issue here is that the database you are trying
to dump contains procedures/methods that were defined by a user while
logged in as root@'%
Hi Pradhan,
Obviously, it should fail. Since you have deleted the root user which is
used by mysqldump for making connection to mysql server for taking backup
Krishna
CGI.COM
On Tue, Oct 19, 2010 at 11:06 AM, Tanmay Pradhan wrote:
> Hi,
>
> I am using the following version of My
Hi,
I am using the following version of MySQL on my Mac OS X Server 10.5.8:
*** Ver 14.14 Distrib 5.4.1-beta, for apple-darwin9.5.0 (i386) using
readline 5.1 ***
In order to restrict root account login from localhost only, I did the
following:
mysql> DELETE FROM user WHERE user = 'root&#
ions about this on the web but no
>> resolution yet.
>>
>>
>> When MySQL runs out of threads, you are unable to stop /
>> restart the database.
>>
>>
>> Is there a way to reserve threads for the root user /
>> database restarts?
>&
database.
Is there a way to reserve threads for the root user /
database restarts?
Yes. Don't give normal users the SUPER privilege.
http://dev.mysql.com/doc/refman/5.1/en/privileges-provided.html#priv_super
Your applications and non-administrative users should be using acc
threads for the root user /
database restarts?
Current version running: 5.0.72sp1-enterprise-gpl-log
Machiel Richards
MySQL DBA
Relational Database Consulting
RDC_Logo
ble started.
>
> According to a windows user, he could do that on my.ini , and I didn't find
> that on Ubuntu 9.04, so I've tried to run a command I found on Mysql
> Reference manual, 5.1. located on (
> http://dev.mysql.com/doc/refman/5.1/en/log-tables.html).
>
> So I at
found on Mysql
Reference manual, 5.1. located on (
http://dev.mysql.com/doc/refman/5.1/en/log-tables.html).
So I attempted something like #mysql -u"mydbrootid" -p"mydbrootpass"
--log-output=TABLE
After that and other few tempts trying that, suddently my root was not able
to
1 - 100 of 819 matches
Mail list logo
