XAMPP error with running MySQL - mysql

I have problem witch XAMPP. When I try to run MySQL, XAMPP shows this:
12:37:02 [mysql] Error: MySQL shutdown unexpectedly.
12:37:02 [mysql] This may be due to a blocked port, missing dependencies,
12:37:02 [mysql] improper privileges, a crash, or a shutdown by another method.
12:37:02 [mysql] Press the Logs button to view error logs and check
12:37:02 [mysql] the Windows Event Viewer for more clues
12:37:02 [mysql] If you need more help, copy and post this
12:37:02 [mysql] entire log window on the forums
I've changed ports to 3307 in
C:\xampp\mysql\bin\my.ini
and in C:\xampp\php\php.ini to mysql.default_port=3307
mysqli.default_port=3307.
I've also deleted ib_logfile1 in C:\xampp\mysql\data
, but it still doesn't work.
Error logs:
2017-08-17 12:27:00 2050 InnoDB: Warning: Using innodb_additional_mem_pool_size 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.
2017-08-17 12:27:00 8272 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB. `
2017-08-17 12:27:00 8272 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-08-17 12:27:00 8272 [Note] InnoDB: The InnoDB memory heap is disabled
2017-08-17 12:27:00 8272 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-08-17 12:27:00 8272 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-08-17 12:27:00 8272 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-08-17 12:27:00 8272 [Note] InnoDB: Using generic crc32 instructions
2017-08-17 12:27:00 8272 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-08-17 12:27:00 8272 [Note] InnoDB: Completed initialization of buffer pool
2017-08-17 12:27:00 8272 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2017-08-17 12:27:00 8272 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2017-08-17 12:27:00 8272 [ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile101
2017-08-17 12:27:00 8272 [ERROR] Plugin 'InnoDB' init function returned error.
2017-08-17 12:27:00 8272 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-08-17 12:27:00 8272 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-17 12:27:00 8272 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-08-17 12:27:00 8272 [ERROR] Aborting
Any help is appreciated. Thanks

MySQL is telling you exactly why it cannot start:
[ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile101
Hence I suggest the first thing you do is to check that c:\xampp\mysql\data exists and is writeable by the DBMS user.

First stop the service on the xampp control panel,
then click on the red cross on the left to install the service on your computer,
then the icon will become a green tick,
then start the service as administrator.
It should be working alright.

Open the XAMPP control panel and stop the actions.
Open services and go to MySql80.
Stop the service.
Start the service.

Related

Error: MySQL shutdown unexpectedly - XAMPP

I have trouble running mysql using xampp on a win10 machine.
Here is the xampp message:
Error: MySQL shutdown unexpectedly.
1:33:01 [mysql] This may be due to a blocked port, missing dependencies,
1:33:01 [mysql] improper privileges, a crash, or a shutdown by another method.
1:33:01 [mysql] Press the Logs button to view error logs and check
1:33:01 [mysql] the Windows Event Viewer for more clues
1:33:01 [mysql] If you need more help, copy and post this
1:33:01 [mysql] entire log window on the forums
And this is my mysql.log:
017-10-18 03:52:49 efc InnoDB: Warning: Using innodb_additional_mem_pool_size 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.
2017-10-18 3:52:49 3836 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2017-10-18 3:52:49 3836 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-10-18 3:52:49 3836 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-18 3:52:49 3836 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-10-18 3:52:49 3836 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-10-18 3:52:49 3836 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-10-18 3:52:49 3836 [Note] InnoDB: Using generic crc32 instructions
2017-10-18 3:52:49 3836 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-10-18 3:52:49 3836 [Note] InnoDB: Completed initialization of buffer pool
2017-10-18 3:52:49 3836 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-10-18 3:52:49 3836 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-10-18 3:52:49 3836 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2017-10-18 3:52:49 3836 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-10-18 3:52:49 3836 [ERROR] Plugin 'InnoDB' init function returned error.
2017-10-18 3:52:49 3836 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-10-18 3:52:49 3836 [Note] Plugin 'FEEDBACK' is disabled.
2017-10-18 3:52:49 3836 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-10-18 3:52:49 3836 [ERROR] Aborting
I have tried reinitilizing mysql data folder, deleting ibdata1, ib_log files from it, without any success.
Any suggestions are much appreciated.
Solved by Install 5.6.35 / PHP 5.6.35 - XAMPP
Have same issue by using windows 10, xampp 7.2.2.
took backup of htdocs projects
uninstalled XAMPP 7.2.x
installed XAMPP 5.6.x
pasted backup projects to htdocs
got Apache port number issue, then change 80 to 8080 in httpd.conf
works fine !
XAMPP MySQL is not running
Solution->
1.Open cmd and type 'services.msc'
2.Service panel will be opened within 5 seconds
3.Now search for anyother sql server which is still running
4.Select all the sql servers and stop them one by one service(There could be more than one)
5.Finally refresh your computer and start MySQL
6.Enjoy
Hope it will run successfully now :=)

AWS Micro Instance - MySQL keeps failing in Wordpress installation

I have a Ubuntu micro instance with default settings. As a matter of fact, this instance is the same as 8 others I have created prior and since to host Wordpress websites.
This one belongs to a Church, and unfortunately, it keeps having its MySql server going to heaven! I am not sure how to sort this, as the mysql.err log shows:
160301 5:03:40 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in$
160301 5:03:40 [Note] Plugin 'FEDERATED' is disabled.
160301 5:03:40 InnoDB: The InnoDB memory heap is disabled
160301 5:03:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160301 5:03:40 InnoDB: Compressed tables use zlib 1.2.8
160301 5:03:40 InnoDB: Using Linux native AIO
160301 5:03:40 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
160301 5:03:40 InnoDB: Completed initialization of buffer pool
160301 5:03:40 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160301 5:03:40 [ERROR] Plugin 'InnoDB' init function returned error.
160301 5:03:40 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160301 5:03:40 [ERROR] Unknown/unsupported storage engine: InnoDB
160301 5:03:40 [ERROR] Aborting
160301 5:03:40 [Note] /usr/sbin/mysqld: Shutdown complete
This is telling me it could not allocate the 128MB required for the buffer pool.
But, my free -m shows there is plenty of memory for this (I also set up a 2GB swap).
ubuntu#ip-xxx-xxx-xxx-xxx:/var/log/mysql$ free -m
total used free shared buffers cached
Mem: 992 634 358 54 76 308
-/+ buffers/cache: 249 742
Swap: 2047 0 2047
Any suggestions are appreciated!
Looks like there is not enough memory left for allocation during the start process.
add this to your /etc/mysql/my.cnf
innodb_buffer_pool_size = 20M

XAMPP v3.2.1 - Error: MySQL shutdown unexpectedly

Hi and thanks for helping.
For some reason MySQL is not working on my XAMPP, I run it as administrator in Windows 10 and its not installed on the default "program files" folder. Here is the console error:
17:01:11 [mysql] Error: MySQL shutdown unexpectedly.
17:01:11 [mysql] This may be due to a blocked port, missing dependencies,
17:01:11 [mysql] improper privileges, a crash, or a shutdown by another method.
17:01:11 [mysql] Press the Logs button to view error logs and check
17:01:11 [mysql] the Windows Event Viewer for more clues
17:01:11 [mysql] If you need more help, copy and post this
17:01:11 [mysql] entire log window on the forums
And here is the log:
2015-11-04 17:01:06 25a4 InnoDB: Warning: Using innodb_additional_mem_pool_size 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.
151104 17:01:06 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151104 17:01:06 [Note] InnoDB: The InnoDB memory heap is disabled
151104 17:01:06 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
151104 17:01:06 [Note] InnoDB: Memory barrier is not used
151104 17:01:06 [Note] InnoDB: Compressed tables use zlib 1.2.3
151104 17:01:06 [Note] InnoDB: Not using CPU crc32 instructions
151104 17:01:06 [Note] InnoDB: Initializing buffer pool, size = 16.0M
151104 17:01:06 [Note] InnoDB: Completed initialization of buffer pool
151104 17:01:06 [Note] InnoDB: The first specified data file E:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
151104 17:01:06 [Note] InnoDB: Setting file E:\xampp\mysql\data\ibdata1 size to 10 MB
151104 17:01:06 [Note] InnoDB: Database physically writes the file full: wait...
151104 17:01:06 [ERROR] InnoDB: Cannot create E:\xampp\mysql\data\ib_logfile101
151104 17:01:06 [ERROR] Plugin 'InnoDB' init function returned error.
151104 17:01:06 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151104 17:01:06 [Note] Plugin 'FEEDBACK' is disabled.
151104 17:01:06 [ERROR] Unknown/unsupported storage engine: InnoDB
151104 17:01:06 [ERROR] Aborting
151104 17:01:06 [Note] E:\xampp\mysql\bin\mysqld.exe: Shutdown complete
I would appreciate any help, thanks.

Recover DB from ibdata1, ib_logfile0, ib_logfile1 and .frm files

Recently My production server was corrupted due to maintenance shutdown by digital ocean. When we trying to recover our database we couldn't access our droplet. Somehow we managed to recover these (ibdata1, ib_logfile0, ib_logfile1 and some .frm) files. When i copied this files to my new mysql server(in another machine), I could't start the mysql server. I got this output
sudo service mysql restart
mysql stop/waiting
start: Job failed to start
I checked the log file and i got this error,
151019 8:55:27 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:27 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:27 InnoDB: The InnoDB memory heap is disabled
151019 8:55:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:27 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:27 InnoDB: Using Linux native AIO
151019 8:55:27 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:27 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:27 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:27 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:27 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:27 [ERROR] Aborting
151019 8:55:27 [Note] /usr/sbin/mysqld: Shutdown complete
151019 8:55:28 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:28 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:28 InnoDB: The InnoDB memory heap is disabled
151019 8:55:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:28 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:28 InnoDB: Using Linux native AIO
151019 8:55:28 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:28 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:28 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:28 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:28 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:28 [ERROR] Aborting
151019 8:55:28 [Note] /usr/sbin/mysqld: Shutdown complete
151019 8:55:29 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:29 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:29 InnoDB: The InnoDB memory heap is disabled
151019 8:55:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:29 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:29 InnoDB: Using Linux native AIO
151019 8:55:29 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:29 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:29 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:29 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:29 [ERROR] Aborting
151019 8:55:29 [Note] /usr/sbin/mysqld: Shutdown complete
I tried adding innodb_log_file_size= 50331648 as suggested by #akuzminsky
Then I got this error log.
151022 6:54:13 [Warning] Using unique option prefix myisam-recover instead of $
151022 6:54:13 [Note] Plugin 'FEDERATED' is disabled.
151022 6:54:13 InnoDB: The InnoDB memory heap is disabled
151022 6:54:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151022 6:54:13 InnoDB: Compressed tables use zlib 1.2.8
151022 6:54:13 InnoDB: Using Linux native AIO
151022 6:54:13 InnoDB: Initializing buffer pool, size = 128.0M
151022 6:54:13 InnoDB: Completed initialization of buffer pool
151022 6:54:13 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 15379293
151022 6:54:13 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: space header page consists of zero bytes in file ./toucan/ormcli$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/catego$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/survey$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/compla$
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 15382291
InnoDB: Page directory corruption: infimum not pointed to
151022 6:54:13 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 10cfd0d80000000000000000000000000000000000e9e915000800000000001$
InnoDB: End of page dump
151022 6:54:13 InnoDB: Page checksum 282054872, prior-to-4.0.14-form checksum$
InnoDB: stored checksum 282054872, prior-to-4.0.14-form stored checksum 3468306$
InnoDB: Page lsn 0 15329557, low 4 bytes of lsn at page end 15329557
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a file space header page
10:54:13 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 K $
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fa4d90e2f10]
/usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fa4d8fcd175]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa4d7d5d340]
/usr/sbin/mysqld(+0x5f058a)[0x7fa4d91e258a]
/usr/sbin/mysqld(+0x56c44e)[0x7fa4d915e44e]
/usr/sbin/mysqld(+0x576137)[0x7fa4d9168137]
/usr/sbin/mysqld(+0x5a5632)[0x7fa4d9197632]
/usr/sbin/mysqld(+0x5a6699)[0x7fa4d9198699]
/usr/sbin/mysqld(+0x591ad3)[0x7fa4d9183ad3]
/usr/sbin/mysqld(+0x542a1a)[0x7fa4d9134a1a]
/usr/sbin/mysqld(+0x511d48)[0x7fa4d9103d48]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fa4d8fcf$
/usr/sbin/mysqld(+0x302221)[0x7fa4d8ef4221]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x92a)[0x7fa4d8ef821a]
/usr/sbin/mysqld(+0x28ac5b)[0x7fa4d8e7cc5b]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fa4d8e815db]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fa4d739fec5]
/usr/sbin/mysqld(+0x286b18)[0x7fa4d8e78b18]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Please help me to resolve this.
Thanks in advance.
Note lines in the error log:
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
The actual size of the redo log file differs from the size in MySQL config.
Add this line to my.cnf
innodb_log_file_size= 50331648
If the tablespace is corrupted you'll still have to heal it. But at least MySQL won't stop at this step.

Windows 10 Enterprise - MYSQL shutdown unexpectedly

I've installed Windows 10 Enterprise 64bit on machine and attempting to install Apache, PHP and MySQL on my machine to use for web development. In short I keep running into an error "MySQL shutdown unexpectedly". I've attempted to install using WAMP and XAMPP on my machine and still run into the same error. Apache connects and works on both WAMP and XAMPP however I get the same MySQL error.
So far from all the research I've done please find a synopsis of my situation and the solutions I've tried. I'm thinking this is to do with Windows 10. Also as a side note I'm using bootcamp on my MacBook 12 inch so not sure if this adding to the problem but I would not have thought so.
Apache running on port 80:433 for both XAMPP and WAMP
WAMP - Mysql -> service, start/resume service is green. When I click on it nothing happens. XAMP I get:
8:50:59 AM [mysql] Error: MySQL shutdown unexpectedly.
8:50:59 AM [mysql] This may be due to a blocked port, missing dependencies,
8:50:59 AM [mysql] improper privileges, a crash, or a shutdown by another method.
8:50:59 AM [mysql] Press the Logs button to view error logs and check
8:50:59 AM [mysql] the Windows Event Viewer for more clues
8:50:59 AM [mysql] If you need more help, copy and post this
8:50:59 AM [mysql] entire log window on the forums
Turned off windows firewall, same errors
4.I've checked for skype but it is actually not installed on my machine.Also checked control panel -> view local services, skype is not there nor running Tried netstat-b in the command prompt and I can't see anything with port 80. Also tried netstat -aon | findstr :80, only TCP 192.168.0.10:49556 23.205.116.42:80 ESTABLISHED 1884. Note: If the port was an issue Apache should not be working
I checked the control panel -> view local services there is no World Wide Web Publishing Service.
Followed solution in Xamp-Mysql Shutdown which included deleting ib_logfile1, ib_logfile and ibdata1. As well as appending my.ini with innodb_force_recovery = 1. I get a slightly different error which I put below.
I'm pretty much out of options and about to give into the fact that MySQL may not work on my windows 10 machine. But before I do any help would be appreciated.
Error Logs:
2015-08-08 08:31:08 7024 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 08:31:08 18ec InnoDB: Warning: Using innodb_additional_mem_pool_size 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.
2015-08-08 08:31:08 7024 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 08:31:08 7024 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 08:31:08 7024 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 08:31:08 7024 [Note] InnoDB: Memory barrier is not used
2015-08-08 08:31:08 7024 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 08:31:08 7024 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 08:31:08 7024 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 08:31:08 7024 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 08:31:08 7024 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-08 08:31:08 18ec InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-08-08 08:31:08 7024 [ERROR] InnoDB: File C:\wamp\mysql\data\ib_logfile0: 'aio read' returned
Error Log # innodb_force_recovery = 1
2015-08-08 09:32:05 3804 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 09:32:05 1bf8 InnoDB: Warning: Using innodb_additional_mem_pool_size 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.
2015-08-08 09:32:05 3804 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 09:32:05 3804 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 09:32:05 3804 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 09:32:05 3804 [Note] InnoDB: Memory barrier is not used
2015-08-08 09:32:05 3804 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 09:32:05 3804 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 09:32:05 3804 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 09:32:05 3804 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 09:32:05 3804 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2015-08-08 09:32:05 3804 [Note] InnoDB: Database physically writes the file full: wait...
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2015-08-08 09:32:05 1bf8 InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-08-08 09:32:05 3804 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation
This solution worked for me.
Uninstall XAMPP and WAMP
Installed WAMP 64bit
Added the following line to my.ini
innodb_flush_method=normal
Closed WAMP and restarted. Logo W is green and working.
Thank you to: Error 187