I followed https://flaviocopes.com/mysql-how-to-install/ to install MySQL on my MacBook running Big Sur.
I'm attempting to create a new connection and I click the button labelled "Configure Server Management" and before I can complete the installation I'm met with the following error:
Check if ~/sandboxes/msb_|Enter version here|/my.sandbox.cnf can be accessed
Operation failed: File ~/sandboxes/msb_|Enter version here|/my.sandbox.cnf doesn't exist
https://imgur.com/a/hhBKsGl
Couldn't find a solve for this anywhere.
On macOS MySQL doesn't use a configuration file by default. It runs with default values. So, for the connection setup part you can just ignore the error and skip over that page.
You can later create a config file in the admin section of your connection and once that has been stored update the management section in the connections editor with the correct path.
Related
I just installed MySQL using the community installer in hopes of running a server and creating a database for use in my C++ program. I installed the Server, Workbench, Shell, Router, and Connector/C++ before running the Workbench. Everything appeared to be working properly. The server was running and I was able to connect to it in my C++ program, so I started to create my database, when the power suddenly went out before I could finish.
Once the power came back on and my PC rebooted, I reopened the MySQL Workbench to find that I was unable to start the server. I clicked the 'Start Server' button several times, but was met with the error "Could not start server: argument 2: <class 'TypeError'>: wrong type".
I tried uninstalling and reinstalling everything, but when I reopened the MySQL Workbench after the installation was finished, I was met with the same error. Does anyone know what could have possibly happened?
EDIT: After uninstalling everything and deleting every trace of MySQL from my computer, I was able to reinstall everything and get the server running again. However now I'm getting the same error when I try to STOP the server: "Could not stop server: argument 2: <class 'TypeError'>: wrong type". What is going on????
I have the same issue and I've installed the developers default version of the MySQL-Workbench with the installer. I recently updated my hardware and reinstalled Windows 10, maybe it's a bug of Windows 20H2 or of the Workbench itself?
I found a workaround: Use the CMD or the Powershell to start or stop the MySQL-Service of the server. In my case, it has the name MySQL80. Take a look in your services of windows when the commands below are not working.
Use net start MySQL80 to start the server.
Use net stop MySQL80 to stop the server.
Remember to open the CMD or the Powershell as Administrator. I think this issue is a bug of the workbench itself because the service is start and stopable with the command line.
The first thing to try is to run mysqld --console from the MySQL server bin folder. That should give you more specific error messages.
In my case, the data folder was missing. I needed to run one of the mysqld --initialize... commands; see https://dev.mysql.com/doc/refman/8.0/en/data-directory-initialization.html. On Windows, running mysqld --initialize... --console helps to see what server is doing.
Once that's done, you can run mysqld --console again to see if it starts successfully.
I solved this problem as follows. currently my.ini file encoding is UTF-8. you must change to ANSI.
I've done numerous suggestions and none work. Except this one:
Download and run the latest MySQL Installer.
A window will appear showing your installed services:
MySQL Server
MySQL Workbench
MySQL Shell
etc.
Click "reconfigure" on the MySQL Server and set up the server as you did previously.
My specific server setup was:
Type and Networking: leave as default
Authentication Method: (RECCOMENDED)
Accounts and Roles: Enter and check mysql password
Windows Service: Uncheck 'configure as a service'
Apply configuration: Execute
Server should be up and running.
in my case I had solve this way
Go to RUN----->Services.msc----->MYSQL80---->start server
hope this way problem will solved.
On my Windows installation the account the service runs under did not have (security) permissions to the non-existing data directory. After creating the data directory which was "Program Files\MySQL\MySQL Server 8.0\data" and setting permissions everything worked with a "net start mysql80".
Here are the steps I took to resolve my MySQL Workbench 8.0.23 issue
that resulted in an inability to start & stop the MySQL server process (mysqld)
from MySQL Workbench (O/S=Windows only answer)...
Close MySQL Workbench
In C:\Users<Your account>\AppData\Roaming\MySQL\Workbench\serverinstances.xml:
Replaced:
sc start MySQL80
sc stop MySQL80
With:
net start MySQL80
net stop MySQL80
Notes:
My mysqld service was installed w/ the name='MySQL80', replace/match this value to your actual service name.
My mysqld service was installed using a 'Network Service' account, verify that your service is also running as a network service before using the 'net' commands
Setup MySQLWorkbench CE 8.0 executable to 'Run As Administrator' so that the commands to start and stop the service run as an administrator:
In File Explorer find the MySQLWorkbench.exe executable:
E.g: C:\Program Files\MySQL\MySQL Workbench 8.0\MySQLWorkbench.exe
In File Explorer, Select the exe, Right click on the exe, select 'Properties', select
'Compatibility' tab: specify 'Run This Program As An Administrator'
Start MySQL Workbench
Attempt to start or stop the MySql server process (mysqld)
Notes:
O/S = Windows 10 specific
MySQL & MySQL Workbench were installed via the MySQL CE 8.0.23 installer
Installed MySQL 8.0.23 as an upgrade from 5.7 to 8.0.23
If this error while starting/connecting the server from Workbench then you need to Go Start->MYsql workbench Installation Click.
Open and reconfigure the MySQL server with port number and Create Root user Password.
Finish this Re-configuration then open workbench. Provide the Port number and Credentials and connect to DB.
In window you may use task manager
just open task manager by search "task manager" in window search
Go to service and find Mysql (name depending on the name saved when initializing mysql server at first time)
Right click it and click start to start server or stop to stop server
I have managed to successfully connect to a docker instance running MySQL via the mysql command line utility. However, I am struggling to do so via DataGrip application from JetBrains.
My mysql cli command is as follows:
mysql -h127.0.0.1 --port=8181 -uroot
The connection string that is generated in DataGrip is:
jdbc:mysql://127.0.0.1:8181
The error I am getting from DataGrip interface is:
[08001] Could not create connection to database server. Attempted reconnect 3 times. Giving up.
Is there anything that need to change in DataGrip that I am missing. I have read that the connection has to also be done via TCP. Not sure how to check that DataGrip is doing that.
Update: I eventually found the problem was the docker container I was using. It seems DataGrip is not able to connect to version 8.0.1 (mysql:8.0.1) mysql docker container. I tested using version 5.7 of the container and could successfully connect.
I was having an issue connecting MySQL 8.0.3 using DataGrip. You need to download the JDBC driver from Oracle website. Select Developer Releases (Since this is an unstable version). The 8.0.8 version worked for me. Download and save in a project folder or something similar on your computer. You will gonna need it later.
Go to DataGrip: File > DataSources. Click on the + and select Driver:
Screenshot of the Step above
On the section Driver Files > Additional files click on the + and select the jar file you just downloaded
After that on the Class dropdown select com.mysql.jdbc.Driver
Mark Dialect as MySQL
On the section URL templates, put the Name as default and Template as jdbc:mysql://{host::localhost}?[:{port::3306}][/{database}?][\?<&,user={user},password={password},{:identifier}={:identifier}>]
Click on apply
Done!
Screenshot of MySQL 8.0.3 running on Datagrip
Add a new datasource using the new driver.
If you find the following error:
[01S00] The server time zone value 'PDT' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support
You can do a temporary fix going to the Advanced tab and setting the serverTimezone variable for UTC as an example.
There are no *.jar-files anymore. Only *.deb-packages for my OS on the Oracle site https://dev.mysql.com/downloads/connector/j/5.1.html
So I selected driver Amazon Aurora MySQL for my MySQL 8.0.3 in docker.
It works!
My MySQL Workbench is not connecting to my local host, and I cannot figure out why exactly it is reacting like this. It just started doing this one day, and randomly it will give me access although it says it is still "unknown", but I am tired of this and would like to fix it.
Since this website reqires that I have a "10" reputation to post images, I will have to describe it.
On the Startup/Shutdown tab in the administration page, it says:
The database server instance is unknown. --The "Start Server" button is faded out so that I cannot click it.
Startup Message Log
2013-07-11 08:57:51 - Workbench will use cmd shell commands to start/stop this instance
2013-07-11 08:57:51 - Status check of service 'MySQL' returned error: Not found
2013-07-11 08:57:51 - Status check of service 'MySQL' returned error: Not found
2013-07-11 09:00:55 - Status check of service 'MySQL' returned error: Not found
2013-07-11 09:00:55 - Status check of service 'MySQL' returned error: Not found
2013-07-11 09:02:01 - Status check of service 'MySQL' returned error: Not found
Then on the server status tab in the administration page, it says:
Name: mysqld#localhost
host: localhost
server:unknown
status: unknown
Connection
There is no connection to the MySQL server. This functionality requires an established connection to a running MySQL server to work.
If anyone can help out, that would be great!
Thanks
I had this problem on my Windows 8.1 machine and it turned out to be problems with the file permissions.
To repair it I went into the folder at "C:\Program Files\MySQL\MySQL Server 5.6" and right clicked on the "data" folder and selected properties. Clicked the security tab and clicked edit. From there click the ADD button then the ADVANCED button and finally the FIND NOW button. In mine I added users, administrators, and "ALL APPLICATION PACKAGES". I granted full control to the users that were already listed for the data folder and the users, administrators, and ALL APPLICATION PACKAGES.
After the permissions were repaired I opened a command prompt as administrator and changed to the "C:\Program Files\MySQL\MySQL Server 5.6\bin" directory cd "C:\Program Files\MySQL\MySQL Server 5.6\bin". From there you can execute mysqld --install which installs the MySQL service.
More information about installing the mysql service on windows can be found at http://dev.mysql.com/doc/refman/5.0/en/windows-start-service.html
[edit] Please note that if you are using a different version of MySQL than the path to the MySQL data directory and bin directory may be different on your windows machine.
The error message says it: the service with the name MySQL cannot be found. So probably your MySQL service has a different name? Do you have a service at all? Starting mysql manually from the bin folder is just that: manual. There is no service involved, hence WB cannot manipulate the run state.
When you install MySQL with the MySQL installer you have everything in place within a couple minutes and it works right from the start.
So first check if you have a service running for your MySQL server and stop starting it manually. If there's a service take its name and enter it in the Windows Service Name field of the configuration manager:
Note that MySQL Workbench can manage your server only if it is installed as a Windows service.
I had this problem on my Windows 8.1, and I solved it updating my workbench to Version6 with "mysql-installer-web-community-5.6.16.0.msi" from the official page of mysql
I have found reinstalling all MySQL products a better alternative, because some of the solutions on the internet will make another instance of your mysql server along with mysql56, which might mess things up for a beginner.
Remember to keep database files and configuration undeleted during the reinstallation.
I had problem on MAC.
Please ensure you have installed mysql and its running. Because installing only workbench app, will not install mysql service. First install mysql and run the service.
In my case, I tried with brew
brew install mysql // installing mysql
brew services restart mysql // restart service after installing
mysql --version // check version
Im trying to install ProcessMaker using my WAMP server (Local Machine)
I went through all the steps sucessfully.
But when installing it it fails with a error message saying "Database is not empty" for wf_workflow database and rb_workflow databases
In the installation test page those two fields are with red sign.
Plz help me with this as i am new to this software.
That error usually raises when you are trying to install ProcessMaker in a server that has another instance of it. You have two options and for both on that installation screen you must activate "advanced" settings that will allow you to overwrite existing installation or rename workspace and database names.
I am getting the following error when I try to configure MySQL instance, could any one help out to resolve this error.
I am using Windows XP SP2.
If you reinstall or upgrade MySQL without first stopping and removing the existing MySQL service and install MySQL using the MySQL Configuration Wizard, you may see this error:
Error: Cannot create Windows service for MySql. Error: 0
This occurs when the Configuration Wizard tries to install the service and finds an existing service with the same name.
One solution to this problem is to choose a service name other than mysql when using the configuration wizard. This enables the new service to be installed correctly, but leaves the outdated service in place. Although this is harmless, it is best to remove old services that are no longer in use.
To permanently remove the old mysql service, execute the following command as a user with administrative privileges, on the command-line:
shell> sc delete mysql
[SC] DeleteService SUCCESS
If the sc utility is not available for your version of Windows, download the delsrv utility from http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/delsrv-o.asp and use the delsrv mysql syntax.
-- http://dev.mysql.com/doc/refman/5.0/en/windows-troubleshooting.html
Usually when the service doesn't manage to start, there will be more detailed information about what went wrong somewhere:
In mySQL's your_hostname_here.err file
In the system's error log (In english-language Windows, it's called event log I think)
you need to look there for the reason.