XAMMPP Version: xampp-win32-1.8.3-0-VC11-installer
MySQL Version:
[View the current MySQL version]
Use-V Parameters
First, we must think of the parameter command to view the version number. The parameter is-V (uppercase letter) or -- version.
Usage:
D: \ xampp \ mysql \ bin <mysql-V
Or
D: \ xampp \ mysql \ bin <mysql-version
From: http://blog.163.com/magicc_love/blog/static/18585366220134159357764/
Mysql_error.log
16:06:35 8956 [Note] Plugin 'federated 'is disabled.
16:06:35 1fc8 InnoDB: Warning: Using stored is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
16:06:35 8956 [Note] InnoDB: The InnoDB memory heap is disabled
16:06:35 8956 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
16:06:35 8956 [Note] InnoDB: Compressed tables use zlib 1.2.3
16:06:35 8956 [Note] InnoDB: Not using CPU crc32 instructions
16:06:35 8956 [Note] InnoDB: Initializing buffer pool, size = 16.0 M
16:06:35 8956 [Note] InnoDB: Completed initialization of buffer pool
16:06:35 8956 [Note] InnoDB: The first specified data file F: \ xampp \ mysql \ data \ ibdata1 did not exist: a new database to be created!
16:06:35 8956 [Note] InnoDB: Setting file F: \ xampp \ mysql \ data \ ibdata1 size to 10 MB
16:06:35 8956 [Note] InnoDB: Database physically writes the file full: wait...
After trying the online method, the problem still persists:
1. Run mysql_installservice.bat In the xampp \ mysql directory. Press any key to close the dos window.
Then run mysql_uninstallservice.bat in this directory.
Now, MySql can be started successfully on the XAMPP control page.
2. In the my. ini file under \ BIN of D: \ XAMPP \ mysql, add
Innodb_force_recovery = 1
However, in the [mysqld] where the position is to be added, it is useless at the beginning at the end.
The above two methods fail to be solved. I will study the log carefully again.
Note:
The first specified data file F: \ xampp \ mysql \ data \ ibdata1 did not exist: a new database to be created!
Check whether the generated ibdata1 cannot be started because of an error in the file creation.
Start MySQL in XAMPP again
It can be started successfully to solve the problem.