Xampp не запускается mysql windows 10

Sometimes MySQL may fail to start in XAMPP, which can be a frustrating experience for users. If you are facing this issue, don’t worry, as there are several steps you can take to fix MySQL not starting in XAMPP on Windows. xampp MySQL not starting windows 11/10; In this tutorial, you will learn how to fix MySQL not starting xampp control panel in windows 11/10.

When you start mysql in xampp you will see some errors. Which is visible in the image given below. But your mysql server will not start in xampp windows.So it means that your mysql server has become corrupt. and it needs to be repaired.

This has happened to us on some commits with Windows XAMPP, which appears to be caused by stopping the MySQL server in the control panel.

This was our error log when we tried to start the MySQL server:

3:43:26 PM  [mysql]   Attempting to start MySQL app...
3:43:26 PM  [mysql]   Status change detected: running
3:43:28 PM  [mysql]   Status change detected: stopped
3:43:28 PM  [mysql]   Error: MySQL shutdown unexpectedly.
3:43:28 PM  [mysql]   This may be due to a blocked port, missing dependencies, 
3:43:28 PM  [mysql]   improper privileges, a crash, or a shutdown by another method.
3:43:28 PM  [mysql]   Press the Logs button to view error logs and check
3:43:28 PM  [mysql]   the Windows Event Viewer for more clues
3:43:28 PM  [mysql]   If you need more help, copy and post this
3:43:28 PM  [mysql]   entire log window on the forums

Follow the below given easy steps to fix/resolve MySQL server not starting in XAMPP windows. And your Mysql server will start in the xampp windows:

• Step 1 – Visit Xampp/mysql Directory
• Step 2 – Make Backup Directory
• Step 3 – Copy MySQL Directory Data
• Step 4 – Paste MySQL Data in Directory
• Step 5 – Copy ibdata1 Directory Data
• Step 6 – Restart MySQL Server In Xampp

Step 1 – Visit Xampp/mysql Directory

Navigate to your XAMPP MySQL directory (C:\xampp\mysql).

Step 2 – Make Backup Directory

Make a new folder called FIX_BACKUP.

Step 3 – Copy MySQL Directory Data

Copy C:\xampp\mysql\backup and C:\xampp\mysql\data into C:\xampp\mysql\FIX_BACKUP.

Step 4 – Paste MySQL Data in Directory

Paste the contents of C:\xampp\mysql\backup into C:\xampp\mysql\data overwriting all the files.

Step 5 – Copy ibdata1 Directory Data

Finally copy the ibdata1 file from C:\xampp\mysql\FIX_BACKUP\data into C:\xampp\mysql\data overwriting the file.

Step 6 – Restart MySQL Server In Xampp

Now restart MySQL server in xampp. So, Your MySQL server should now start in the XAMPP control panel.

If the above steps do not resolve the issue, it may be necessary to reinstall XAMPP. This will ensure that all components are installed correctly and that there are no missing or corrupt files. Follow these steps to reinstall XAMPP:

1. Uninstall XAMPP from your system.
2. Download the latest version of XAMPP from the official website.
3. Install XAMPP on your system, making sure to select all the required components.
4. Start XAMPP and check if MySQL is running.

Conclusion

MySQL not starting in XAMPP can be a frustrating problem, but fortunately, it can be fixed by following the steps above. By checking the XAMPP control panel, looking for conflicting ports, checking the MySQL error log, and reinstalling XAMPP, you can get MySQL up and running in XAMPP in no time.

Recommended Tutorials

Почему то перестал работать mySQL, сегодня же запускал все было хорошо, может быть кто-нибудь сталкивался? что можно сделать?

18:11:56  [mysql] 	Error: MySQL shutdown unexpectedly.
18:11:56  [mysql] 	This may be due to a blocked port, missing dependencies, 
18:11:56  [mysql] 	improper privileges, a crash, or a shutdown by another method.
18:11:56  [mysql] 	Press the Logs button to view error logs and check
18:11:56  [mysql] 	the Windows Event Viewer for more clues
18:11:56  [mysql] 	If you need more help, copy and post this
18:11:56  [mysql] 	entire log window on the forums

InnoDB: using atomic writes.
2020-04-03 17:41:35 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-04-03 17:41:35 0 [Note] InnoDB: Uses event mutexes
2020-04-03 17:41:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-04-03 17:41:35 0 [Note] InnoDB: Number of pools: 1
2020-04-03 17:41:35 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-04-03 17:41:35 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-04-03 17:41:35 0 [Note] InnoDB: Completed initialization of buffer pool
2020-04-03 17:41:35 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-04-03 17:41:35 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-04-03 17:41:35 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-04-03 17:41:35 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2020-04-03 17:41:35 0 [Note] InnoDB: 10.4.11 started; log sequence number 10282705; transaction id 18356
2020-04-03 17:41:35 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2020-04-03 17:41:35 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-04-03 17:41:35 0 [Note] Server socket created on IP: '::'.

XAMPP is a great tool for web developers who need to host websites locally on their own computers. Unfortunately, because it uses ports and services that are commonly used by other applications, conflicts can happen, causing certain applications on XAMPP to be unable to run.

In this article, we will be exploring what you can do if XAMPP’s Apache service does not run on Windows.

Note that if you are using XAMPP on macOS, please refer to the following article instead.

If you prefer to watch a video as opposed to reading, we have a video on this as well:

1. The problem
2. Possible causes and fixes
   1. Port 3306 is already used by another process
   2. Changing the port used by XAMPP
   3. MySQL’s data has been corrupted
3. Unable to access phpMyAdmin
4. Conclusion

1. The problem

If your MySQL module’s status changes to back to stopped every time you try to start it, you are strongly encouraged to read on further to solve this problem.

Below is a transcription of the error log shown on XAMPP when MySQL fails to start:

[mysql] Attempting to start MySQL service...
[mysql] Status change detected: running
[mysql] Status change detected: stopped
[mysql] Error: MySQL shutdown unexpectedly
[mysql] This may be due to a blocked port, missing dependencies,
[mysql] improper priviliges, a crash, or a shutdown by another method.

2. Possible causes and fixes

Below are some common causes that prevent XAMPP’s MySQL module from starting.

a. Port 3306 is used by another process

The most likely reason that XAMPP’s MySQL service is unable to start is because port 3306 is already used by a different program that is currently running on your computer. By default, XAMPP’s MySQL service binds to port 3306 when started, and it can only do so if another program is not already using it.

To ascertain whether this is the case, you can click on the Netstat button to open up a window with a list of all the ports that are being used on your computer currently. If port 3306 is in the list when you haven’t started MySQL on XAMPP, this means that another program is using it.

To remedy this, you will need to find the process that is using port 3306 and end the process. In the example above, a process called mysqld.exe is using port 3306. To stop it, I will have to use Ctrl + Alt + Delete to open up the Task Manager, then find and end the mysqld.exe process.

Once this is done, you can try starting MySQL on XAMPP again. Depending on the program that was occupying port 3306, this might or might not work. If it doesn’t work, you will have to find the program that was creating the process and uninstall it. In most cases, this should be another installation of MySQL on your computer, such as:

• MySQL Workbench
• MySQL Community Server

…or some other variation of MySQL, since it is one of the few programs that use port 3306.

After uninstalling the other program(s), remember to restart your computer before trying to start MySQL again.

b. Changing the port used by XAMPP MySQL

If you don’t want to uninstall the program that is using port 3306, or if you can’t find the process using the instructions above, you can also configure XAMPP MySQL to use a different port. Do note that if another MySQL program is using port 3306, there is a chance that this doesn’t work, as 2 seperate installations of MySQL can interfere with each other.

Regardless, below are the steps to change the port of XAMPP’s MySQL:

1. In the XAMPP control panel, click on the Config button of the MySQL module.
2. In the popped window, select my.ini.

1. Inside the file, go down and find the section that contains the following line: # The MySQL server. Below this line, you should find the port number, which says port=3306 by default.
2. Change to a different port. You can use any unused port on your computer between 1 to 65535, but I usually use port 3307.
3. Save the changes to the file, and try to start MySQL on XAMPP again.

---

Article continues after the advertisement:

---

Below is a snapshot of my my.cnf file, with the part that you need to change highlighted:

my.cnf

# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# You can copy this file to
# C:/xampp/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is C:/xampp/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
# password       = your_password 
port=3306
socket="C:/xampp/mysql/mysql.sock"


# Here follows entries for some specific programs 

# The MySQL server
default-character-set=utf8mb4
[mysqld]
port=33063307
socket="C:/xampp/mysql/mysql.sock"
basedir="C:/xampp/mysql"
tmpdir="C:/xampp/tmp"
datadir="C:/xampp/mysql/data"
pid_file="mysql.pid"
# enable-named-pipe
key_buffer=16M
max_allowed_packet=1M
sort_buffer_size=512K
net_buffer_length=8K
read_buffer_size=256K
read_rnd_buffer_size=512K
myisam_sort_buffer_size=8M
log_error="mysql_error.log"

# Change here for bind listening
# bind-address="127.0.0.1" 
# bind-address = ::1          # for ipv6

# Where do all the plugins live
plugin_dir="C:/xampp/mysql/lib/plugin/"

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
# commented in by lampp security
#skip-networking
#skip-federated

# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id	=1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin


# Point the following paths to different dedicated disks
#tmpdir = "C:/xampp/tmp"
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir="C:/xampp/mysql/data"
innodb_data_file_path=ibdata1:10M:autoextend
innodb_log_group_home_dir="C:/xampp/mysql/data"
#innodb_log_arch_dir = "C:/xampp/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size=16M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size=5M
innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
innodb_lock_wait_timeout=50

## UTF 8 Settings
#init-connect=\'SET NAMES utf8\'
#collation_server=utf8_unicode_ci
#character_set_server=utf8
#skip-character-set-client-handshake
#character_sets-dir="C:/xampp/mysql/share/charsets"
sql_mode=NO_ZERO_IN_DATE,NO_ZERO_DATE,NO_ENGINE_SUBSTITUTION
log_bin_trust_function_creators=1

character-set-server=utf8mb4
collation-server=utf8mb4_general_ci
[mysqldump]
max_allowed_packet=16M

[mysql]
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer=20M
sort_buffer_size=20M
read_buffer=2M
write_buffer=2M

[myisamchk]
key_buffer=20M
sort_buffer_size=20M
read_buffer=2M
write_buffer=2M

[mysqlhotcopy]

c. MySQL’s data has been corrupted

If you have had multiple copies of MySQL installed on your device at one point, or had a separate installation of XAMPP, it is possible that the data in your current installation might have been corrupted. In such a scenario, you can try:

1. Ensuring that all other installations of MySQL are removed on your computer, then uninstalling and reinstalling XAMPP, or;
2. Restoring your existing XAMPP’s MySQL installation with backup data.

If you would like to try option B before reinstalling XAMPP, you can follow the steps below:

1. Go to your XAMPP MySQL directory. By default, it is located under Local Disk → XAMPP → MySQL (e.g. if you installed it under the default C-drive, you will find the folder in C:\xampp\mysql). Here you will be seeing different folders — the ones that we need to use are the data and backup folders
2. Rename the data folder to data_old.
3. Create a new folder with the name data. This is the new folder that MySQL will use to replace the old one. Now, we need to fill this folder with certain files.
4. Go to the backup folder and copy all the files inside it. Paste them into the new data folder.
5. Now, we need to paste databases into our new data folder. In order to do so, inside the data_old folder, copy the mysQL folder, as well as all the folders under the phpmyadmin folder. If you have only one folder, it is totally okay, just make sure you paste it. There is NO need to copy the performance_schema and phpmyadmin folders.
6. Last but not least, we need to copy the ibdata1 file. Go to your data_old folder, find the ibdata1 file, and past it into the data folder.

3. Unable to access phpMyAdmin

There can also be cases where you are able to start MySQL on XAMPP, but are unable to access the http://localhost/phpmyadmin URL. This can be caused by a multitude of reasons, and we explore this in a separate article:

4. Conclusion

As with the other articles on the blog, we’d love if you leave a comment below, especially if you:

1. Find any errors in this article.
2. Find a problem causing this issue that is not described in this article.

We will periodically upload this article with new solutions and issues that we find, and we will credit you if you share your issues and / or solutions! Your comments will add to the information that is already here, and help other future readers!

---

Article continues after the advertisement:

---