Is there a limit on the size of the databases that WB can connect to MySQL? Maybe it was the size of the schemas with MyISAM that were too big. I have created a new schema with MyISAM and now I am able to connect to MySQL using the WB. I have not being able to recreate the issue again. So I decided to remove the schemas with MyISAM storage engine from the command line.Īfter I removed all the MyISAM schemas I managed successfully to use the WB to connect to MySQL. The schemas with MyISAM were created using the old MySQL browser and the size of those schemas were quite large. I then remembered that I had some schemas with MyISAM storage engine and some other schemas with INNODB. I dont see anything with mysql in the 'M' section of services. The error I got is: : exception in grt execute_task, continuing: Exception: Access denied for user (using password: NO) scroll down for mysqlXX, XX is some number i think today is 80.
With WB I could not connect to MySQL using a new connection with the following parameters: I could connect to MySQL from the command line using the root user but not using the WB.įrom the command line I tried successfully the following commands: Your server is not configured to accept network connections so you have to switch to change your. sudo mysql -u root -p Create a user named 'admin' and use that to connect in mysql-workbench.
To enforce a tcp connection you have to either set the host to 127.0.0.1 or use the -protocoltcp parameter. MySQL 5.7 and up dont support connecting as 'root' in mysql-workbench so you must create a normal user and connect via that. When I put in all the right credentials and try to connect to the user that I set up for the job and runs with. I have also upgraded MySQL Workbench from 5 to 6.0.7. When you specify localhost as the host to connect to, the mysql commandline client tries to connect using a local socket. I'm trying to connect to my MySQL server, which is sitting at home, having a static ip, from school using MySQL Workbench. I have recently upgraded from Ubuntu 12.04 to 13.04. Most likely, the problem lies with the privileges for the 'root' account on the remote machine.
0 kommentar(er)
