I installed MySql community server on Windows 10 Home. Then, I installed WAMP server 64 to setup an Apache php server. Finally, I installed Wordpress where my problem arose. All products are current releases just downloaded.
During installation of Wordpress, phpMyAdmin says the database was created and it shows on the left panel. The name is wordpress_db. MySQL Query Workbench doesn't find it with a SQL show databases command. Wordpress gave an error "not found". I finally manually created the db in MySQL Workbench, rebooted, and after restarting Wordpress on the Apache server created I was able to finish the installation. There were no errors showing with the db create from phpMyAdmin and it allowed me to set privileges for users without a problem. I can't explain what happened and don't particularly like mysteries that just go away. They always com back to haunt you!
Can anyone shed any light on what happened during the installation and db_create?
Thanks in advance for anyone who looks at this.
Update
I uninstalled and reinstalled and the problems went away. Now I am running a MySQL instance that isn't distributed directly from the vendor and I lost some of the things that come with MySQLcommunity server.
One thing to note - the installation docs don't tell you to change the port on MariaDB from 3306 to something else using phpMyAdmin when you are using MySql. Once i changed the port, the server instances instantly popped up green. They were initially orange.
thanks
I am new to using MySQL and I needed to download it for school, however, I keep getting this error message (picture below). I am using xampp and connecting using the username root. the port also matches what it is telling me. It will let me proceed but a lot of the features are missing. Any help at all would be appreciated.
Incompatible/nonstandard server version or connection protocol
detected (10.0.10).
A connection to this database can be established but some MySQL
Workbench features may not work properly since the database is not
fully compatible with the supported versions of MySQL.
MySQL Workbench is developed and tested for MySQL Server versions 5.1,
5.5, 5.6 and 5.7
As I can see, You are using latest XAMPP.
All you need to do is, after opening MySQL Workbench, and instead of setting up a new connection, Press CTRL+R or click on DATABASE tab in the top menu. Select Reverse Engineer and provide necessary information. You are good to go now.
The MySql workbench wont crash or show any compatibility issue now.
The current version of XAMPP uses MariaDB instead of MySQL.
Because MySQL Workbench is designed to work with MySQL and not with the very similar drop in replacement MariaDB, you are gonna have problems ...
So, if you want to use MySQL Workbench with XAMPP then a solution would be to try installing the last version of XAMPP that uses MySQL. That version is probably 1.8.3 from (August of 2014?). You can download it here:
XAMPP Sourceforge old versions
If you are using the latest XAMPP that uses MariaDB, in that case in your MySQL Workbench don't use 'Connect to Database' instead use 'Reverse Engineer' and provide the necessary credentials. That's all, No hassle.
I encounter the same message followed by a crash of MySQL Workbench, with version 6.3.7 (build 1199).
I didn't find a solution, but here is a work-around:
Once you press the button Continue anyway, just open a database use toto, and then wait a bit (a minute is enough in my case), and then you can call a query without a crash. I found this trick here.
I experimented the same with WAMP 3.2.0.
MariaDB was configured to listen to port 3306 (the usal MySQL port) and MySQL 8 was listening on port 3308. If you are in this case, don't be fooled by the fact you have 2 DBs.
To solve this, you have to choose the DB you want. I wanted MySQL and I just ask MySQLWorkBench to open a connection on port 3308 to MySQL.
You can ditch MySQL Workbench, and use the browser made for the MariaDB, they have a free version here: https://www.upscene.com/downloads/dbw
It's limited in its abilities, but I had no troubles connecting and browsing.
I had the similar problem because i was using Denwer at the same time.
To solve the problem:
Stop Denwer
Restart MySQL server
Profit! Now you can open your database in the Workbench
The idea is that denwer was starting its local server which didnt allow MySQL to start normally.
If you want to use denwer at the same time wth MySQL you can just start it after MySQL (Point 4).
In my case I already had MySql server and workbench installed and setup prior to my XAMPP installation. I wanted to continue with my existing setup.
I also installed MySql server with my XAMPP. I started mysql inside XAMPP and when I connected to MySql Workbench, I encountered the same error. Because Workbench was trying to connect with the server which was installed with XAMPP, apparently this was incompatible.
So I stopped mysql in XAMPP and started started mysql server manually(the previous setup and installed server).
Refer this to know how to start mysql manually in windows.
You can also config XAMPP to use your existing SqlServer.
So I had the same problem. For me none of the methods worked, but then I found out that my MariaDB was occupying the same port, so I uninstalled it and that solved the problem.
i had same issue, i changed the mysql server port from 3306 to 3308 in XAMPP config file.
[mysqld]
port=3308
I have been using MySql Workbench to connect to a local MySql server and to remote MySql Servers. The last couple of days the Workbench freezes when I connect to the local version. It still works for the remote servers.
I am using workbench 6.3.4 and then tried 6.2.5 just to see if it is a version issue.
I also can access the local MySql instance using HeidiSQL.
Any recommendations on what to look for?
Update
The advice to recreate the connection solved the issue. I just created a new one and it works fine.
A couple of things you can try:
Try restarting the sql server (remember, workbench is just a utility for accessing a db, it does not host the database for you)
See if you can access mysql on the command prompt / terminal, the command for mac & windows
(once you navigate to the mysql folder, try the command:)
mysql -u root
(if you have a password-protected account, the command will be
mysql -u someuser -p
If the above doesn't work, mysql is either offline or denying you access (depending on response), and you'll need to setup the server / assign privileges.
If all else fails, it may help to try another version of SQL / Workbench (for a easy-to-use sql sever setup, I'd recommend WAMP or MAMP, assuming you want a HTTP server bundled with it)
Additionally, it may help to recreate the local connection in workbench (of if your getting regular crashes, reinstall & update workbench). Good luck with it.
I have a mysql database with 3000 tables, and a hibernate application. It working fine on ubuntu, but on Mac(homebrew) always show connection errors after
ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - HHH000319: Could not get database metadata
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could not create connection to database server. Attempted reconnect 3 times. Giving up.
I doubt some setting for mysql need to be change, but do not know which one.
Looks like your database server isn't responding.
Check the configuration files for hibernate and make sure that it's pointed at the right host for the database.
If you're using localhost, make sure that the mysql server you're running locally is up (ps or mysql command should help here) and verify that hibernate is either communicating over the UNIX socket, or that you have networking turned on in your local server (since by default it's usually off and required for TCP/IP access, even to localhost).
Fixed after added 'max_allowed_packet=20M' to my.cnf
I'm having an issue on both a win7 development machine, and on a windows 2008 production server with connecting to a remote Suse Linux server to mysql over SSH. I've followed the very simple instructions here.
http://realprogrammers.com/how_to/set_up_an_ssh_tunnel_with_putty.html
only on the last step, i'm trying to use the odbc connector that I downloaded from here.
http://dev.mysql.com/downloads/connector/odbc/
trying both localhost:3306 and 127.0.0.1:3306 doesn't seem to make a difference. I CAN log into the linux server in putty over ssh, and use the command line from the terminal to connect to mysql. My issue is that I need the windows server to be able to connect and query data from the mysql instance on the linux server. When I attempt to connect from the odbc connector it immediately pops up an error that root#localhost is denied with password=YES. I've checked my user table in mysql and root is set to allow login from any host, including localhost. Anyone have any other suggestions for getting this to work? It's quite urgent as we need to plan for a data synchronization of several gigs by this Saturday. Thanks in advance for any help.
Okay, I figured this out... You have to run putty.exe as an administrator. Once I did that the connection worked just fine. Hopefully this saves someone a few hours of work down the road. Thanks to bfavaretto for his help.