i am running mysql server 5.5 i haven't installed it as a service.
I am starting mysql from command line by typing mysqld.
Mysql is successfully started i can query anything now, But if i close this commandline window the mysql connection is also closed.
Why is this so ?
I want it run mysql even after the console is closed without installing it as a service. Is it possible to do so or i have to keep that console window open to do all the task.
How can i solve this problem.
Please help.
If you are running a linux distro (e.g. ubuntu), then start it in a different shell (e.g. CTRL-ALT-F2) and move back to the shell you were already using.
If you are running from Windows, then why not start the GUI version of MYSQL server instead ?
In newer version of windows the (emulated) cmd is sandboxed which means that everything is discarded after closing the window, unless of course it is a service which will be hand by Windows.
Related
I am having trouble starting up a server through MySQL Workbench. From the navigator pane on the left side of Instance -> Start/Shutdown, I tried the "Start Server" button at which point the server will look like it will try to start. The workbench will get hung up at this point and indefinitely not respond with a "thinking" mouse icon while in the workbench app.
This is my first time learning to use MySQL workbench, which I want to say that when I initially installed MySQL Workbench a server did start after installation and worked fine. It was after restarting my computer and checking on the workbench the next day (today) that the server no longer runs. I'm not seeing any MySQL references in my Services (services.msc) that might relate to starting up but that might also be because I did not install as a Windows Service. My original troubleshooting was in trying to establish a connection, which I realized it was because the server wasn't running. Could someone help me understand why the server isn't starting? Or would it be recommended to install the workbench as a Windows Service to avoid the issue I'm having?
Screenshot of the MySQL Workbench window where the application will get hung up when starting the server.
Current setup: Personal workstation, Windows 10 (64 bit), MySQL Workbench 8.0 (version 8.0.29 build 1751076 CE 64 bits). I do not plan on running the server 24/7 since this is my personal workstation.
Right-click on My Computer
Select Manage
Select Services under Servies and applications
Find MySQL among the services and open it.
Choose Automatic as a start option.
Click on start.
Press Apply & OK then exit.
It is not necessary, but I still recommend restarting PC.
The solution below fixed my issue. I definitely recommend installing MySQL Server as a windows service and making sure uncheck mark the box that says to start when Windows starts unless you plan to have your computer as a dedicated server.
Source from #Lazycoder_007
This solution uses the window's mysql installer which you have used to
install your MySQL.
Start your windows mysql installer. For me it was
"mysql-installer-community-8.0.20.0"
Then remove/uninstall the SQL
Server and remove all configurations
Manually delete the SQL Server
folder from "C:\Program Files\MySQL\MySQL Server 8.0."
Start your
mysql installer again and install the SQL Server again
You can check
now that the MySqL Server has started.
I have used mySQL for a project in the past, and haven't used it for months. However, when i check my task manager 'mysql' is using about 100MB of RAM. This happens every times i reboot. Why is my sql running, or using memory when i don't need it. Is a server running in the background that i have to disable? For context i was using my SQL Workbench 8.0 when working on my project.
Open a command prompt window cmd.exe
Stop MySQL service: net stop mysql57 (or net stop mysql)
Go to your mysql server installation path, in my case: cd "C:\Program Files\MySQL\MySQL Server 5.7\bin\"
Execute mysqld.exe --remove
This will remove the MySQL Service.
Note that You may need an elevated command line prompt, for that press WIN-X select Command Prompt (Admin)
Yes, MySQL Server service would be constantly running in the background, if (because) this service's startup type was set on an "automatic start when computer starts" mode during the installation of MySQL Workbench. The comment by #Alejandro offers the finest explanation.
(below steps I had tried for MySQL 8.0.30 version, however shall work with nearby versions as well; as steps to stop the service might be generic.)
In Windows 10, to stop the MySQL Server's service, OR, change the startup-type setting of MySQL Server.
Open Windows Services panel via the Start menu, OR, Win+R -> type services.msc, do Enter.
Different Windows OS's services would be listed here, alphabetically.
Find the MySQL Service. For MySQL 8 versions, it's often by default name - MySQL80, unless you had named it by a custom name during installation.
Click STOP, to stop the service.
On the other hand, you may choose your desired Startup type. By default, you'll find it on Automatic type.
If you want to keep Manual type, make sure to start the service by coming at this Services wizard, before using MySQL Workbench. Otherwise, the workbench won't be able to recognize/find the server.
While installing the MYSQL Server, this check box is by default checked (shown in the picture). If you uncheck this, then you need to start your MYSQL Server manually.
I just installed Laragon but when it wants to start its services, it "freezes" when mySQL have to be launched, then shows me that message :
mysqld.exe - Application Error
This application was unable to start correctly (0xc000007b). Click OK to close the application.
After that, Laragon's window writes "initialize data..." then does not change until I stop all services.
I wanted to check the log files but... zero log. So impossible to have some details...
I've tried to uninstall and reinstall.
I've tried another version of mySQL.
None of them works. WAMP is also installed on my computer, but I don't really want to uninstall it (and I don't think that's problem since I have both at work).
I think MySQL 5.7 is not compatible with your OS.
You can try two options:
Copy your MySQL in WAMP to laragon\bin\mysql\
Use MariaDB
I used to work with XAMPP to build PHP applications. Once I tried Zend engine and uninstalled it. After that, MySQL in XAMPP is not working. It is giving "Terminating worker thread 1" error.
When I check ports,
MySQL has status Service: MySQL_ZendServer51.
Pleas help me how to reassign it back to XAMPP? I have reinstalled XAMPP several times. But no use.
Thanks,
Raj
First you should delete the old mysql service.
Assuming you have Vista or Windows 7:
Go to Start and type cmd.exe in the search field and hit Ctrl+Alt+Enter. This will start the command line as Administrator.
Now you can type sc.exe delete MySQL_ZendServer51 to remove the service.
Now you can start your XAMPP Control Panel and uncheck the "svc" checkbox next to MySQL (if it's not already)
Next check it on again (this will install the proper mysql service)
And make sure you don't have to server running (which could be possible, that Zend installed it's own mysql but for some reason didn't removed it?)
I just went here: c:\xampp\mysql\bin\mysqld.exe
And opened the document and MySQL Started without problem.
I am trying to run MySql 5.1 on Windows 7 Home Premium 64 bit. I have downloaded the MSI installer from the MYSql website and installed it. The installation is successful, but the service does not start.
If I try to run MySql manually using the mysqld executable, it crashes immediately on running (error: mysqld.exe has stopped working).
Earlier mysql was running on the machine, but I had some problem with it (wasn't executing big queries) and installed it again which somehow broke the program. I had installed it to work as a service which started giving me this isse, and now it won't work even if I don't install it as a service.
I have tried removing the mysql folder and re-installing. Is there somewhere else where Mysql saves configuration info or other data?
Has anyone else found this problem and solved it?
How can I find out why the process is failing to run?
Or you can try and run the mysqld.exe as administrator.
See the Debugging a MySQL Server in your MySQL reference manual.
download the noinstall (zip archive) version of MySQL corresponding exactly to the version that is already installed on your system
extract the .pdb symbols files to your existing MySQL installation's bin directory
start Dr. Watson
start mysqld-debug in standalone mode
capture the list of all moduled (i.e. loaded DLLs) with their full path from DrWatson
capture the stack trace from DrWatson
examine the MySQL log files (including mysqld.trace) to see what went on immediately prior to the crash