mySQL workbench hangs after connecting to database - mysql

I am using MySQL workbench 6.3 CE to connect to mysql database on amazon aws (rds) system. I was running a create table query that was taking too long (lot of joins), and I stopped the query, and closed the workbench from Task Manager (end process). Since that operation:
1) I can open the workbench connect to the database, but once I connect and select any table from the schema, the workbench hangs.
2) No query could be run from workbench - I have to stop the query and I get the error "Interrupt: Error 2006, Mysql server has gone away".
3) if I click on the table name in the object browser, I don't see any columns for the table.
I tried to run the queries from the command line (in the workbench, right click on the database connection and click "Start command line client" - and here, I am able to run queries without issue. However, I have connected to this database through RODBC - in R, none of the odbcCommands are working (sqlTables() hangs, etc).
I am at my wits end trying to understand whats wrong - any pointers would be wonderful.
Thanks.

Actually, I realized it was because I stopped the create table query - I don't know the mechanics, but apparently, there was a background process running. I had to kill the query and kill the connection and everything was back to normal.
Hope this helps someone some other time.

Related

AWS MySQL Database Disappearing

I have a MySQL database running on AWS RDS. I have a node.js server that queries the MySQL database. Everything is fine for most days but around once a week, my node server says "Unknown database."
I try to query the database with MySQL Workbench and receive the same message. I have checked my instance and it is running fine with the status being "available."
To fix the issue, I have to recreate the database which means I lose all my data.
Has anyone had issues with this? This is very frustrating since I have no idea what would cause this problem.
We‘re running MySQL RDS databases since AWS launch and never had such an issue. Are you sure the created database is really gone? Do you maybe have a job running at an interval that doesn’t work as intended? What do the RDS logs say?
To debug the issue you can
have a look at RDS server logs
enable query logging to table and analyze queries fired at the server
run a small instance which is not touched for the period to proof it’s not a RDS-related isssue
A few years later...lol. I had the same problem and realised you have to be connected to the same domain in AWS as your database. If you know the connection string of your database, find the domain it is in. Then in the top right hand side of the aws console you should see a drop down that shows the current domain you are logged into. My guess is the two are not the same. Change the value of the drop down and you should see your database.

Mysql workbench loses connection after restarting computer

I have installed Mysql server and mysql workbench and have successfully used mysql workbench to work with my databases. I used it and have since then closed the program and shut off my computer. Now when I click on my connection, it shows a server status screen and says 'no connection'. I get error message 10061 could not connect server may not be running. This is the second time this happened to me and I find that reinstalling mysql fixes this. The problem is I cannot reinstall every time I need to use mysql workbench. What can I do to solve this?

phpMyAdmin freezes when running any query

I have a new MacBook Pro and have installed/configured development environment to include PHP and MySql in particular. MySql Workbench works 100% and I can run queries from terminal (i.e., the command line). However, every SQL query I run in phpMyAdmin simply freezes. No matter how simple the query. The exact same query runs fine in MySql Workbench, but I much prefer phpMyAdmin.
I've followed this and reinstalled mysql and phpMyAdmin twice.
https://coolestguidesontheplanet.com/get-apache-mysql-php-and-phpmyadmin-working-on-macos-sierra/
I suspect there is a permission setting somewhere.
What am I doing wrong? Why would phpMyAdmin work, but not execute queries?
Any thoughts are greatly appreciated.

How do I Respond to MySQL Workbench's "MySQL server has gone away"?

I'm using MySQL Workbench 6.3 on both Mac OS X and Centos 7. After a long period of inactivity, queries report "Error Code 2006: MySQL server has gone away"
I don't expect that leaving MySQL Workbench to maintain a connection to the server overnight, especially if I've let my computer go to sleep.
I do expect that there's a button or menu item somewhere that lets me reconnect again, WITHOUT having to copy the dozens or hundreds of lines of SQL I may have written in my current session.
I've been warned that I let my connection timeout, MySQL Workbench, now is there a way to please please just reconnect?
Try Query -> Reconnect to server.
http://prntscr.com/auqdru

Using MySQL workbench I can't create new connections

I have a freshly installed workbench 6.3 version and a 5.1 mysql Server version.
I already have connections created. Namely, I can successfully connecto to local Instance MySQL56, which I assume is a default connection. I have two, way older connections that have appeared even though last time I used this program (and later uninstalled) was months ago, with another version.
I've read what I've found and felt could help
MySQL Workbench 5.2 CE, Windows 7, "Can't connect to MySQL Server on 127.0.0.1 (10061)"
MySQL Workbench: "Can't connect to MySQL server on 127.0.0.1' (10061)" error
And tried every option. Nothing works. I try to create a connection with this steps:
Database -> manage connections -> bottom left corner: New
Then I give it a name, leave everything as default, put a pw into the vault, and try to test it. Does not work. Whatever combination I try, it does not work. Yes server is running, I've tried 3 different ways of checking.
I do not understand at all how something I've done in the past is taking me so many hours, I do not know what I'm missing, but I can't create a new connection.
Also to be noted, in case it's useful: On default schema, I write the name of a schema I previously created. Thing is, as I said, I've tried every combination. But when I've tried to save said schema in a folder, workbench has instantly crashed. Twice already.
I'm all out of ideas, so if anyone can tell me what to do, it'd be of great help, I find nothing following guides out there.