Saltar al contenido

cómo resolver el error: mysql se apaga inesperadamente en el ejemplo de código xampp

Esta es la contestación más acertada que te podemos compartir, pero primero estúdiala pausadamente y valora si se adapta a tu proyecto.

Ejemplo 1: cierre inesperado de mysql xampp

1. Exit Xampp and navigate to xampp/mysql/data directory
2. delete the ibdata1 file3. restart the XAMPP server

or

1. Exit Xampp and navigate to xampp/mysql/data directory
2. delete the ibdata1, ib_logfile0,ib_logfile1,ib_logfile101 files
3. restart the XAMPP server

or

Try to check the error log at the installed location: /xampp/mysql/data/mysql_error.log

Ejemplo 2: mysql se apaga inesperadamente

So, before deleting files, first try to do what the error message in XAMPP 
message panel recommend you to do, using the MySQL backup folder which is 
included with XAMPP. So do the next:

Rename the folder mysql/data to mysql/data_old (you can use any name)

Create a new folder mysql/data

Copy the content that resides in mysql/backup to the new mysql/data folder

Copy all your database folders that are in mysql/data_old to mysql/data 
(skipping the mysql, performance_schema, and phpmyadmin folders from data_old)

Finally copy the ibdata1 file from mysql/data_old and replace it inside 
mysql/data folder

Start MySQL from XAMPP control panel

And, voilà. No databases lost, no ports changed, no run as administrator, 
no force recovery, no kill mysqld process, no restoring from previous versions,
no more errors.

Ejemplo 3: xampp mysql se apaga inesperadamente

1. Exit Xampp and navigate to xampp/mysql/data directory
2. delete the ibdata1 file3. restart the XAMPP server

or

1. Exit Xampp and navigate to xampp/mysql/data directory
2. delete the ibdata1, ib_logfile0,ib_logfile1,ib_logfile101 files
3. restart the XAMPP server

or

Try to check the error log at the installed location: /xampp/mysql/data/mysql_error.log
This can help you better debug the problem.
Also Note:

1. XAMPP might hit into port issue when you have skype also running.
2. There is a federated plugin issue that is common.

¡Haz clic para puntuar esta entrada!
(Votos: 0 Promedio: 0)



Utiliza Nuestro Buscador

Deja una respuesta

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *