Knowledgebase

How to Stop and Start MySQL Service in Windows and Linux VPS?

Windows VPS

1. Login to your Windows VPS through Remote Desktop. Please refer to connect VPS using RDP for more details.

Go to Start >>Administrative Tools >>Services.

At Services Window, locate and select MySQL service.

If MySQL service is running, at right hand side you will get following 3 options.

• Stop the service // This option will stop the selected service.
• Pause the service // This option will pause the selected service.
• Restart the service // This option will restart the selected service.

To Stop, Pause or Restart the service, click on the respective option.

If MySQL service is stopped, you will get only option of Start the service as shown in the following image.

By following above steps, you can also stop/start other Windows service.

Linux VPS

In Linux VPS, you can stop/start MySQL service either through SSH or WHM control panel.

Stop/start MySQL service through SSH/Terminal

Connect to your VPS through SSH with root user and type following commands. Please refer to connect VPS using SSH for more details.

If you want to stop/start other Linux VPS services, you can use above commands by placing service name. Following are some of the most common Linux VPS services.

Start/Stop MySQL service through WHM

1. Login to WHM (https://your-IP-address:2087).

Under the Service Configuration section, select Service Manager.

Uncheck the check boxes under mysql and click on Save button. This will stop MySQL service.

To start MySQL service, you just need to check checkboxes under mysql and Save button.

By following the above steps, you can also stop/start other listed services.

Related Articles

You can connect your MySQL with PHP using the below methods. Method 1 — PHP extension(mysqli).

Database clone is a process to create a separate copy of the database. You can also use it as.

This article will assist you to enable remote access to MySQL server through Windows command.

Problem Statement Recently one of our customers was unable to connect to Collection Max and.

By default in the windows server, the strict mode will be enabled on MySQL. Please refer to the.

Chapter 2 Starting the Server for the First Time on Windows

This section gives a general overview of starting the MySQL server. The following sections provide more specific information for starting the MySQL server from the command line or as a Windows service.

The information here applies primarily if you installed MySQL using the noinstall version, or if you wish to configure and test MySQL manually rather than with the MySQL Installer.

The examples in these sections assume that MySQL is installed under the default location of C:\Program Files\MySQL\MySQL Server 8.0 . Adjust the path names shown in the examples if you have MySQL installed in a different location.

Clients have two options. They can use TCP/IP, or they can use a named pipe if the server supports named-pipe connections.

MySQL for Windows also supports shared-memory connections if the server is started with the shared_memory system variable enabled. Clients can connect through shared memory by using the —protocol=MEMORY option.

For information about which server binary to run, see Selecting a MySQL Server Type.

Testing is best done from a command prompt in a console window (or “ DOS window ” ). In this way you can have the server display status messages in the window where they are easy to see. If something is wrong with your configuration, these messages make it easier for you to identify and fix any problems.

The database must be initialized before MySQL can be started. For additional information about the initialization process, see Initializing the Data Directory.

To start the server, enter this command:

For a server that includes InnoDB support, you should see the messages similar to those following as it starts (the path names and sizes may differ):

When the server finishes its startup sequence, you should see something like this, which indicates that the server is ready to service client connections:

The server continues to write to the console any further diagnostic output it produces. You can open a new console window in which to run client programs.

If you omit the —console option, the server writes diagnostic output to the error log in the data directory ( C:\Program Files\MySQL\MySQL Server 8.0\data by default). The error log is the file with the .err extension, and may be set using the —log-error option.

The initial root account in the MySQL grant tables has no password. After starting the server, you should set up a password for it using the instructions in Securing the Initial MySQL Account.

Stop MySQL service windows

I am developing a website and need to refresh data. Therefore MySQL must be stopped.
How can I stop the service?

When I look at control panel services it is started without stop or restart option.

16 Answers 16

On Windows

If you are using windows Open the Command Prompt and type

To Stop MySQL Service

To Start MySQL Service

On Linux

Fedora / Red Hat also support this:

I know this answer is late but i hope it helps for some one.

You can set its startup type to manual in services.msc. This way it will not start automatically unless required. Simply get the name of the service from services.msc as shown here:

You can create batch files to start and stop the service fairly easily as well. Now use this name in batch files.

And in your stop.bat:

The Top Voted Answer is out of date. I just installed MySQL 5.7 and the service name is now MySQL57 so the new command is

net stop MySQL57

Start Powershell as administrator and run:

Find the service name:

run ‘services.msc’, look for MySQL and click on properties

For Windows there’s a couple of tricks to take care of.

(Assuming you’ve installed MySQL from Oracle’s site but maybe have chosen not to run the service at startup).

To use «mysqld stop» from the command line for WinVista/Win7 you must right click on Start -> All Programs -> Accessories -> Command Prompt -> Run As Administrator

Now that you have local OS admin access you can use «mysqld stop» (which will simply return)

IF YOU SEE THE FOLLOWING YOU ARE TRYING IT WITH A USER/COMMAND PROMPT THAT DOES NOT HAVE THE CORRECT PRIVILEGES:

If mysqld does not appear as a known system command, try adding it to your class path

1. Right click on My Computer
2. Advanced System Settings
3. Environment Variables
4. System variables
5. look for and left click select the variable named path

click on «Edit» and copy out the string to notepad and append at the end the full path to your MySQL bin directory , e.g.

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\Program Files\MySQL\MySQL Server 5.5\bin

Chapter 3 The Server Shutdown Process

The server shutdown process takes place as follows:

The shutdown process is initiated.

This can occur initiated several ways. For example, a user with the SHUTDOWN privilege can execute a mysqladmin shutdown command. mysqladmin can be used on any platform supported by MySQL. Other operating system-specific shutdown initiation methods are possible as well: The server shuts down on Unix when it receives a SIGTERM signal. A server running as a service on Windows shuts down when the services manager tells it to.

The server creates a shutdown thread if necessary.

Depending on how shutdown was initiated, the server might create a thread to handle the shutdown process. If shutdown was requested by a client, a shutdown thread is created. If shutdown is the result of receiving a SIGTERM signal, the signal thread might handle shutdown itself, or it might create a separate thread to do so. If the server tries to create a shutdown thread and cannot (for example, if memory is exhausted), it issues a diagnostic message that appears in the error log:

The server stops accepting new connections.

To prevent new activity from being initiated during shutdown, the server stops accepting new client connections by closing the handlers for the network interfaces to which it normally listens for connections: the TCP/IP port, the Unix socket file, the Windows named pipe, and shared memory on Windows.

The server terminates current activity.

For each thread associated with a client connection, the server breaks the connection to the client and marks the thread as killed. Threads die when they notice that they are so marked. Threads for idle connections die quickly. Threads that currently are processing statements check their state periodically and take longer to die. For additional information about thread termination, see KILL Statement, in particular for the instructions about killed REPAIR TABLE or OPTIMIZE TABLE operations on MyISAM tables.

For threads that have an open transaction, the transaction is rolled back. If a thread is updating a nontransactional table, an operation such as a multiple-row UPDATE or INSERT may leave the table partially updated because the operation can terminate before completion.

If the server is a replication source server, it treats threads associated with currently connected replicas like other client threads. That is, each one is marked as killed and exits when it next checks its state.

If the server is a replica server, it stops the replication I/O and SQL threads, if they are active, before marking client threads as killed. The SQL thread is permitted to finish its current statement (to avoid causing replication problems), and then stops. If the SQL thread is in the middle of a transaction at this point, the server waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement. See also STOP SLAVE | REPLICA Statement. Since nontransactional statements cannot be rolled back, in order to guarantee crash-safe replication, only transactional tables should be used.

To guarantee crash safety on the replica, you must run the replica with —relay-log-recovery enabled.

The server shuts down or closes storage engines.

At this stage, the server flushes the table cache and closes all open tables.

Each storage engine performs any actions necessary for tables that it manages. InnoDB flushes its buffer pool to disk (unless innodb_fast_shutdown is 2), writes the current LSN to the tablespace, and terminates its own internal threads. MyISAM flushes any pending index writes for a table.

The server exits.

To provide information to management processes, the server returns one of the exit codes described in the following list. The phrase in parentheses indicates the action taken by systemd in response to the code, for platforms on which systemd is used to manage the server.

0 = successful termination (no restart done)

1 = unsuccessful termination (no restart done)

2 = unsuccessful termination (restart done)

Stop mysql server windows

The server shutdown process takes place as follows:

The shutdown process is initiated.

This can occur initiated several ways. For example, a user with the SHUTDOWN privilege can execute a mysqladmin shutdown command. mysqladmin can be used on any platform supported by MySQL. Other operating system-specific shutdown initiation methods are possible as well: The server shuts down on Unix when it receives a SIGTERM signal. A server running as a service on Windows shuts down when the services manager tells it to.

The server creates a shutdown thread if necessary.

Depending on how shutdown was initiated, the server might create a thread to handle the shutdown process. If shutdown was requested by a client, a shutdown thread is created. If shutdown is the result of receiving a SIGTERM signal, the signal thread might handle shutdown itself, or it might create a separate thread to do so. If the server tries to create a shutdown thread and cannot (for example, if memory is exhausted), it issues a diagnostic message that appears in the error log:

The server stops accepting new connections.

To prevent new activity from being initiated during shutdown, the server stops accepting new client connections by closing the handlers for the network interfaces to which it normally listens for connections: the TCP/IP port, the Unix socket file, the Windows named pipe, and shared memory on Windows.

The server terminates current activity.

For each thread associated with a client connection, the server breaks the connection to the client and marks the thread as killed. Threads die when they notice that they are so marked. Threads for idle connections die quickly. Threads that currently are processing statements check their state periodically and take longer to die. For additional information about thread termination, see Section 13.7.8.4, “KILL Statement”, in particular for the instructions about killed REPAIR TABLE or OPTIMIZE TABLE operations on MyISAM tables.

For threads that have an open transaction, the transaction is rolled back. If a thread is updating a nontransactional table, an operation such as a multiple-row UPDATE or INSERT may leave the table partially updated because the operation can terminate before completion.

If the server is a replication source server, it treats threads associated with currently connected replicas like other client threads. That is, each one is marked as killed and exits when it next checks its state.

If the server is a replica server, it stops the replication I/O and SQL threads, if they are active, before marking client threads as killed. The SQL thread is permitted to finish its current statement (to avoid causing replication problems), and then stops. If the SQL thread is in the middle of a transaction at this point, the server waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement. See also Section 13.4.2.10, “STOP SLAVE | REPLICA Statement”. Since nontransactional statements cannot be rolled back, in order to guarantee crash-safe replication, only transactional tables should be used.

To guarantee crash safety on the replica, you must run the replica with —relay-log-recovery enabled.

The server shuts down or closes storage engines.

At this stage, the server flushes the table cache and closes all open tables.

Each storage engine performs any actions necessary for tables that it manages. InnoDB flushes its buffer pool to disk (unless innodb_fast_shutdown is 2), writes the current LSN to the tablespace, and terminates its own internal threads. MyISAM flushes any pending index writes for a table.

The server exits.

To provide information to management processes, the server returns one of the exit codes described in the following list. The phrase in parentheses indicates the action taken by systemd in response to the code, for platforms on which systemd is used to manage the server.

0 = successful termination (no restart done)

1 = unsuccessful termination (no restart done)

2 = unsuccessful termination (restart done)