Version: ' 10.1.9-mariadb ' socket: ' port:3306 mariadb.org binary distribution
2016-07-18 10:42:04 1578 InnoDB:Warning:Using innodb_additional_mem_pool_size is DEPRECATED. This option is removed in future releases, together with the option Innodb_use_sys_malloc and with the InnoDB ' s intern Al memory allocator.
2016-07-18 10:42:04 5496 [Note] innodb:using mutexes to ref count buffer pool pages
2016-07-18 10:42:04 5496 [Note] innodb:the InnoDB memory heap is disabled
2016-07-18 10:42:04 5496 [Note] innodb:mutexes and rw_locks use Windows interlocked functions
2016-07-18 10:42:04 5496 [Note] innodb:memory barrier is not used
2016-07-18 10:42:04 5496 [Note] innodb:compressed tables use zlib 1.2.3
2016-07-18 10:42:04 5496 [Note] innodb:not using CPU CRC32 instructions
2016-07-18 10:42:04 5496 [Note] innodb:initializing buffer pool, size = 16.0M
2016-07-18 10:42:04 5496 [Note] innodb:completed initialization of buffer pool
2016-07-18 10:42:04 5496 [ERROR] innodb:e:\xampp\mysql\data\ibdata1 can ' t be opened in Read-write mode
2016-07-18 10:42:04 5496 [ERROR] innodb:the system tablespace must be writable!
2016-07-18 10:42:04 5496 [ERROR] Plugin ' InnoDB ' init function returned ERROR.
2016-07-18 10:42:04 5496 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.
2016-07-18 10:42:04 5496 [Note] Plugin ' FEEDBACK ' is disabled.
2016-07-18 10:42:04 5496 [ERROR] unknown/unsupported storage Engine:innodb
2016-07-18 10:42:04 5496 [ERROR] Aborting
The scarlet Letter can be found from the log, telling us that we can't read and write the Ibdatal file ... If the file can not read and write, it should be your manager's authority problem, the solution is to find the XAMPP installation directory to set the contents of this folder to the administrator has the highest permissions.
Workaround:
1. Open the Task Manager to terminate the MYSQLD process;
2. Open the Data folder of the MySQL installation directory and delete the following 2 files:
Ib_logfile0 and Ib_logfile1
3. Restart MySQL
Xampp startup problems with MySQL