Error mysql shutdown unexpectedly xampp как исправить

If you use a local development environment, you may run into problems that are similar to those on a live server. In some cases, your WordPress website may be unable to connect with its database because MySQL isn’t running or it shut down unexpectedly.

Depending on which local environment you use, the process of troubleshooting your MySQL database might vary a bit. With XAMPP, the process is remarkably straightforward since you get access to a control panel instead of having to rely on the command line only.

In this article, we’ll explain what XAMPP is and what the “MySQL shutdown unexpectedly” error means. Then we’ll walk you through three methods you can use to fix it. Let’s get to it!

An Introduction to XAMPP

XAMPP is a free, PHP development environment that you can use for Windows, macOS, or Linux. It is a collection of software that enables you to host websites locally by mimicking the functions of a live server:

Using XAMPP, you can install all the software you need to run WordPress locally using a single bundle, rather than setting up each element individually. Development environments differ in what software they bundle.

With XAMPP, the components that you get include:

• Apache: This is arguably the most popular web server software in the world, and it enables you to host sites.
• MariaDB: This open-source database software enables you to manage databases.
• PHP: WordPress is built on PHP, which means you need a PHP install to run the Content Management System (CMS).
• Perl: Although WordPress doesn’t use the Perl programming language, it comes as part of the XAMPP stack by default.

On top of setting up the software you need to run WordPress, XAMPP provides you with a simple control panel:

This enables you to access logs for each of XAMPP’s components. It includes an overview log that shows you everything that’s happening in the background of your environment.

However, using a local development distribution doesn’t mean your server isn’t susceptible to errors. In some cases, the software components may malfunction, such as with the XAMPP error “MySQL shutdown unexpectedly”.

What Is the XAMPP Error “MySQL Shutdown Unexpectedly”?

As the name of the error implies, this is the message you’ll see if the MySQL software on your environment shuts down or ceases to function unexpectedly:

We say “unexpectedly”, because you can manually shut down the MySQL database software at any point. That also happens when you restart your server.

However, when the software is shut down, your website won’t be able to connect to its database. In other words, WordPress won’t work.

As you can see in the above image, XAMPP provides you with advice on troubleshooting the “MySQL shutdown unexpectedly error” right within its events log. In the next section, we’ll go into more detail on the various ways you can use to fix this issue.

How to Fix the XAMPP Error “MySQL Shutdown Unexpectedly” (3 Methods)?

Typically, fixing the XAMPP error “MySQL shutdown unexpectedly” is quick and easy. Below, we’ll walk you through three fixes, starting with the simplest.

1. Run XAMPP Using Administrator Privileges

Often, XAMPP produces errors when you don’t run the software using administrator privileges. This is because its components may not be able to function or configure properly at lower permission levels.

If you’re unsure whether that’s the case with your setup, we recommend that you close XAMPP altogether, and then restart the environment as an administrator. To do so in Windows, find the folder where you installed XAMPP and locate the xampp-control file. Next, right-click on that file and select Run as administrator:

If you’re a macOS user, you can right-click on the folder, and then select Get Info. In the pop-up window that opens, navigate to the Sharing & Permissions section, click on the padlock icon, and enter your administrator password. Change the Read & Write permission settings to Everyone.

Once XAMPP is up and each of its components is running, MySQL should function correctly. That means your database will be accessible.

2. Restore Your Database Backup

If restarting XAMPP with administrator privileges doesn’t solve the problem with your database, the next step is to restore its backup. XAMPP automatically creates backups for your environment’s software, which you can access within the folder where you installed it.

By default, your XAMPP MySQL backup files should be under Local Disk > XAMPP > MySQL. Inside that directory, you’ll see several folders, two of which are called data and backup:

The data folder includes all of the files that your database uses. The backup folder contains a single recent copy of your MySQL.

You can make a backup by clicking on the Stop button to the right of the MySQL option on the main menu:

Once you stop MySQL, return to XAMPP’s MySQL folder and follow these steps to restore the MySQL backup:

1. Make a copy of the data folder.
2. Rename this new folder copy to something like data-old. This will be your backup.
3. Copy the contents of the backup folder into the data folder.

That’s it! To play it safe, though, we strongly recommend that you keep the data-old folder around until you make sure everything is working properly.

At this stage, you can return to the XAMPP control panel to restart MySQL, which should be running correctly now.

3. Change Your MySQL Port

One of the most common causes of the XAMPP error “MySQL shutdown unexpectedly” is another software using the port assigned to MySQL. By default, it tends to be 3306. To be certain, you can select the Netstat module from XAMPP’s control panel, right above the Shell tool:

Netstat is a command line tool that can show you active connections on your network, including which ports they’re using. Once you initialize Netstat, you’ll be able to see what port each tool in your stack is using, including MySQL.

If a conflict with that port caused the shutdown, restoring a backup or running MySQL with administrator privileges won’t make a difference. The only way to solve this issue is to change the port that MySQL uses. Thanks to Netstat, you can see what that port is and which other ones are in use.

To do so, go ahead and stop the service, using the same process we showed you in the last section. Next, click on the Config button next to MySQLon XAMPP’s main menu, and then select the my.ini option:

The my.ini file contains the MySQL configuration settings. After you click on it, XAMPP will open the file using your default text editor. Once you’re in, look for the line that reads Port, which specifies the port number that MySQL uses.

Here, you can change that port number to another option that you know other programs aren’t using. In most cases, we recommend using 3307, which should be available. Save your changes and close the my.ini file.

You can then use the XAMPP control panel to restart MySQL. Hopefully, your database is now working as it should. If for some reason, XAMPP can’t connect to your database using the new port that you set, it will let you know through the control panel’s log. In that case, you might try using a different port instead.

Summary

If you use XAMPP to run WordPress locally, you may encounter the occasional error with your server’s configuration. One of the most common issues is MySQL shutting down unexpectedly.

The good news is that, if this does happen, there are three methods you can use to troubleshoot the issue:

1. Run XAMPP using administrator privileges.
2. Restore your database backup.
3. Change your MySQL port.

If you enjoyed this XAMPP tutorial, be sure to check out DevKinsta as well. DevKinsta is our free local development tool that lets you quickly spin up WordPress sites with customizable PHP settings, HTTPS support, built-in email and database management, and more. DevKinsta also features full integration with MyKinsta, but you don’t have to be a Kinsta customer to integrate DevKinsta into your workflow.

If you use a local development environment, you may run into problems that are similar to those on a live server. In some cases, your WordPress website may be unable to connect with its database because MySQL isn’t running or it shut down unexpectedly.

Depending on which local environment you use, the process of troubleshooting your MySQL database might vary a bit. With XAMPP, the process is remarkably straightforward since you get access to a control panel instead of having to rely on the command line only.

In this article, we’ll explain what XAMPP is and what the “MySQL shutdown unexpectedly” error means. Then we’ll walk you through three methods you can use to fix it. Let’s get to it!

An Introduction to XAMPP

XAMPP is a free, PHP development environment that you can use for Windows, macOS, or Linux. It is a collection of software that enables you to host websites locally by mimicking the functions of a live server:

Using XAMPP, you can install all the software you need to run WordPress locally using a single bundle, rather than setting up each element individually. Development environments differ in what software they bundle.

With XAMPP, the components that you get include:

• Apache: This is arguably the most popular web server software in the world, and it enables you to host sites.
• MariaDB: This open-source database software enables you to manage databases.
• PHP: WordPress is built on PHP, which means you need a PHP install to run the Content Management System (CMS).
• Perl: Although WordPress doesn’t use the Perl programming language, it comes as part of the XAMPP stack by default.

On top of setting up the software you need to run WordPress, XAMPP provides you with a simple control panel:

This enables you to access logs for each of XAMPP’s components. It includes an overview log that shows you everything that’s happening in the background of your environment.

However, using a local development distribution doesn’t mean your server isn’t susceptible to errors. In some cases, the software components may malfunction, such as with the XAMPP error “MySQL shutdown unexpectedly”.

What Is the XAMPP Error “MySQL Shutdown Unexpectedly”?

As the name of the error implies, this is the message you’ll see if the MySQL software on your environment shuts down or ceases to function unexpectedly:

We say “unexpectedly”, because you can manually shut down the MySQL database software at any point. That also happens when you restart your server.

However, when the software is shut down, your website won’t be able to connect to its database. In other words, WordPress won’t work.

As you can see in the above image, XAMPP provides you with advice on troubleshooting the “MySQL shutdown unexpectedly error” right within its events log. In the next section, we’ll go into more detail on the various ways you can use to fix this issue.

How to Fix the XAMPP Error “MySQL Shutdown Unexpectedly” (3 Methods)?

Typically, fixing the XAMPP error “MySQL shutdown unexpectedly” is quick and easy. Below, we’ll walk you through three fixes, starting with the simplest.

1. Run XAMPP Using Administrator Privileges

Often, XAMPP produces errors when you don’t run the software using administrator privileges. This is because its components may not be able to function or configure properly at lower permission levels.

If you’re unsure whether that’s the case with your setup, we recommend that you close XAMPP altogether, and then restart the environment as an administrator. To do so in Windows, find the folder where you installed XAMPP and locate the xampp-control file. Next, right-click on that file and select Run as administrator:

If you’re a macOS user, you can right-click on the folder, and then select Get Info. In the pop-up window that opens, navigate to the Sharing & Permissions section, click on the padlock icon, and enter your administrator password. Change the Read & Write permission settings to Everyone.

Once XAMPP is up and each of its components is running, MySQL should function correctly. That means your database will be accessible.

2. Restore Your Database Backup

If restarting XAMPP with administrator privileges doesn’t solve the problem with your database, the next step is to restore its backup. XAMPP automatically creates backups for your environment’s software, which you can access within the folder where you installed it.

By default, your XAMPP MySQL backup files should be under Local Disk > XAMPP > MySQL. Inside that directory, you’ll see several folders, two of which are called data and backup:

The data folder includes all of the files that your database uses. The backup folder contains a single recent copy of your MySQL.

You can make a backup by clicking on the Stop button to the right of the MySQL option on the main menu:

Once you stop MySQL, return to XAMPP’s MySQL folder and follow these steps to restore the MySQL backup:

1. Make a copy of the data folder.
2. Rename this new folder copy to something like data-old. This will be your backup.
3. Copy the contents of the backup folder into the data folder.

That’s it! To play it safe, though, we strongly recommend that you keep the data-old folder around until you make sure everything is working properly.

At this stage, you can return to the XAMPP control panel to restart MySQL, which should be running correctly now.

3. Change Your MySQL Port

One of the most common causes of the XAMPP error “MySQL shutdown unexpectedly” is another software using the port assigned to MySQL. By default, it tends to be 3306. To be certain, you can select the Netstat module from XAMPP’s control panel, right above the Shell tool:

Netstat is a command line tool that can show you active connections on your network, including which ports they’re using. Once you initialize Netstat, you’ll be able to see what port each tool in your stack is using, including MySQL.

If a conflict with that port caused the shutdown, restoring a backup or running MySQL with administrator privileges won’t make a difference. The only way to solve this issue is to change the port that MySQL uses. Thanks to Netstat, you can see what that port is and which other ones are in use.

To do so, go ahead and stop the service, using the same process we showed you in the last section. Next, click on the Config button next to MySQLon XAMPP’s main menu, and then select the my.ini option:

The my.ini file contains the MySQL configuration settings. After you click on it, XAMPP will open the file using your default text editor. Once you’re in, look for the line that reads Port, which specifies the port number that MySQL uses.

Here, you can change that port number to another option that you know other programs aren’t using. In most cases, we recommend using 3307, which should be available. Save your changes and close the my.ini file.

You can then use the XAMPP control panel to restart MySQL. Hopefully, your database is now working as it should. If for some reason, XAMPP can’t connect to your database using the new port that you set, it will let you know through the control panel’s log. In that case, you might try using a different port instead.

Summary

If you use XAMPP to run WordPress locally, you may encounter the occasional error with your server’s configuration. One of the most common issues is MySQL shutting down unexpectedly.

The good news is that, if this does happen, there are three methods you can use to troubleshoot the issue:

1. Run XAMPP using administrator privileges.
2. Restore your database backup.
3. Change your MySQL port.

If you enjoyed this XAMPP tutorial, be sure to check out DevKinsta as well. DevKinsta is our free local development tool that lets you quickly spin up WordPress sites with customizable PHP settings, HTTPS support, built-in email and database management, and more. DevKinsta also features full integration with MyKinsta, but you don’t have to be a Kinsta customer to integrate DevKinsta into your workflow.

I am new to XAMPP, but I find that a combination of these suggestions works best (At least on Windows 8.1 with the latest version of XAMPP. Note that the computer I tested this on, also had skype).

First logon to skype and navigate to «Tools < Options < Advanced < Connection.»
Then check the box that says «Use port 80 and 443 for additional incoming connections.» Save, close, and quit skype.

Next, on your XAMPP control panel, click «config < my.ini» and change lines 19 and 27 (should have port = 3306) from «3306» to «3307.»

Also, you will need to navigate to xampp < phpMyAdmin < config.inc and change line 27, which should like something like this:

$cfg[‘Servers’][$i][‘host’] = ‘127.0.0.1’;

You will need to add «3307» as follows:

$cfg[‘Servers’][$i][‘host’] = ‘127.0.0.1:3307’;

Now, open your browser and you should see the xampp page when you type in «localhost.»
Additionally, if this is your first time using xampp, you may see a warning about your lack of password (highlighted in pink) on your localhost/phpmyadmin/ page. This is easily remedied by going to the «user accounts» tab in phpmyadmin, clicking on «edit privileges» and entering password. Remember to save the hashed version of any and all passwords you create as we will use this next! -I opened a notepad and saved (and numbered) them. Note that phpMyadmin will notify you of when you are changing the password for your current session (this will be displayed at the top of your phpMyadmin page and is very important, as you will need THAT specific hashed version of your password).

Next, you will need to navigate to the following location «xampp < phpMyAdmin < config.inc» on your computer and open and edit the file with a text editor. You will want to put in the hashed version of your password between the single quotes for password and change «AllowNoPassword» from true to false.

And, that ought to do it.

Ошибка: MySQL shutdown unexpectedly

Некоторые пользователи не могут запустить MySQL в XAMPP. По их словам, каждый раз, когда они запускают MySQL в XAMPP, они получают сообщение об ошибке, в котором говорится: «MySQL shutdown unexpectedly». Наиболее распространенной причиной этой проблемы являются поврежденные файлы базы данных XAMPP. Если у вас возникла такая проблема с MySQL, советы, представленные в этом посте, могут помочь вам решить проблему.

Почему MySQL неожиданно завершает работу?

Перед выходом из XAMPP необходимо остановить MySQL. Если вы выйдете из XAMPP без остановки MySQL, это может привести к повреждению файлов данных MySQL. Из-за этого у вас могут возникнуть некоторые проблемы с MySQL, такие как неожиданное завершение работы MySQL. Если у вас возникла такая проблема, возможно, файлы данных MySQL в вашей системе повреждены. Мы описали некоторые методы устранения неполадок, которые могут помочь вам избавиться от этой проблемы.

Ошибка: неожиданное завершение работы MySQL

Попробуйте следующие решения, чтобы устранить проблему. Прежде чем продолжить, мы рекомендуем вам создать резервную копию папки XAMPP. Для этого скопируйте папку XAMPP и вставьте ее в другой раздел вашего жесткого диска или на внешний жесткий диск.

Давайте посмотрим на все эти решения в деталях. Прежде чем пробовать каждый метод, описанный ниже, убедитесь, что вы правильно закрыли XAMPP.

Запустите XAMPP от имени администратора

Рекомендуется всегда запускать XAMPP от имени администратора, чтобы избежать повреждения файла данных. Запустите XAMPP от имени администратора и посмотрите, решит ли это проблему. Если это поможет, вы сэкономите время на других методах устранения неполадок. Чтобы запустить XAMPP от имени администратора, выполните следующие действия:

1. Нажмите «Поиск Windows» и введите XAMPP.
2. Щелкните правой кнопкой мыши XAMPP и выберите «Запуск от имени администратора» .
3. Нажмите « Да», если вы получили приглашение UAC.

Восстановить базу данных MySQL

Как описано выше в этой статье, основной причиной этой проблемы является повреждение файлов данных XAMPP. Если проблема возникает на вашем компьютере из-за этой проблемы, восстановление базы данных MySQL может решить проблему. Шаги по восстановлению базы данных MySQL приведены ниже:

Щелкните Поиск Windows и введите PowerShell. Выберите Windows PowerShell в результатах поиска.

Введите следующую команду: mysqld —console —skip-grant-tables —skip-external-locking и нажмите Enter.

Приведенная выше команда запустит сервер MySQL без загрузки таблиц грантов. Когда указанная выше команда будет выполнена успешно, введите следующую команду: mysqlcheck -r —databases mysql —use-frm и нажмите Enter.

Приведенная выше команда восстановит базу данных MySQL. После успешного выполнения вышеуказанных команд проверьте, сохраняется ли проблема.

Измените файл my.ini

Изменение порта путем изменения файла my.ini устранило проблему для некоторых пользователей. Вы также можете попробовать это. Откройте файл my.ini и измените порт 3306 на другой. По умолчанию файл my.ini находится в следующем месте: C:xamppmysqlbin

1. Откройте Проводник.
2. Скопируйте указанный выше путь и вставьте его в адресную строку Проводника. После этого нажмите Enter.
3. Теперь прокрутите вниз и найдите файл my.ini.
4. Как только вы найдете его, щелкните его правой кнопкой мыши и выберите «Открыть с помощью > Блокнот».

Если вы не найдете файл my.ini в указанном выше месте, вы можете следовать приведенным ниже инструкциям.

1. Нажмите «Поиск Windows» и введите XAMPP.
2. Щелкните правой кнопкой мыши XAMPP в результатах поиска и выберите «Запуск от имени администратора» .
3. Нажмите «Да» в приглашении UAC. Это откроет панель управления XAMPP.
4. Нажмите кнопку Config рядом с MySQL и выберите my.ini . Это откроет файл my.ini в текстовом редакторе по умолчанию.

После открытия файла my.ini в Блокноте нажмите клавиши Ctrl + F и введите 3306. Замените любой из портов 3306 другим номером порта. Вы можете ввести любой случайный номер порта, например 3307, 3308 и т. д. Для некоторых пользователей проблема устранена заменой порта 3306 на 2811.

1. Сохраните файл my.ini и закройте Блокнот.
2. Перезагрузите компьютер и запустите XAMPP.
3. Проверьте, устранена ли проблема.

Если это не сработает, отмените изменения, внесенные в файл my.ini, и попробуйте следующее решение.

Удалите все файлы в папке «Данные»

Если приведенное выше решение не устранило вашу проблему, отмените изменения в файле my.ini, которые вы только что внесли. Теперь откройте проводник и перейдите по следующему пути: C:xamppmysqlданные

Приведенный выше путь открывает папку данных напрямую. Теперь удалите все файлы, кроме папок. После удаления файлов в папке Data перейдите по следующему пути в проводнике:

Найдите файл my.ini и откройте его с помощью Блокнота. Теперь введите port=8111 чуть ниже port=3306 (как показано на снимке экрана выше). Нажмите клавиши Ctrl + S , чтобы сохранить изменения, внесенные в файл my.ini, и закройте Блокнот. Теперь запустите XAMPP от имени администратора и запустите MySQL. На этот раз проблема не должна возникнуть.

Если приведенное выше решение не устранило вашу проблему, откройте папку XAMPP, которую вы скопировали на внешний жесткий диск или в другой раздел жесткого диска, и скопируйте все содержимое внутри нее. Теперь откройте XAMPP на диске C и вставьте туда скопированное содержимое. Замените файлы и папки, если вас попросят это сделать. Теперь перейдите по следующему пути: C:xamppmysqldata

Переименуйте aria_log_control в aria_log_control_old и запустите XAMPP. Запустите MySQL и посмотрите, внесет ли это какие-либо изменения. Если это не поможет, отмените изменения и попробуйте следующее решение.

Остановите все службы SQL и запустите их снова

Перезапуск служб SQL устранил проблему некоторых пользователей. Этот метод может работать и для вас. Откройте приложение «Службы», остановите все службы SQL и запустите их снова. Шаги для этого написаны ниже:

1. Нажмите клавиши Win+R Это запустит окно команды «Выполнить».
2. Введите services.msc и нажмите ОК. Появится окно управления услугами.
3. В приложении «Службы» прокрутите вниз и найдите службы SQL. На вашем компьютере может быть несколько служб SQL.
4. Остановите все службы SQL. Для этого щелкните правой кнопкой мыши службу SQL и выберите «Остановить».
5. Теперь снова щелкните правой кнопкой мыши службы SQL и выберите «Пуск».

После перезапуска служб SQL закройте приложение «Службы» и запустите XAMPP от имени администратора. Запустите MySQL и посмотрите, возникает ли ошибка снова.

Скопируйте файлы из папки резервного копирования в папку данных

Еще одно эффективное решение этой проблемы — скопировать все данные из папки «Резервное копирование» и вставить их в папку «Данные». Для этого сначала скопируйте указанный ниже путь и вставьте его в адресную строку Проводника. После этого нажмите Enter.

Это откроет папку резервного копирования XAMPP в вашем каталоге C. Теперь скопируйте оттуда все данные и перейдите по следующему пути:

Вставьте туда скопированные данные. Если вам будет предложено заменить файлы, выберите Да. Запустите XAMPP от имени администратора и проверьте, можете ли вы запустить MySQL на этот раз. Если нет, попробуйте следующее решение.

Удалите файлы INFO из папки данных

Если проблема не устранена, удалите файл INFO и проверьте, помогает ли он. Файлы INFO находятся в следующем месте на вашем диске C:xamppmysqlbackup

Независимо от того, есть ли в указанном выше месте один или несколько файлов INFO, вы должны удалить их все. После удаления файлов INFO запустите XAMPP и запустите MySQL. MySQL должен запуститься без каких-либо ошибок.

Если это не сработает, скопируйте все файлы из папки XAMPP, которую вы создали в качестве резервной копии, на внешний жесткий диск или в другой раздел жесткого диска и вставьте скопированные файлы в папку XAMPP на диске C. Замените файлы и папки, если вас об этом попросят.

Это решение помогло многим пользователям. Если приведенные выше решения не помогли решить вашу проблему, этот метод должен вам помочь. Переименуйте папку Data и скопируйте файл ibdata1 в папку Data. Процесс, как это сделать, описан ниже:

1. Откройте папку XAMPP, расположенную на диске C.
2. Теперь откройте папку mysql.
3. Переименуйте папку данных в data_old.
4. Скопируйте папку резервной копии на другой раздел жесткого диска или на внешний жесткий диск. Теперь переименуйте папку резервной копии, расположенную внутри папки mysql на диске C, в data.
5. Откройте папку data_old и скопируйте в нее все папки базы данных и файл ibdata1. Не копируйте папки mysql, performance_schema и phpmyadmin.
6. Теперь откройте папку данных (которая раньше была папкой резервной копии) и вставьте туда скопированные данные. Замените файлы, если вас об этом попросят.
7. Запустите панель управления XAMPP и запустите mysql.

Удалите и переустановите XAMPP

Если все вышеперечисленные решения не помогли решить вашу проблему, удалите и переустановите XAMPP. Вы можете удалить XAMPP из панели управления или из настроек Windows 11/10. После удаления Xampp загрузите его последнюю версию с официального сайта Apache и установите снова.

Что делать, если MySQL не открывается в XAMPP?

У вас могут возникнуть проблемы с XAMPP, если вы установите его в другом месте, а не в месте по умолчанию. Расположение по умолчанию для установки XAMPP — c:xampp. Поэтому, если вы установили XAMPP в другом месте, удалите его и установите в место по умолчанию. Если вы установили XAMPP в расположение по умолчанию, но MySQL по-прежнему не открывается или не работает в XAMPP, откройте приложение «Службы» в Windows 11/10, остановите все службы SQL и запустите их снова.

Источник

How to Fix the XAMPP Error “MySQL Shutdown Unexpectedly” (3 Methods)

If you use a local development environment, you may run into problems that are similar to those on a live server. In some cases, your WordPress website may be unable to connect with its database because MySQL isn’t running or it shut down unexpectedly.

Depending on which local environment you use, the process of troubleshooting your MySQL database might vary a bit. With XAMPP, the process is remarkably straightforward since you get access to a control panel instead of having to rely on the command line only.

In this article, we’ll explain what XAMPP is and what the “MySQL shutdown unexpectedly” error means. Then we’ll walk you through three methods you can use to fix it. Let’s get to it!

An Introduction to XAMPP

XAMPP is a free, PHP development environment that you can use for Windows, macOS, or Linux. It is a collection of software that enables you to host websites locally by mimicking the functions of a live server:

The XAMPP website.

Using XAMPP, you can install all the software you need to run WordPress locally using a single bundle, rather than setting up each element individually. Development environments differ in what software they bundle.

With XAMPP, the components that you get include:

Need to give a shoutout here. Kinsta is amazing, I use it for my personal website. The support is rapid and outstanding, and their servers are the fastest for WordPress.

Phillip Stemann

• Apache: This is arguably the most popular web server software in the world, and it enables you to host sites.
• MariaDB: This open-source database software enables you to manage databases.
• PHP: WordPress is built on PHP, which means you need a PHP install to run the Content Management System (CMS).
• Perl: Although WordPress doesn’t use the Perl programming language, it comes as part of the XAMPP stack by default.

On top of setting up the software you need to run WordPress, XAMPP provides you with a simple control panel:

The XAMPP control panel.

This enables you to access logs for each of XAMPP’s components. It includes an overview log that shows you everything that’s happening in the background of your environment.

However, using a local development distribution doesn’t mean your server isn’t susceptible to errors. In some cases, the software components may malfunction, such as with the XAMPP error “MySQL shutdown unexpectedly”.

Important

Looking for a free and powerful local WordPress development tool? DevKinsta features quick and easy site creation, email and database management tools, one-click PHP version switching, and full integration with MyKinsta. Get started with DevKinsta today, even if you’re not a Kinsta customer.

What Is the XAMPP Error “MySQL Shutdown Unexpectedly”?

As the name of the error implies, this is the message you’ll see if the MySQL software on your environment shuts down or ceases to function unexpectedly:

The XAMPP error “MySQL shutdown unexpectedly”.

We say “unexpectedly”, because you can manually shut down the MySQL database software at any point. That also happens when you restart your server.

However, when the software is shut down, your website won’t be able to connect to its database. In other words, WordPress won’t work.

As you can see in the above image, XAMPP provides you with advice on troubleshooting the “MySQL shutdown unexpectedly error” right within its events log. In the next section, we’ll go into more detail on the various ways you can use to fix this issue.

How to Fix the XAMPP Error “MySQL Shutdown Unexpectedly” (3 Methods)?

Typically, fixing the XAMPP error “MySQL shutdown unexpectedly” is quick and easy. Below, we’ll walk you through three fixes, starting with the simplest.

1. Run XAMPP Using Administrator Privileges

Often, XAMPP produces errors when you don’t run the software using administrator privileges. This is because its components may not be able to function or configure properly at lower permission levels.

If you’re unsure whether that’s the case with your setup, we recommend that you close XAMPP altogether, and then restart the environment as an administrator. To do so in Windows, find the folder where you installed XAMPP and locate the xampp-control file. Next, right-click on that file and select Run as administrator:

Deploy your application to Kinsta — Start with a $20 Credit now.

Run your Node.js, Python, Go, PHP, Ruby, Java, and Scala apps, (or almost anything else if you use your own custom Dockerfiles), in three, easy steps!

If you’re a macOS user, you can right-click on the folder, and then select Get Info. In the pop-up window that opens, navigate to the Sharing & Permissions section, click on the padlock icon, and enter your administrator password. Change the Read & Write permission settings to Everyone.

Once XAMPP is up and each of its components is running, MySQL should function correctly. That means your database will be accessible.

2. Restore Your Database Backup

If restarting XAMPP with administrator privileges doesn’t solve the problem with your database, the next step is to restore its backup. XAMPP automatically creates backups for your environment’s software, which you can access within the folder where you installed it.

By default, your XAMPP MySQL backup files should be under Local Disk > XAMPP > MySQL. Inside that directory, you’ll see several folders, two of which are called data and backup:

XAMPP’s MySQL directory.

The data folder includes all of the files that your database uses. The backup folder contains a single recent copy of your MySQL.

Important

Before you restore the backup files, use your XAMPP control panel to stop the MySQL software.

You can make a backup by clicking on the Stop button to the right of the MySQL option on the main menu:

Using the XAMPP control panel.

Once you stop MySQL, return to XAMPP’s MySQL folder and follow these steps to restore the MySQL backup:

Looking for a powerful tool for local WordPress development? DevKinsta features one-click site creation, built-in HTTPS, powerful email and database management tools, and more. Learn more about DevKinsta!

1. Make a copy of the data folder.
2. Rename this new folder copy to something like data-old. This will be your backup.
3. Copy the contents of the backup folder into the data folder.

That’s it! To play it safe, though, we strongly recommend that you keep the data-old folder around until you make sure everything is working properly.

At this stage, you can return to the XAMPP control panel to restart MySQL, which should be running correctly now.

3. Change Your MySQL Port

One of the most common causes of the XAMPP error “MySQL shutdown unexpectedly” is another software using the port assigned to MySQL. By default, it tends to be 3306. To be certain, you can select the Netstat module from XAMPP’s control panel, right above the Shell tool:

Using XAMPP’s Netstat tool.

Netstat is a command line tool that can show you active connections on your network, including which ports they’re using. Once you initialize Netstat, you’ll be able to see what port each tool in your stack is using, including MySQL.

Checking active connections using Netstat.

If a conflict with that port caused the shutdown, restoring a backup or running MySQL with administrator privileges won’t make a difference. The only way to solve this issue is to change the port that MySQL uses. Thanks to Netstat, you can see what that port is and which other ones are in use.

To do so, go ahead and stop the service, using the same process we showed you in the last section. Next, click on the Config button next to MySQLon XAMPP’s main menu, and then select the my.ini option:

Accessing MySQL’s config file.

The my.ini file contains the MySQL configuration settings. After you click on it, XAMPP will open the file using your default text editor. Once you’re in, look for the line that reads Port, which specifies the port number that MySQL uses.

Here, you can change that port number to another option that you know other programs aren’t using. In most cases, we recommend using 3307, which should be available. Save your changes and close the my.ini file.

You can then use the XAMPP control panel to restart MySQL. Hopefully, your database is now working as it should. If for some reason, XAMPP can’t connect to your database using the new port that you set, it will let you know through the control panel’s log. In that case, you might try using a different port instead.

Summary

If you use XAMPP to run WordPress locally, you may encounter the occasional error with your server’s configuration. One of the most common issues is MySQL shutting down unexpectedly.

The good news is that, if this does happen, there are three methods you can use to troubleshoot the issue:

1. Run XAMPP using administrator privileges.
2. Restore your database backup.
3. Change your MySQL port.

If you enjoyed this XAMPP tutorial, be sure to check out DevKinsta as well. DevKinsta is our free local development tool that lets you quickly spin up WordPress sites with customizable PHP settings, HTTPS support, built-in email and database management, and more. DevKinsta also features full integration with MyKinsta, but you don’t have to be a Kinsta customer to integrate DevKinsta into your workflow.

Get all your applications, databases and WordPress sites online and under one roof. Our feature-packed, high-performance cloud platform includes:

• Easy setup and management in the MyKinsta dashboard
• 24/7 expert support
• The best Google Cloud Platform hardware and network, powered by Kubernetes for maximum scalability
• An enterprise-level Cloudflare integration for speed and security
• Global audience reach with up to 35 data centers and 275+ PoPs worldwide

Test it yourself with $20 off your first month of Application Hosting or Database Hosting. Explore our plans or talk to sales to find your best fit.

Источник

Users working on the MySQL platform encounter an error called “Error: MySQL shutdown unexpectedly”. Issues in the database and corrupted files are some of the reasons behind this error. So, removing these corrupted files will fix this issue.

You might face this error while starting the XAMPP control panel and the Apache module. In this post, we will find a way to resolve this issue.

Cause of “Error: MySQL Shutdown Unexpectedly” in XAMPP

Apart from corrupted files, improper database shut down, missing files and port changes can also cause this error. When you run MySQL in a webserver, the corrupted files in the mysql/data folder cause MySQL to shut down.

This is what the error looks like – 

Error: MySQL shutdown unexpectedly.

This may be due to a blocked port, missing dependencies,

improper privileges, a crash, or a shutdown by another method.

Press the Logs button to view error logs and check

the Windows Event Viewer for more clues

If you need more help, copy and post this

entire log window on the forums

Error log

xamppmysqldatamysql_error.log 

InnoDB: Mutexes and rw_locks use Windows interlocked functions

InnoDB: Uses event mutexes

InnoDB: Compressed tables use zlib 1.2.11

InnoDB: Number of pools: 1

InnoDB: Using SSE2 crc32 instructions

InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M

InnoDB: Completed initialization of buffer pool

InnoDB: 128 out of 128 rollback segments are active.

InnoDB: Creating shared tablespace for temporary tables

InnoDB: Setting file 'xamppmysqldataibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

InnoDB: File 'xamppmysqldataibtmp1' size is now 12 MB.

InnoDB: Waiting for purge to start

InnoDB: 10.4.11 started; log sequence number 47134; transaction id 9

InnoDB: Loading buffer pool(s) from E:xamppmysqldataib_buffer_pool

Plugin 'FEEDBACK' is disabled.

InnoDB: Buffer pool(s) load completed at 201018 18:42:04

Server socket created on IP: '::'.

Steps to fix this problem – 

• Stop the XAMPP server, MySQL and Apache
• Create a backup of the “/xampp/mysql/data” folder using a compression software
• Rename the “/xampp/mysql/data” folder to “/xampp/mysql/data-old”
• Create a new folder and name it “/xampp/mysql/data”
• Copy all folders from the “/xampp/mysql/backup” and paste it to the “/xampp/mysql/data” folder, which you have just created
• Copy all the databases from the “/xampp/mysql/data-old” folder and paste it to the “/xampp/mysql/data” folder
• Finally copy the “ibdata1” and all of the log files including “ib_logfile0, ib_logfile1 ” from “/xampp/mysql/data-old” and paste it to the “/xampp/mysql/data” folder
• Start MySQL from the XAMPP control panel
• Go to phpMyAdmin to check if all the databases are available and running properly

While undergoing this process make sure you backup all your data in a secure place.

Some users are unable to start MySQL in XAMPP. According to them, every time they start MySQL in XAMPP, they receive an error message that says “Error: MySQL shutdown unexpectedly.” The most common cause of this problem is the corrupted database files of XAMPP. If you are experiencing such an issue with MySQL, the suggestions provided in this post may help you fix the problem.

Why does MySQL shutdown unexpectedly?

It is necessary to stop MySQL before exiting XAMPP. If you exit XAMPP without stopping MySQL, it may corrupt the MySQL data files. Due to this, you may experience several problems with MySQL, like the shutting down of MySQL unexpectedly. If you are experiencing such a problem, it might be possible that the MySQL data files on your system are corrupted. We have described some troubleshooting methods that may help you get rid of this problem.

Try the following solutions to fix the issue. Before you proceed, we recommend you create a backup of the XAMPP folder. For this, copy the XAMPP folder and paste it into another partition of your hard drive or your external hard drive.

1. Launch XAMPP as administrator
2. Repair MySQL Database
3. Modify the my.ini file
4. Delete all the files inside the Data folder
5. Rename the aria_log_control file
6. Stop all the SQL services and start them again
7. Copy the files from the Backup folder to the Data folder
8. Delete the INFO file(s) from the Data folder
9. Rename the Data folder and copy the ibdata1 file to the Data folder
10. Uninstall and reinstall Xampp

Let’s see all these solutions in detail. Before trying every method written below, make sure that you have closed XAMPP properly.

1] Launch XAMPP as administrator

It is recommended to always launch XAMPP as an administrator to avoid data file corruption. Launch XAMPP as administrator and see if it fixes the problem. If this helps, you will save time on other troubleshooting methods. To launch XAMPP as administrator, follow the steps below:

1. Click on Windows Search and type XAMPP.
2. Right-click on XAMPP and select Run as Administrator.
3. Click Yes if you receive the UAC prompt.

You can also set XAMPP to always run as administrator.

2] Repair MySQL Database

As described above in this article, the main cause of this problem is the corruption in XAMPP data files. If the problem is occurring on your computer due to this issue, repairing the MySQL database can fix the issue. The steps to repair the MySQL database are given below:

Click on Windows Search and type PowerShell. Select Windows PowerShell from the Search Results.

Type the following command and press Enter.

mysqld --console --skip-grant-tables --skip-external-locking

The above command will start the MySQL server without loading the grant tables. When the above command is executed successfully, type the following command and press Enter.

mysqlcheck -r --databases mysql --use-frm

The above command will repair the MySQL database. After the above commands are executed successfully, check if the issue persists.

3] Modify the my.ini file

Changing the port by modifying the my.ini file has fixed the issue for some users. You can also try this. Open the my.ini file and change the port 3306 to something else. By default, the my.ini file is located at the following location:

C:xamppmysqlbin

1. Open the File Explorer.
2. Copy the above path and paste it into the address bar of File Explorer. After that hit Enter.
3. Now, scroll down and locate the my.ini file.
4. Once you find it, right-click on it and select “Open with > Notepad.”

If you do not find the my.ini file at the above-mentioned location, you can follow the instructions mentioned below.

1. Click on Windows Search and type XAMPP.
2. Right-click on XAMPP from the search results and select Run as Administrator.
3. Click Yes in the UAC prompt. This will open the XAMPP Control panel.
4. Click on the Config button next to MySQL and select my.ini. This will open the my.ini file in your default text editor software.

After opening the my.ini file in Notepad, press the Ctrl + F keys and type 3306. Replace any of the 3306 ports with a different port number. You can enter any random port number, like 3307, 3308, etc. For some users, replacing the 3306 port with 2811 fixed the issue.

Save the my.ini file and close Notepad. Restart your computer and then launch XAMPP. Check if the issue is fixed. If this does not work, revert the changes that you have made in the my.ini file and try the next solution.

4] Delete all the files inside the Data folder

If the above solution did not fix your problem, revert the changes in the my.ini file that you have just made. Now, open the File Explorer and go to the following path:

C:xamppmysqldata

The above path opens the Data folder directly. Now, delete all the files except the folders. After deleting the files inside the Data folder, go to the following path in File Explorer:

C:xamppmysqlbin

Locate the my.ini file and open it with Notepad. Now, type port=8111 just below port=3306 (as shown in the screenshot above). Press the Ctrl + S keys to save the changes you made in the my.ini file and close Notepad. Now, run XAMPP as administrator and start MySQL. The problem should not occur this time.

5] Rename the aria_log_control file

If the above solution did not fix your problem, Open the XAMPP folder that you copied on your external hard drive or on another hard drive partition and copy all the contents inside it. Now, open the XAMPP on your C drive and paste the copied content there. Replace the files and folders if you will be asked to do so. Now, go to the following path:

C:xamppmysqldata

Rename aria_log_control to aria_log_control_old and launch XAMPP. Start MySQL and see if this brings any changes. If this does not help, revert the changes and try the next solution.

Read: Best free Xampp Server alternatives for developers.

6] Stop all the SQL services and start them again

Restarting the SQL services has fixed the issue of some users. This method may work for you too. Open the Services app and stop all the SQL services and start them again. The steps to do this are written below:

1. Press the Win + R keys. This will launch the Run command box.
2. Type services.msc and click OK. The Service Management window will appear.
3. In the Services app, scroll down and locate the SQL services. You may find more than one SQL service on your computer.
4. Stop all the SQL services. For this, right-click on SQL service and select Stop.
5. Now, right-click again on the SQL services and select Start.

After restarting the SQL services, close the Services app and launch XAMPP as administrator. Start MySQL and see if the error occurs again.

7] Copy the files from the Backup folder to the Data folder

Another effective solution to fix this problem is to copy all the data inside the Backup folder and paste it into the Data folder. To do so, first, copy the below path and paste it into the address bar of the File Explorer. After that press Enter.

C:xamppmysqlbackup

This will open the Backup folder of XAMPP in your C directory. Now, copy all the data from there and go to the following path:

C:xamppmysqldata

Paste the copied data there. If you are prompted to replace the files, select Yes. Launch XAMPP as administrator and check if you can start MySQL this time. If not, try the next solution.

8] Delete the INFO file(s) from the Data folder

If the problem still persists, delete the INFO file and check if it helps. The INFO file(s) is/are located at the following location on your C drive.

C:xamppmysqldata

Whether there is one or more than one INFO file at the above location, you have to delete all of them. After deleting the INFO file(s), launch XAMPP and start MySQL. MySQL should start without giving any error.

If this does not work, copy all the files from the XAMPP folder that you have created as a backup on your external hard drive or on another hard drive partition and paste the copied files inside the XAMPP folder on your C drive. Replace the files and folders if you are asked to do so.

9] Rename the Data folder and copy the ibdata1 file to the Data folder

This solution has helped a lot of users. If the above solutions did not fix your problem, this method should work for you. Rename the Data folder and copy the ibdata1 file to the Data folder. The process to do this is explained below.

1. Open the XAMPP folder located on your C drive.
2. Now, open the mysql folder.
3. Rename the data folder to data_old.
4. Copy the backup folder on another partition of your hard drive or on an external hard drive. Now, rename the backup folder located inside the mysql folder on your C drive to data.
5. Open the data_old folder and copy all the database folders inside it and the ibdata1 file. Do not copy the mysql, performance_schema, and phpmyadmin folders. Now, open the data folder (which was actually the backup folder earlier) and paste the copied data there. Replace the files if you are asked to do so.
6. Launch XAMPP Control Panel and start mysql.

10] Uninstall and reinstall XAMPP

If all the above solutions failed to fix your problem, uninstall and reinstall XAMPP. You can uninstall XAMPP from the Control Panel or from Windows 11/10 Settings. After uninstalling Xampp, download its latest version from the official website of Apache and install it again.

Read: How to increase phpMyAdmin upload size on XAMPP.

What to do if MySQL is not opening in XAMPP?

You may experience problems with XAMPP if you install it in another location instead of its default location. The default location to install XAMPP is c:xampp. Therefore, if you have installed XAMPP on another location, uninstall it and install it on its default location. If you have installed XAMPP on its default location but still MySQL is not opening or running in XAMPP, open the Services app in Windows 11/10 and stop all SQL services and start them again.

Another effective solution to fix this problem is to change the port 3306 to 3308. To do this, you have to edit the my.ini file, which is located at the following location:

C:xamppmysqlbin

Hope this helps.

Read next: Apache is not starting from XAMPP Control Panel in Windows 11/10.