Binary Logging is turned on. The log file, device-bin.index, is present.
When I click Server/Server Logs I get tabs for Error Log File, General Log File, and Slow log File. I don't get a tab for the Binary Log.
MySQLWorkbench version 6.3, MySQL Server Version 5.7.18
For MYSQL Workbench 8.0 you can access the logs in the Help menu -> Locate log files.
MySQL Workbench has no support for the binary log in the log viewer. Only what is of common interest is there.
Related
I'm scared to ask this because people can be a little mean on here but I've watched 1000 of YouTube videos and went through just as many google searches. I was trying to create a data dictionary for mysql diagram. I used this website https://dataedo.com/kb/tools/mysql-workbench/how-to-export-data-dictionary#toc_0 to help me. I downloaded the .py link listed in the install plugin step. The followed the instructions in mysql. It said the plugin install was successful and to restart my workbench. After that I started getting the error shown in the picture. I have tried everything:
Restart workbench
Repair workbench through msi download
Followed the steps in this link: https://www.tutorialspoint.com/how-do-i-kill-all-the-processes-in-mysql-show-processlist
Updated all my sql products in mysql installer
Made sure mysql services were turned on and running
I don't know what else to do. I can't even open workbench to see if the plugin is the issue because again I can't get in. I just need some help
That is a strannge error, where mysql workbench has some corrupt files.
Deinstall MySQL Workbench with the MySQL Installer
Install Workbench again
So everything will start normal again, the configuration and connections will stay and can be used again as normal
This is not an installation issue, so don't waste your time by trying to fix this issue by repeating the installation.
The error comes from the approach where MySQL Workbench tries to ensure there's only one instance of it running. For that it searches the process list for another instance and, if one was found, sends the command line parameters it got to that instance, letting the already running instance handle them (and shuts itself down after that).
But again: this happens only if another instance is found, so check your process list carefully. Filter by the term "MySQL" to see any MySQL related processes (including that of a MySQL server). Shutdown/kill any of these processes and try launching WB again.
Same issue happened to me and it was like what the heck. Don't waste your time to uninstall and reinstall because it won't solve your problem.
Solution: open your file explorer and delete the entire folder "Workbench"
Path: %appdata%\MySQL\Workbench
I have the same issue with this file.
Just as Jr Relampagos says, delete the .py file here : AppData\Roaming\MySQL\Workbench\modules
Restart Workbench, it works for me.
With me I'm just go to C:\Users<USER>\AppData\Roaming\MySQL\Workbench\modules and then delete the .py file you install, then open the Workbench again
There is a serious problem with the new update of the Liquid Xml and i can't figure it out.
When open a new xml file by clicking on it i receive the error:
"There was a problem sending the command to the program." and then
the file is open.
When trying to validate an xml file with a schema i receive errors that elements are not found. Doing the same validation with
LiquidXml on another computer all is fine. How can i downgrade this
version because is not OK.
We have seen this on some PCs, it looks like a DDE timeout issue which we are working on a resolution. We see the file does actually open, but Windows shows the error as you describe. Is this what you see, or does the file not open either?
Do you have a specific schema, or any schema? E.g. if you open the sample project and open the BookStoreSample.xml and press F7 do you get the issue?
If you want to uninstall, you can do so using the 'Change or remove a program' from Windows Control Panel. You can then download and install the 2016 version:
https://www.liquid-technologies.com/my-downloads
Note: you need to login as the user who purchased the license.
Every time I start MySQL workbench I get this message
I would like to know what this means and how I can get rid of it... I tried looking on the internet and googling the entire message but no good info came up because you can't see the full message.
Does anyone know what this means and if it's a problem for my database?
MySQL Workbench tries to load its workspace data and something is wrong with it. Rename the MySQL Workbench folder (the part you can see in the message) or remove it entirely. Then restart the application and it will recreate all the files.
A side note: often Ctrl+C works in those dialogs, so you can paste the entire content into a text editor.
It's only MySQL workbench which is a GUI for data admin if i'm not mistaken (like navicat). You could simply run the mysql installer and remove/add MySQL workbench again.
I'm following the tutorials and samples of the official WSO2 ESB documentation. When I create (or load) a synapse configuration in the WSO2 Developer Studio I'm getting the error as shown below:
Save problems
Save could not be completed.
Reason:
resources\sunErrorHandler.esb_diagram (The system cannot find the path specified)
This error shows up when I want to open anything in the Design view. Even when I'm not trying to save anything.
So far I have tried to add the path specified in the error, but without success. I already found a workaround to be able to save and deploy my ESB configurations. By using "Save as" I'm able to keep the changes I made in the XML files. However the error stills shows up when I open the new version of the file.
Does anyone know a better solution to permanently resolve this error message?
I had this problem as well, running eclipse.exe as administrator fixed it.
Issue remains unresolved for my Eclipse + DevStudio 3.8.0 install on a Windows 10 environment. However since I was experiencing some other issues with the WSO2 ESB I decided to migrate to a Linux (Ubuntu) environment. This seems to work much better, the eclipse does not seem to have this issue on Linux.
Eclipse want to write in C:\Program Files\eclipse\resources. I solve problem by adding full permissions to group users on folder C:\Program Files\eclipse
If this happens in Mac you can provide the required permission to the "/Applications/IntegrationStudio.app/Contents/MacOS/resources" folder.
In Eclipse(version 3.6.2.M201102101200/Helios service release 2). I am getting a strange error when I run a large Java project called ACE toolkit. Below is a picture:
What are possible reasons it would do this?
can it be that Java runtime version is incompatible? The project was built for Java 1.5, but I have 1.6 running.
I appreciate any tips or advice.
There could be any number of reasons for eclipse crashing, from insufficient memory to a misbehaving plugin. The first place to start troubleshooting would be the C:\path\to\your\workspace\.metadata\.log file. You might find something helpful if you examine the end of this file soon after eclipse crashes.
From the documentation:
Eclipse has a log file where problems are recorded and usually this is the first thing that an Eclipse developer asks for when you report a problem. The log file can be found in a couple of places:
Workspace log - This is the most common location for the log file, It is stored in your workspace in the meta-data directory. Check out
workspace/.metadata/.log.
Configuration log - Sometimes information is recored in the configuration log file instead of the workspace log. (especially if
the workspace hasn't been created yet, there isn't one, or it cannot
be created) Check your configuration area for a configuration log
file. (configuration/.log)
Startup - Occasionally problems happen in the system really early before there is a workspace and before there is a configuration area.
This means that there is nowhere to write the log file so information
is written to the console, See the notes below on running with a
console to get these messages.