Search found 86 matches: ntdll.dll

Searched query: +ntdll +dll

Return to advanced search

Error: MySQL shutdown unexpectedly.

i've tried many things to solve this problem but i can't find anything on the internet that can solve my problem. The problem is that i can't start mysql on XAMPP and that's verry anoying. Maybe can you guys help me?

Here is my error log:

2015-11-10 15:26:56 10fc 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-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2018-06-07 20:14:45 27b8 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.
2018-06-07 20:14:45 10168 [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.

2018-06-07 20:14:45 10168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-07 20:14:45 10168 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-07 20:14:45 10168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-07 20:14:45 10168 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-07 20:14:45 10168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-07 20:14:45 10168 [Note] InnoDB: Using generic crc32 instructions
2018-06-07 20:14:45 10168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-07 20:14:45 10168 [Note] InnoDB: Completed initialization of buffer pool
2018-06-07 20:14:45 10168 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-07 20:14:45 27b8 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-07 20:14:45 10168 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180607 20:14:45 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-07 21:59:02 33bc 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.
2018-06-07 21:59:02 13244 [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.

2018-06-07 21:59:02 13244 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-07 21:59:02 13244 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-07 21:59:02 13244 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-07 21:59:02 13244 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-07 21:59:02 13244 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-07 21:59:02 13244 [Note] InnoDB: Using generic crc32 instructions
2018-06-07 21:59:02 13244 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-07 21:59:02 13244 [Note] InnoDB: Completed initialization of buffer pool
2018-06-07 21:59:02 13244 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-07 21:59:02 33bc 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-07 21:59:02 13244 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180607 21:59:02 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-07 22:00:02 2dac 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.
2018-06-07 22:00:02 11692 [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.

2018-06-07 22:00:02 11692 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-07 22:00:02 11692 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-07 22:00:02 11692 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-07 22:00:02 11692 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-07 22:00:02 11692 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-07 22:00:02 11692 [Note] InnoDB: Using generic crc32 instructions
2018-06-07 22:00:02 11692 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-07 22:00:02 11692 [Note] InnoDB: Completed initialization of buffer pool
2018-06-07 22:00:02 11692 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-07 22:00:02 2dac 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-07 22:00:02 11692 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180607 22:00:02 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-08 22:33:33 b94 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.
2018-06-08 22:33:33 2964 [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.

2018-06-08 22:33:33 212c 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.
2018-06-08 22:33:33 8492 [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.

2018-06-08 22:33:33 2964 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-08 22:33:33 2964 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-08 22:33:33 2964 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-08 22:33:33 2964 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-08 22:33:33 2964 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-08 22:33:33 2964 [Note] InnoDB: Using generic crc32 instructions
2018-06-08 22:33:33 2964 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-08 22:33:33 2964 [Note] InnoDB: Completed initialization of buffer pool
2018-06-08 22:33:33 8492 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-08 22:33:33 8492 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-08 22:33:33 8492 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-08 22:33:33 8492 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-08 22:33:33 8492 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-08 22:33:33 8492 [Note] InnoDB: Using generic crc32 instructions
2018-06-08 22:33:33 8492 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-08 22:33:33 8492 [Note] InnoDB: Completed initialization of buffer pool
2018-06-08 22:33:33 8492 [ERROR] InnoDB: D:\XAMPP\mysql\data\ibdata1 can't be opened in read-write mode
2018-06-08 22:33:33 8492 [ERROR] InnoDB: The system tablespace must be writable!
2018-06-08 22:33:33 8492 [ERROR] Plugin 'InnoDB' init function returned error.
2018-06-08 22:33:33 8492 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-06-08 22:33:33 8492 [Note] Plugin 'FEEDBACK' is disabled.
2018-06-08 22:33:33 8492 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-06-08 22:33:33 8492 [ERROR] Aborting

2018-06-08 22:33:33 2964 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-08 22:33:33 b94 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-08 22:33:33 2964 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180608 22:33:33 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-08 22:35:44 24d0 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.
2018-06-08 22:35:44 9424 [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.

2018-06-08 22:35:44 9424 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-08 22:35:44 9424 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-08 22:35:44 9424 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-08 22:35:44 9424 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-08 22:35:44 9424 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-08 22:35:44 9424 [Note] InnoDB: Using generic crc32 instructions
2018-06-08 22:35:44 9424 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-08 22:35:44 9424 [Note] InnoDB: Completed initialization of buffer pool
2018-06-08 22:35:44 9424 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-08 22:35:44 24d0 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-08 22:35:44 9424 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180608 22:35:44 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-08 22:35:55 19b0 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.
2018-06-08 22:35:55 6576 [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.

2018-06-08 22:35:55 6576 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-08 22:35:55 6576 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-08 22:35:55 6576 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-08 22:35:55 6576 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-08 22:35:55 6576 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-08 22:35:55 6576 [Note] InnoDB: Using generic crc32 instructions
2018-06-08 22:35:55 6576 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-08 22:35:55 6576 [Note] InnoDB: Completed initialization of buffer pool
2018-06-08 22:35:55 6576 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-08 22:35:55 19b0 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-08 22:35:55 6576 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180608 22:35:55 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-08 22:38:31 1a68 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.
2018-06-08 22:38:31 6760 [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.

2018-06-08 22:38:31 6760 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-08 22:38:31 6760 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-08 22:38:31 6760 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-08 22:38:31 6760 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-08 22:38:31 6760 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-08 22:38:31 6760 [Note] InnoDB: Using generic crc32 instructions
2018-06-08 22:38:31 6760 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-08 22:38:31 6760 [Note] InnoDB: Completed initialization of buffer pool
2018-06-08 22:38:31 6760 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-08 22:38:31 1a68 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-08 22:38:31 6760 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180608 22:38:31 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-08 22:38:45 2b68 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.
2018-06-08 22:38:45 11112 [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.

2018-06-08 22:38:45 11112 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-08 22:38:45 11112 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-08 22:38:45 11112 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-08 22:38:45 11112 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-08 22:38:45 11112 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-08 22:38:45 11112 [Note] InnoDB: Using generic crc32 instructions
2018-06-08 22:38:45 11112 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-08 22:38:45 11112 [Note] InnoDB: Completed initialization of buffer pool
2018-06-08 22:38:45 11112 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-08 22:38:45 2b68 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-08 22:38:45 11112 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180608 22:38:45 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-08 22:44:13 1c20 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.
2018-06-08 22:44:13 7200 [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.

2018-06-08 22:44:13 7200 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-08 22:44:13 7200 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-08 22:44:13 7200 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-08 22:44:13 7200 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-08 22:44:13 7200 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-08 22:44:13 7200 [Note] InnoDB: Using generic crc32 instructions
2018-06-08 22:44:13 7200 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-08 22:44:13 7200 [Note] InnoDB: Completed initialization of buffer pool
2018-06-08 22:44:13 7200 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-08 22:44:13 1c20 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-08 22:44:13 7200 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180608 22:44:13 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-08 23:01:20 20e0 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.
2018-06-08 23:01:20 8416 [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.

2018-06-08 23:01:20 8416 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-08 23:01:20 8416 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-08 23:01:20 8416 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-08 23:01:20 8416 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-08 23:01:20 8416 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-08 23:01:20 8416 [Note] InnoDB: Using generic crc32 instructions
2018-06-08 23:01:20 8416 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-08 23:01:20 8416 [Note] InnoDB: Completed initialization of buffer pool
2018-06-08 23:01:20 8416 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-08 23:01:20 20e0 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-08 23:01:20 8416 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180608 23:01:20 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-06-09 21:18:52 21d8 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.
2018-06-09 21:18:52 8664 [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.

2018-06-09 21:18:52 8664 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-06-09 21:18:52 8664 [Note] InnoDB: The InnoDB memory heap is disabled
2018-06-09 21:18:52 8664 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-09 21:18:52 8664 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-06-09 21:18:52 8664 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-09 21:18:52 8664 [Note] InnoDB: Using generic crc32 instructions
2018-06-09 21:18:52 8664 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-06-09 21:18:52 8664 [Note] InnoDB: Completed initialization of buffer pool
2018-06-09 21:18:52 8664 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-09 21:18:52 21d8 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3216
2018-06-09 21:18:52 8664 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180609 21:18:52 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.32-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!thd_key_delete()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?free_frm_image@TABLE_SHARE@@QAEXPBE@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_result_field@Item@@UAEXPAVField@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
by BrinkBoef
09. June 2018 20:34
 
Forum: XAMPP for Windows
Topic: Error: MySQL shutdown unexpectedly.
Replies: 0
Views: 113

MYSQL shutdown unexpectedly in Window10

2015-11-10 15:26:56 10fc 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-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2018-03-15 10:05:47 1878 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.
2018-03-15 10:05:47 6264 [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.

2018-03-15 10:05:47 6264 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:05:47 6264 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:05:47 6264 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:05:47 6264 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:05:47 6264 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:05:47 6264 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:05:47 6264 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:05:47 6264 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:05:47 6264 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-15 10:05:48 6264 [Note] InnoDB: 128 rollback segment(s) are active.
2018-03-15 10:05:48 6264 [Note] InnoDB: Waiting for purge to start
2018-03-15 10:05:48 6264 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1835037
2018-03-15 10:05:48 5148 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-03-15 10:05:48 6264 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-15 10:05:48 6264 [Note] Server socket created on IP: '::'.
2018-03-15 10:05:48 6264 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2018-03-15 10:05:48 6264 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2018-03-15 10:05:48 6264 [ERROR] Aborting

2018-03-15 10:06:39 a44 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.
2018-03-15 10:06:39 2628 [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.

2018-03-15 10:06:39 2628 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:06:39 2628 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:06:39 2628 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:06:39 2628 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:06:39 2628 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:06:39 2628 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:06:39 2628 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:06:39 2628 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:06:39 2628 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-15 10:06:39 2628 [Note] InnoDB: 128 rollback segment(s) are active.
2018-03-15 10:06:39 2628 [Note] InnoDB: Waiting for purge to start
2018-03-15 10:06:39 2628 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1835047
2018-03-15 10:06:39 3792 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-03-15 10:06:39 2628 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-15 10:06:39 2628 [Note] Server socket created on IP: '::'.
2018-03-15 10:06:39 2628 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.


2018-03-15 10:06:39 2628 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2018-03-15 10:06:39 2628 [ERROR] Aborting

2018-03-15 10:08:59 1094 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.
2018-03-15 10:08:59 4244 [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.

2018-03-15 10:08:59 4244 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:08:59 4244 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:08:59 4244 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:08:59 4244 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:08:59 4244 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:08:59 4244 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:08:59 4244 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:08:59 4244 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:08:59 4244 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2018-03-15 10:08:59 4244 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2018-03-15 10:08:59 4244 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2018-03-15 10:08:59 4244 [ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile1
2018-03-15 10:08:59 4244 [ERROR] Plugin 'InnoDB' init function returned error.
2018-03-15 10:08:59 4244 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-03-15 10:08:59 4244 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-15 10:08:59 4244 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-03-15 10:08:59 4244 [ERROR] Aborting

2018-03-15 10:11:10 1bb4 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.
2018-03-15 10:11:10 7092 [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.

2018-03-15 10:11:10 7092 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:11:10 7092 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:11:10 7092 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:11:10 7092 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:11:10 7092 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:11:10 7092 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:11:10 7092 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:11:10 7092 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:11:10 7092 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-15 10:11:10 7092 [Note] InnoDB: The log sequence number 0 in ibdata file do not match the log sequence number 1835057 in the ib_logfiles!
2018-03-15 10:11:11 1bb4 InnoDB: Assertion failure in thread 7092 in file fsp0fsp.cc line 1880
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
180315 10:11:11 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.30-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!no_key()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?str_result@Item@@UAEPAVString@@PAV2@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlSetCurrentTransaction()
ntdll.dll!RtlSetCurrentTransaction()
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.
2018-03-15 10:11:21 1528 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.
2018-03-15 10:11:21 5416 [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.

2018-03-15 10:11:21 5416 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:11:21 5416 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:11:21 5416 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:11:21 5416 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:11:21 5416 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:11:21 5416 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:11:22 5416 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:11:22 5416 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:11:22 5416 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-15 10:11:22 5416 [Note] InnoDB: The log sequence number 0 in ibdata file do not match the log sequence number 1835057 in the ib_logfiles!
2018-03-15 10:11:22 1528 InnoDB: Assertion failure in thread 5416 in file fsp0fsp.cc line 1880
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
180315 10:11:22 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.30-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!no_key()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?str_result@Item@@UAEPAVString@@PAV2@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlSetCurrentTransaction()
ntdll.dll!RtlSetCurrentTransaction()
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.
2018-03-15 10:11:38 d1c 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.
2018-03-15 10:11:38 3356 [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.

2018-03-15 10:11:38 3356 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:11:38 3356 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:11:38 3356 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:11:38 3356 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:11:38 3356 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:11:38 3356 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:11:38 3356 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:11:38 3356 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:11:38 3356 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-15 10:11:38 3356 [Note] InnoDB: The log sequence number 0 in ibdata file do not match the log sequence number 1835057 in the ib_logfiles!
2018-03-15 10:11:38 d1c InnoDB: Assertion failure in thread 3356 in file fsp0fsp.cc line 1880
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
180315 10:11:38 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.30-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!no_key()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?str_result@Item@@UAEPAVString@@PAV2@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlSetCurrentTransaction()
ntdll.dll!RtlSetCurrentTransaction()
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.
2018-03-15 10:14:59 19d0 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.
2018-03-15 10:14:59 6608 [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.

2018-03-15 10:15:00 6608 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:15:00 6608 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:15:00 6608 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:15:00 6608 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:15:00 6608 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:15:00 6608 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:15:00 6608 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:15:00 6608 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:15:00 6608 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-03-15 10:15:00 6608 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-03-15 10:15:00 6608 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2018-03-15 10:15:00 6608 [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!
2018-03-15 10:15:00 6608 [ERROR] Plugin 'InnoDB' init function returned error.
2018-03-15 10:15:00 6608 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-03-15 10:15:00 6608 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-15 10:15:00 6608 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-03-15 10:15:00 6608 [ERROR] Aborting

2018-03-15 10:21:47 6860 [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.

2018-03-15 10:21:47 6860 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:21:47 6860 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:21:47 6860 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:21:47 6860 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:21:47 6860 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:21:47 6860 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:21:47 6860 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:21:47 6860 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:21:47 6860 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-03-15 10:21:47 6860 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-03-15 10:21:47 6860 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2018-03-15 10:21:47 6860 [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!
2018-03-15 10:21:47 6860 [ERROR] Plugin 'InnoDB' init function returned error.
2018-03-15 10:21:47 6860 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-03-15 10:21:47 6860 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-15 10:21:47 6860 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-03-15 10:21:47 6860 [ERROR] Aborting

2018-03-15 10:29:56 5872 [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.

2018-03-15 10:29:56 5872 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-15 10:29:56 5872 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-15 10:29:56 5872 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-15 10:29:56 5872 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-15 10:29:56 5872 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-15 10:29:56 5872 [Note] InnoDB: Using generic crc32 instructions
2018-03-15 10:29:56 5872 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-15 10:29:56 5872 [Note] InnoDB: Completed initialization of buffer pool
2018-03-15 10:29:56 5872 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-03-15 10:29:56 5872 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-03-15 10:29:56 5872 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2018-03-15 10:29:56 5872 [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!
2018-03-15 10:29:56 5872 [ERROR] Plugin 'InnoDB' init function returned error.
2018-03-15 10:29:56 5872 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-03-15 10:29:57 5872 [Note] Plugin 'FEEDBACK' is disabled.
2018-03-15 10:29:57 5872 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-03-15 10:29:57 5872 [ERROR] Aborting
by dgupta330
15. March 2018 06:00
 
Forum: XAMPP for Windows
Topic: MYSQL shutdown unexpectedly in Window10
Replies: 1
Views: 551

MySQL startet nicht

Ich habe auch das Problem, dass sich MySQL nicht starten lässt.

Error Log:

2015-11-10 15:26:56 10fc 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-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2018-01-27 11:14:17 1f10 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.
2018-01-27 11:14:17 7952 [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.

2018-01-27 11:14:17 7952 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-01-27 11:14:17 7952 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-27 11:14:17 7952 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-01-27 11:14:17 7952 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-01-27 11:14:17 7952 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-27 11:14:17 7952 [Note] InnoDB: Using generic crc32 instructions
2018-01-27 11:14:17 7952 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-01-27 11:14:17 7952 [Note] InnoDB: Completed initialization of buffer pool
2018-01-27 11:14:18 7952 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-27 11:14:18 1f10 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3199
2018-01-27 11:14:18 7952 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180127 11:14:18 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.30-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?str_result@Item@@UAEPAVString@@PAV2@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
2018-01-27 11:14:26 11c8 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.
2018-01-27 11:14:26 4552 [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.

2018-01-27 11:14:26 4552 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-01-27 11:14:26 4552 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-27 11:14:26 4552 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-01-27 11:14:26 4552 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-01-27 11:14:26 4552 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-27 11:14:26 4552 [Note] InnoDB: Using generic crc32 instructions
2018-01-27 11:14:26 4552 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-01-27 11:14:26 4552 [Note] InnoDB: Completed initialization of buffer pool
2018-01-27 11:14:26 4552 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-27 11:14:26 11c8 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
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3199
2018-01-27 11:14:26 4552 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180127 11:14:26 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.30-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?str_result@Item@@UAEPAVString@@PAV2@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
by TobiWimma
27. January 2018 11:17
 
Forum: XAMPP für Windows
Topic: MySQL startet nicht
Replies: 13
Views: 1519

MySQL startet nicht

Hallo zusammen,

mein MYSQL startet plötzlich nicht mehr. Wenige Minuten davor lief es noch, jetzt kommt folgende Meldung:18:47:46 [mysql] Versuche MySQL zu starten...
18:47:46 [mysql] Statusänderung erkannt: gestartet
18:47:47 [mysql] Statusänderung erkannt: gestoppt
18:47:47 [mysql] Fehler: MySQL wurde unerwartet beendet
18:47:47 [mysql] Ursache könnte ein geblockter Port, fehlende Abhängigkeiten,
18:47:47 [mysql] fehlende Berechtigungen, ein Absturz oder ein Abbruch einer anderen Methode sein.
18:47:47 [mysql] Drücke den Logs Button um error logs zu sehen und prüfe
18:47:47 [mysql] im Windows Event Viewer für weitere Hinweise
18:47:47 [mysql] Wenn du weitere Hilfe benötigst, kopiere den kompletten Inhalt des Log Fensters
18:47:47 [mysql] und füge ihn als Ergänzung in einem neuen Forum Eintrag hinzu.

Im Log steht Folgendes:
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-11-15 18:18:15 1b04 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-11-15 18:18:15 6916 [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-11-15 18:18:15 6916 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:18:15 6916 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:18:15 6916 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:18:15 6916 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:18:15 6916 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:18:15 6916 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:18:15 6916 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:18:15 6916 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:18:15 6916 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-15 18:18:15 6916 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 13218450 in the ib_logfiles!
2017-11-15 18:18:15 6916 [Note] InnoDB: Database was not shutdown normally!
2017-11-15 18:18:15 6916 [Note] InnoDB: Starting crash recovery.
2017-11-15 18:18:15 6916 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-11-15 18:18:16 6916 [Note] InnoDB: Restoring possible half-written data pages
2017-11-15 18:18:16 6916 [Note] InnoDB: from the doublewrite buffer...
2017-11-15 18:18:16 6916 [Note] InnoDB: 128 rollback segment(s) are active.
2017-11-15 18:18:16 6916 [Note] InnoDB: Waiting for purge to start
2017-11-15 18:18:16 6916 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 13218450
2017-11-15 18:18:16 1252 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-11-15 18:18:16 6916 [Note] Plugin 'FEEDBACK' is disabled.
2017-11-15 18:18:16 6916 [Note] Server socket created on IP: '::'.
2017-11-15 18:18:16 6916 [Note] c:\users\lhian\onedrive\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-11-15 18:39:37 1c48 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-11-15 18:39:37 7240 [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-11-15 18:39:37 7240 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:39:37 7240 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:39:37 7240 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:39:37 7240 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:39:37 7240 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:39:37 7240 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:39:37 7240 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:39:37 7240 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:39:37 7240 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-15 18:39:37 7240 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 14225262 in the ib_logfiles!
2017-11-15 18:39:37 7240 [Note] InnoDB: Database was not shutdown normally!
2017-11-15 18:39:37 7240 [Note] InnoDB: Starting crash recovery.
2017-11-15 18:39:37 7240 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-11-15 18:39:37 7240 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_wordpress/wp_options-DESKTOP-L9K8C9Q uses space ID: 39 at filepath: .\bitnami_wordpress\wp_options-desktop-l9k8c9q.ibd. Cannot open tablespace bitnami_wordpress/wp_options which uses space ID: 39 at filepath: .\bitnami_wordpress\wp_options.ibd
InnoDB: Error: could not open single-table tablespace file .\bitnami_wordpress\wp_options.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
171115 18:39:37 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.21-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787106 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!my_wildcmp_mb_bin()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?set_required_privilege@Settable_routine_parameter@@UAEX_N@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!my_wildcmp_mb_bin()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
2017-11-15 18:39:47 1a1c 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-11-15 18:39:47 6684 [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-11-15 18:39:47 6684 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:39:47 6684 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:39:47 6684 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:39:47 6684 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:39:47 6684 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:39:47 6684 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:39:47 6684 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:39:47 6684 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:39:47 6684 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-15 18:39:47 6684 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 14225262 in the ib_logfiles!
2017-11-15 18:39:47 6684 [Note] InnoDB: Database was not shutdown normally!
2017-11-15 18:39:47 6684 [Note] InnoDB: Starting crash recovery.
2017-11-15 18:39:47 6684 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-11-15 18:39:47 6684 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_wordpress/wp_options-DESKTOP-L9K8C9Q uses space ID: 39 at filepath: .\bitnami_wordpress\wp_options-desktop-l9k8c9q.ibd. Cannot open tablespace bitnami_wordpress/wp_options which uses space ID: 39 at filepath: .\bitnami_wordpress\wp_options.ibd
InnoDB: Error: could not open single-table tablespace file .\bitnami_wordpress\wp_options.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
171115 18:39:47 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.21-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787106 K bytes of memory
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!my_wildcmp_mb_bin()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?set_required_privilege@Settable_routine_parameter@@UAEX_N@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!my_wildcmp_mb_bin()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
2017-11-15 18:47:18 44c 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-11-15 18:47:18 1100 [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-11-15 18:47:18 1100 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:47:18 1100 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:47:18 1100 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:47:18 1100 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:47:18 1100 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:47:18 1100 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:47:18 1100 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:47:18 1100 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:47:18 1100 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-11-15 18:47:18 1100 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-11-15 18:47:18 1100 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\lhian\OneDrive\XAMPP\mysql\data\ibdata1
2017-11-15 18:47:18 1100 [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-11-15 18:47:18 1100 [ERROR] Plugin 'InnoDB' init function returned error.
2017-11-15 18:47:18 1100 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-11-15 18:47:18 1100 [Note] Plugin 'FEEDBACK' is disabled.
2017-11-15 18:47:18 1100 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-11-15 18:47:18 1100 [ERROR] Aborting

2017-11-15 18:47:29 2df4 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-11-15 18:47:29 11764 [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-11-15 18:47:29 11764 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:47:29 11764 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:47:29 11764 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:47:29 11764 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:47:29 11764 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:47:29 11764 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:47:29 11764 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:47:29 11764 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:47:29 11764 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-11-15 18:47:29 11764 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-11-15 18:47:29 11764 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\lhian\OneDrive\XAMPP\mysql\data\ibdata1
2017-11-15 18:47:29 11764 [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-11-15 18:47:29 11764 [ERROR] Plugin 'InnoDB' init function returned error.
2017-11-15 18:47:29 11764 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-11-15 18:47:29 11764 [Note] Plugin 'FEEDBACK' is disabled.
2017-11-15 18:47:29 11764 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-11-15 18:47:29 11764 [ERROR] Aborting

2017-11-15 18:47:46 2154 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-11-15 18:47:46 8532 [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-11-15 18:47:46 8532 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:47:46 8532 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:47:46 8532 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:47:46 8532 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:47:46 8532 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:47:46 8532 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:47:46 8532 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:47:46 8532 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:47:46 8532 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-11-15 18:47:46 8532 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-11-15 18:47:46 8532 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\lhian\OneDrive\XAMPP\mysql\data\ibdata1
2017-11-15 18:47:46 8532 [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-11-15 18:47:46 8532 [ERROR] Plugin 'InnoDB' init function returned error.
2017-11-15 18:47:46 8532 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-11-15 18:47:46 8532 [Note] Plugin 'FEEDBACK' is disabled.
2017-11-15 18:47:46 8532 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-11-15 18:47:46 8532 [ERROR] Aborting


Kann mir jemand weiterhelfen? Ich muss morgen mein Arbeitsergebnis präsentieren und stehe jetzt völlig auf dem Schlauch.

Danke schonmal!
by llia
15. November 2017 18:52
 
Forum: XAMPP für Windows
Topic: MySQL startet nicht
Replies: 1
Views: 1619

Re: Apache suddenly stops working

I have the same problem:

Faulting application name: httpd.exe, version: 2.4.23.0, time stamp: 0x577631b1
Faulting module name: ntdll.dll, version: 6.1.7601.23864, time stamp: 0x595fa490
Exception code: 0xc0000374
Fault offset: 0x000ce8fb
Faulting process id: 0xa54
Faulting application start time: 0x01d310fdecddb997
Faulting application path: C:\xampp\apache\bin\httpd.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: ba3f5bfe-7cfe-11e7-b6a1-005056864a79

other info:

Informazioni di sistema
Impostazione Valore

PHP attivo su Windows NT SRVPORT1 6.1 build 7601 (Windows Server 2008 R2 Datacenter Edition Service Pack 1) i586
Versione database 5.5.5-10.1.16-MariaDB
Collation database utf8_general_ci
Collation connessione database utf8mb4_general_ci
Versione PHP 7.0.9
Web Server Apache/2.4.23 (Win32) OpenSSL/1.0.2h PHP/7.0.9
WebServer interfaccia PHP apache2handler
Versione di Joomla! Joomla! 3.6.5 Stable [ Noether ] 1-December-2016 22:46 GMT
Versione piattaforma Joomla! Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
by nirovi
14. September 2017 08:35
 
Forum: XAMPP for Windows
Topic: Apache suddenly stops working
Replies: 1
Views: 2108

CLI has stopped responding

When I enter "php -v" on command line administrator, a window appears saying "CLI has stopped responding".
Because of this I cannot install Composer.

Below is what Event Viewer says.
Code: Select all
Faulting application name: php.exe, version: 5.6.30.0, time stamp: 0x5880378d
Faulting module name: ntdll.dll, version: 6.3.9600.18696, time stamp: 0x5915ecd6
Exception code: 0xc0000005
Fault offset: 0x00040f17
Faulting process ID: 0x15c8
Faulting application start time: 0x01d2ef52226ae6a9
Faulting application path: C:\xampp\php\php.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 609ab573-5b45-11e7-82a8-38b1dbf6d8ea
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: php.exe, version: 5.6.30.0, time stamp: 0x5880378d
Faulting module name: ntdll.dll, version: 6.3.9600.18696, time stamp: 0x5915ecd6
Exception code: 0xc0000005
Fault offset: 0x00040f17
Faulting process ID: 0x1ac4
Faulting application start time: 0x01d2ef5183067933
Faulting application path: C:\xampp\php\php.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: cc689e33-5b44-11e7-82a8-38b1dbf6d8ea
Faulting package full name:
Faulting package-relative application ID:


I have uninstalled and reinstalled xampp and it didn't help.
by desbest
27. June 2017 15:24
 
Forum: XAMPP for Windows
Topic: CLI has stopped responding
Replies: 0
Views: 855

PHPMyAdmin Access Denied

Here is the error code from the log, kindly help. Thank you


2015-11-10 15:26:56 10fc 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-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2017-06-20 10:43:56 10f0 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-06-20 10:43:56 4336 [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-06-20 10:43:56 4336 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-06-20 10:43:56 4336 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-20 10:43:56 4336 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-06-20 10:43:56 4336 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-06-20 10:43:56 4336 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-06-20 10:43:56 4336 [Note] InnoDB: Using generic crc32 instructions
2017-06-20 10:43:56 4336 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-06-20 10:43:56 4336 [Note] InnoDB: Completed initialization of buffer pool
2017-06-20 10:43:56 4336 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-20 10:43:58 4336 [Note] InnoDB: 128 rollback segment(s) are active.
2017-06-20 10:43:58 4336 [Note] InnoDB: Waiting for purge to start
2017-06-20 10:43:58 4336 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1835037
2017-06-20 10:43:58 2724 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-06-20 10:43:58 4336 [Note] Plugin 'FEEDBACK' is disabled.
2017-06-20 10:43:58 4336 [Note] Server socket created on IP: '::'.
2017-06-20 10:43:58 4336 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.22-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
170620 10:44:05 [ERROR] mysqld got exception 0xc0000005 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.22-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=1
max_threads=1001
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787106 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x6c9af98
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...
chtbrkg.dll!???
WS2_32.dll!recv()
mysqld.exe!my_wildcmp_mb_bin()
mysqld.exe!?my_net_read@@YAKPAUst_net@@@Z()
mysqld.exe!my_net_read_packet()
mysqld.exe!?search@?$Hash_filo@Vacl_entry@@@@QAEPAVacl_entry@@PAEI@Z()
mysqld.exe!?mysql_table_grant@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@Ust_lex_user@@@@AAV?$List@VLEX_COLUMN@@@@K_N@Z()
mysqld.exe!?copy@ACL_USER@@QAEPAV1@PAUst_mem_root@@@Z()
mysqld.exe!?acl_authenticate@@YA_NPAVTHD@@I@Z()
mysqld.exe!?write_execute_ddl_log_entry@@YA_NI_NPAPAUst_ddl_log_memory_entry@@@Z()
mysqld.exe!?login_connection@@YA_NPAVTHD@@@Z()
mysqld.exe!?thd_prepare_connection@@YA_NPAVTHD@@@Z()
mysqld.exe!?threadpool_add_connection@@YAHPAVTHD@@@Z()
mysqld.exe!?login@@YAHPAUconnection_t@@PAU_TP_CALLBACK_INSTANCE@@@Z()
mysqld.exe!?login@@YAHPAUconnection_t@@PAU_TP_CALLBACK_INSTANCE@@@Z()
ntdll.dll!LdrRegisterDllNotification()
ntdll.dll!TpCallbackIndependent()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
Connection ID (thread ID): 2
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off

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.
by tella_opeyemi
20. June 2017 10:38
 
Forum: XAMPP for Windows
Topic: PHPMyAdmin Access Denied
Replies: 0
Views: 1096

Apache suddenly stops working

Hi all,

Can anyone help me with my problem?
Apache sometimes stop working. Please see the log message from the event viewer.

Faulting application name: apache.exe, version: 2.2.4.0, time stamp: 0x45ebef86
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58
Exception code: 0xc0000005
Fault offset: 0x0002e39e
Faulting process id: 0x17d0
Faulting application start time: 0x01d247aecbd584d4
Faulting application path: C:\xampp\apache\bin\apache.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 49ba053a-b3a4-11e6-b356-0cc47a78ecd1

I am new to this and I don't have any idea what to do. Hope someone can help me.
Thanks!
by jdelfin
28. November 2016 10:05
 
Forum: XAMPP for Windows
Topic: Apache suddenly stops working
Replies: 1
Views: 2108

XAMPP 7.0.5 stüzt ab - Win 7 ultimate

Hallo Leute,

mein Apache HTTP Server stürzt immer wieder ab, dann bekomme ich eine Meldung in der steht:

Apache HTTP Serverfunktioniert nicht mehr
Problemdetails:
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: httpd.exe
Anwendungsversion: 2.4.18.0
Anwendungszeitstempel: 5667f02e
Fehlermodulname: ntdll.dll
Fehlermodulversion: 6.1.7601.23392
Fehlermodulzeitstempel: 56eb302d
Ausnahmecode: c0000005
Ausnahmeoffset: 0002e43e
Betriebsystemversion: 6.1.7601.2.1.0.256.1
Gebietsschema-ID: 1031
Zusatzinformation 1: 0a9e
Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
Zusatzinformation 3: 0a9e
Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789


Im Apache Error log steht:

[Sat Apr 30 10:09:42.919402 2016] [ssl:warn] [pid 4644:tid 252] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sat Apr 30 10:09:42.970408 2016] [core:warn] [pid 4644:tid 252] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Sat Apr 30 10:09:43.058920 2016] [ssl:warn] [pid 4644:tid 252] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sat Apr 30 10:09:43.084923 2016] [mpm_winnt:notice] [pid 4644:tid 252] AH00455: Apache/2.4.18 (Win32) OpenSSL/1.0.2e PHP/7.0.4 configured -- resuming normal operations
[Sat Apr 30 10:09:43.085423 2016] [mpm_winnt:notice] [pid 4644:tid 252] AH00456: Apache Lounge VC14 Server built: Dec 9 2015 10:17:39
[Sat Apr 30 10:09:43.085423 2016] [core:notice] [pid 4644:tid 252] AH00094: Command line: 'c:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache'
[Sat Apr 30 10:09:43.086423 2016] [mpm_winnt:notice] [pid 4644:tid 252] AH00418: Parent: Created child process 3692
[Sat Apr 30 10:09:43.518478 2016] [ssl:warn] [pid 3692:tid 264] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sat Apr 30 10:09:43.641494 2016] [ssl:warn] [pid 3692:tid 264] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sat Apr 30 10:09:43.666497 2016] [mpm_winnt:notice] [pid 3692:tid 264] AH00354: Child: Starting 150 worker threads.
[Sat Apr 30 10:35:10.749412 2016] [mpm_winnt:notice] [pid 4644:tid 252] AH00428: Parent: child process 3692 exited with status 3221225477 -- Restarting.
[Sat Apr 30 10:35:11.187967 2016] [ssl:warn] [pid 4644:tid 252] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sat Apr 30 10:35:11.217471 2016] [mpm_winnt:notice] [pid 4644:tid 252] AH00455: Apache/2.4.18 (Win32) OpenSSL/1.0.2e PHP/7.0.4 configured -- resuming normal operations
[Sat Apr 30 10:35:11.217471 2016] [mpm_winnt:notice] [pid 4644:tid 252] AH00456: Apache Lounge VC14 Server built: Dec 9 2015 10:17:39
[Sat Apr 30 10:35:11.217971 2016] [core:notice] [pid 4644:tid 252] AH00094: Command line: 'c:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache'
[Sat Apr 30 10:35:11.219971 2016] [mpm_winnt:notice] [pid 4644:tid 252] AH00418: Parent: Created child process 2764
[Sat Apr 30 10:35:11.718535 2016] [ssl:warn] [pid 2764:tid 264] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sat Apr 30 10:35:11.845551 2016] [ssl:warn] [pid 2764:tid 264] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sat Apr 30 10:35:11.872054 2016] [mpm_winnt:notice] [pid 2764:tid 264] AH00354: Child: Starting 150 worker threads.


Jetzt noch etwas zum lachen für Euch: Ich benutze XAMPP seit Jahren hatte nie Probleme und kann auch nichts mit diesen Fehlermeldungen anfangen. Sorry
Wenn Ihr jetzt noch weitere Infos benötigt dann sagt bitte einfach bescheid und ich reiche diese umgehend nach.

Besten Dank
Schöne Grüße
BonnyAndClyde2011
by BonnyAndClyde2011
30. April 2016 09:42
 
Forum: XAMPP für Windows
Topic: XAMPP 7.0.5 stüzt ab - Win 7 ultimate
Replies: 2
Views: 2413

Apache/Mysql Crashing When increasing System Specification

Hi all,

I have been using XAMPP on windows for the two year or so and it has been running perfectly, no crashes no problems. (Up until four month ago.)

Around four months ago, we upgraded our server/system to a faster specification.

Here is what the old spec was -

Windows Edition: Windows Server R2 2008 Standard with Service Pack 1
System:
Processor: Intel(R) Xeon(R) CPU 5160 @3.0GHZ (2 Processors) (Single Core)
Installed Memory: 7GB
System Type: 64 Bit Operating System


Upgraded Spec
Windows Edition: Windows Server R2 2008 Standard with Service Pack 1
System:
Processor: Intel(R) Xeon(R) CPU X5680 @3.33GHZ (2 Processors) (Dual Core)
Installed Memory: 8GB
System Type: 64 Bit Operating System


So like I mentioned before, the old spec never had any problems, it never crashed or failed over one and a half years.

As soon as we upgraded the following happened.

Random Apache crashes, making the site un-usable until it is manually restarted. It would throw errors up when accessing phpMyAdmin when apache had crashed too, stopping you from querying the DB. I even uninstalled XAMPP and installed the latest version with PHP7, this still didn't solve the problem.

Heres an example

Notice in .\libraries\common.inc.php#253
Undefined variable: _POST

Backtrace

.\index.php#12: require_once(.\libraries\common.inc.php)
Warning in .\libraries\common.inc.php#253
array_merge(): Argument #2 is not an array

Backtrace

.\libraries\common.inc.php#253: array_merge(
array,
NULL,
)
.\index.php#12: require_once(.\libraries\common.inc.php)
Notice in .\libraries\common.inc.php#443
Undefined variable: _POST

Backtrace

.\index.php#12: require_once(.\libraries\common.inc.php)
Notice in .\libraries\common.inc.php#453
Undefined variable: _POST

Backtrace

.\index.php#12: require_once(.\libraries\common.inc.php)
Notice in .\libraries\cleanup.lib.php#26
Undefined variable: _POST

Backtrace

.\libraries\common.inc.php#514: PMA_removeRequestVars(array)
.\index.php#12: require_once(.\libraries\common.inc.php)
Notice in .\libraries\cleanup.lib.php#31
Undefined variable: _POST

Backtrace

.\libraries\common.inc.php#514: PMA_removeRequestVars(array)
.\index.php#12: require_once(.\libraries\common.inc.php)

This can happen from 1-5 times a day, and there are no logs produced to give any reason why it happened. The only way I could find out was go into the event viewer which is extremely vague.

Heres an example --

Faulting application name: httpd.exe, version: 2.4.18.0, time stamp: 0x5667f02e
Faulting module name: php7ts.dll, version: 7.0.2.0, time stamp: 0x568d8eb5
Exception code: 0xc0000005
Fault offset: 0x0001ab54
Faulting process id: 0x9bf4
Faulting application start time: 0x01d18f1d3eed5f7e
Faulting application path: C:\xampp_\apache\bin\httpd.exe
Faulting module path: C:\xampp_\php\php7ts.dll
Report Id: a2a226d0-fb64-11e5-b4cb-005056a97cdf

And

Faulting application name: httpd.exe, version: 2.4.18.0, time stamp: 0x5667f02e
Faulting module name: ntdll.dll, version: 6.1.7601.23313, time stamp: 0x5684289c
Exception code: 0xc0000374
Fault offset: 0x000ce00b
Faulting process id: 0x3320
Faulting application start time: 0x01d18b1c1e501368
Faulting application path: C:\xampp_\apache\bin\httpd.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 77d4bd4a-f723-11e5-9fc8-005056a97cdf


Just to prove my theory of the faster spec being the issue, I got the Specification lowered back to its original state, and for 2 weeks XAMPP never crashed once, as soon as we but it back to the higher spec, it crashed within hours.

Is there anything you are speicificly meant to do to XAMPP if you upgrade to faster spec?

I am absolutely lost for ideas, I have looked and looked online and can't seem to find anyone who is experiencing the same problems that I am having and why.

If anyone could shed some light on these issues, I would greatly appreciate it!
by CodeFluffer
07. April 2016 09:10
 
Forum: XAMPP for Windows
Topic: Apache/Mysql Crashing When increasing System Specification
Replies: 1
Views: 3486

Re: Problems with localhost

Hi Altrea

Below is the next part of the error log.

[color=0000fff]MySQL Error Log[/color]

2015-11-22 13:31:58 2e14 InnoDB: uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 536728786, innodb 1575996416, none 3735928559, stored checksum in field2 0, calculated checksums for field2: crc32 536728786, innodb 1371122432, none 3735928559, page LSN 0 0, low 4 bytes of LSN at page end 0, page number (if stored to page already) 0, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
InnoDB: Page directory corruption: supremum not pointed to
2015-11-22 13:31:58 2e14 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; asc ;
InnoDB: End of page dump
2015-11-22 13:31:58 2e14 InnoDB: uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 536728786, innodb 1575996416, none 3735928559, stored checksum in field2 0, calculated checksums for field2: crc32 536728786, innodb 1371122432, none 3735928559, page LSN 0 0, low 4 bytes of LSN at page end 0, page number (if stored to page already) 0, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
13:31:58 UTC - mysqld got exception 0xc0000005 ;
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=262144
max_used_connections=3
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133634 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1b49dd70
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...
d57941 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
d13bd0 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
d14a26 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
c34d60 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
9adc41 mysqld.exe!?multi_range_read_info_const@handler@@UAE_KIPAUst_range_seq_if@@PAXIPAI2PAVCost_estimate@@@Z()
9b256e mysqld.exe!?dsmrr_info_const@DsMrr_impl@@QAE_KIPAUst_range_seq_if@@PAXIPAI2PAVCost_estimate@@@Z()
b98260 mysqld.exe!?sel_arg_range_seq_next@@YAIPAXPAUst_key_multi_range@@@Z()
b99f11 mysqld.exe!?make_quick@TRP_RANGE@@UAEPAVQUICK_SELECT_I@@PAVPARAM@@_NPAUst_mem_root@@@Z()
b9ed49 mysqld.exe!?test_quick_select@SQL_SELECT@@QAEHPAVTHD@@V?$Bitmap@$0EA@@@_K2_NW4enum_order@st_order@@@Z()
b70880 mysqld.exe!?set_semijoin_embedding@JOIN@@QAEXXZ()
b7ce60 mysqld.exe!?decide_subquery_strategy@JOIN@@QAE_NXZ()
b7db0a mysqld.exe!?optimize@JOIN@@QAEHXZ()
b068c9 mysqld.exe!?optimize@st_select_lex_unit@@QAE_NXZ()
b371f6 mysqld.exe!?mysql_derived_optimize@@YA_NPAVTHD@@PAULEX@@PAUTABLE_LIST@@@Z()
b36f5e mysqld.exe!?mysql_handle_single_derived@@YA_NPAULEX@@PAUTABLE_LIST@@P6A_NPAVTHD@@01@Z@Z()
aa0d2c mysqld.exe!?handle_derived@TABLE_LIST@@QAE_NPAULEX@@P6A_NPAVTHD@@0PAU1@@Z@Z()
a3bd38 mysqld.exe!?handle_derived@st_select_lex@@QAE_NPAULEX@@P6A_NPAVTHD@@0PAUTABLE_LIST@@@Z@Z()
b7d635 mysqld.exe!?optimize@JOIN@@QAEHXZ()
afc282 mysqld.exe!?explain@JOIN@@QAE_NXZ()
b019a2 mysqld.exe!?mysql_select@@YA_NPAVTHD@@PAUTABLE_LIST@@IAAV?$List@VItem@@@@PAVItem@@PAV?$SQL_I_List@Ust_order@@@@43_KPAVselect_result@@PAVst_select_lex_unit@@PAVst_select_lex@@@Z()
b01a7f mysqld.exe!?handle_select@@YA_NPAVTHD@@PAVselect_result@@K@Z()
9d9354 mysqld.exe!??0st_ha_create_information@@QAE@ABU0@@Z()
9dc559 mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
9e015b mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
9e0e46 mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
9e1cbd mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
a55929 mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
a559cd mysqld.exe!handle_one_connection()
db246b mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
c04336 mysqld.exe!win_pthread_mutex_trylock()
e3e8c3 mysqld.exe!my_mb_ctype_mb()
e3e94d mysqld.exe!my_mb_ctype_mb()
76523744 KERNEL32.DLL!BaseThreadInitThunk()
7726a064 ntdll.dll!RtlSetCurrentTransaction()
7726a02f ntdll.dll!RtlSetCurrentTransaction()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (21206e20): SELECT COUNT(*)
FROM (
SELECT 0

FROM
wp_blc_links AS links
JOIN wp_blc_instances AS instances ON links.link_id = instances.link_id

WHERE
( instances.parser_type IN ('link', 'image', 'youtube-iframe', 'metadata', 'url_field') ) AND
( instances.container_type IN ('dummy', 'page', 'post', 'comment') )

GROUP BY links.link_id) AS fooConnection ID (thread ID): 41
Status: NOT_KILLED

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.
2015-11-22 14:35:06 16252 [Note] Plugin 'FEDERATED' is disabled.
2015-11-22 14:35:06 1e78 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-11-22 14:35:06 16252 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-22 14:35:06 16252 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-22 14:35:06 16252 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-22 14:35:06 16252 [Note] InnoDB: Memory barrier is not used
2015-11-22 14:35:06 16252 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-22 14:35:06 16252 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-22 14:35:06 16252 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-22 14:35:06 16252 [Note] InnoDB: Completed initialization of buffer pool
2015-11-22 14:35:06 16252 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-22 14:35:06 16252 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 59462396 in the ib_logfiles!
2015-11-22 14:35:06 16252 [Note] InnoDB: Database was not shutdown normally!
2015-11-22 14:35:06 16252 [Note] InnoDB: Starting crash recovery.
2015-11-22 14:35:06 16252 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-22 14:35:06 16252 [Note] InnoDB: Restoring possible half-written data pages
2015-11-22 14:35:06 16252 [Note] InnoDB: from the doublewrite buffer...
2015-11-22 14:35:07 16252 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-22 14:35:07 16252 [Note] InnoDB: Waiting for purge to start
2015-11-22 14:35:07 16252 [Note] InnoDB: 5.6.24 started; log sequence number 59462396
2015-11-22 14:35:07 16252 [Note] Server hostname (bind-address): '*'; port: 3306
2015-11-22 14:35:07 16252 [Note] IPv6 is available.
2015-11-22 14:35:07 16252 [Note] - '::' resolves to '::';
2015-11-22 14:35:07 16252 [Note] Server socket created on IP: '::'.
2015-11-22 14:35:07 16252 [Note] Event Scheduler: Loaded 0 events
2015-11-22 14:35:07 16252 [Note] f:\mark\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.24' socket: '' port: 3306 MySQL Community Server (GPL)
2015-11-27 15:34:42 9728 [Note] Plugin 'FEDERATED' is disabled.
2015-11-27 15:34:42 20ac 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-11-27 15:34:42 9728 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-27 15:34:42 9728 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-27 15:34:42 9728 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-27 15:34:42 9728 [Note] InnoDB: Memory barrier is not used
2015-11-27 15:34:42 9728 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-27 15:34:42 9728 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-27 15:34:42 9728 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-27 15:34:42 9728 [Note] InnoDB: Completed initialization of buffer pool
2015-11-27 15:34:42 9728 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-27 15:34:42 9728 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 59710800 in the ib_logfiles!
2015-11-27 15:34:42 9728 [Note] InnoDB: Database was not shutdown normally!
2015-11-27 15:34:42 9728 [Note] InnoDB: Starting crash recovery.
2015-11-27 15:34:42 9728 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-27 15:34:43 9728 [Note] InnoDB: Restoring possible half-written data pages
2015-11-27 15:34:43 9728 [Note] InnoDB: from the doublewrite buffer...
2015-11-27 15:34:44 9728 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-27 15:34:44 9728 [Note] InnoDB: Waiting for purge to start
2015-11-27 15:34:44 9728 [Note] InnoDB: 5.6.24 started; log sequence number 59710800
2015-11-27 15:34:44 9728 [Note] Server hostname (bind-address): '*'; port: 3306
2015-11-27 15:34:44 9728 [Note] IPv6 is available.

I would be grateful if you could give me some pointers on how to resolve the situation.

Many Thanks

The_Warm_Observer
by the_warm_observer
20. March 2016 18:00
 
Forum: XAMPP for Windows
Topic: Problems with localhost
Replies: 9
Views: 7321

Re: Error: MySQL shutdown unexpectedly

I read ALL mysql_error.log and among tons of my attempts to start mysql found long list of warnings and errors (I can't put it all here because it is really very long) and then following:

160309 16:05:23 [ERROR] mysqld got exception 0xc0000005 ;
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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 10.0.17-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=501
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 403207 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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...
mysqld.exe!?init_all_master_info@Master_info_index@@QAE_NXZ()
mysqld.exe!?init_slave@@YAHXZ()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!my_mb_ctype_mb()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
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.

I have no idea what it could be and what to do next. I am really frustrated.
Does that mean that my site is lost? Is there any hope that I can put it on web-hosting without access to MySQL in Xampp???
by alexis987
10. March 2016 19:26
 
Forum: XAMPP for Windows
Topic: Error: MySQL shutdown unexpectedly
Replies: 5
Views: 3272

XAMPP Fehlermeldung

Hallo Leute :)

ich habe auf meinem Windows 10 Rechner XAMPP laufen. Urplötzlich schmierte mir allerdings MySQL ab. Wenn ich nun MySQL starten will, zeigt er mir eine Fehlermeldung an und bricht ab.

Ich hänge den Error_Log unten an.

Hat einer eine Idee?
Vielen Dank schonmal im Vorraus :)

Mit besten Grüßen
mvaleriu

2016-03-03 21:17:07 8d4 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.
2016-03-03 21:17:07 2260 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-03-03 21:17:07 2260 [Note] InnoDB: The InnoDB memory heap is disabled
2016-03-03 21:17:07 2260 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-03-03 21:17:07 2260 [Note] InnoDB: Memory barrier is not used
2016-03-03 21:17:07 2260 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-03-03 21:17:07 2260 [Note] InnoDB: Using generic crc32 instructions
2016-03-03 21:17:07 2260 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-03-03 21:17:07 2260 [Note] InnoDB: Completed initialization of buffer pool
2016-03-03 21:17:07 2260 [Note] InnoDB: Highest supported file format is Barracuda.
2016-03-03 21:17:07 2260 [Note] InnoDB: Log scan progressed past the checkpoint lsn 75941840
2016-03-03 21:17:07 2260 [Note] InnoDB: Database was not shutdown normally!
2016-03-03 21:17:07 2260 [Note] InnoDB: Starting crash recovery.
2016-03-03 21:17:07 2260 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-03-03 21:17:07 2260 [Note] InnoDB: Restoring possible half-written data pages
2016-03-03 21:17:07 2260 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 75943364
2016-03-03 21:17:07 2260 [ERROR] InnoDB: Database page corruption on disk or a failed
2016-03-03 21:17:07 2260 [ERROR] InnoDB: Space 0 file C:\xampp\mysql\data\ibdata1 read of page 203.
2016-03-03 21:17:07 2260 [ERROR] InnoDB: You may have to recover from a backup.
2016-03-03 21:17:07 8d4 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 6d86f3d1000000cb000000000000000000000000048589300006000000000000000000000000fffffffe0000000000000001000001d90078000001d90078000000000000000221f2000001fe000001d9ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; asc m 0 x x ! ;
InnoDB: End of page dump
2016-03-03 21:17:08 8d4 InnoDB: uncompressed page, stored checksum in field1 1837560785, calculated checksums for field1: crc32 3147805670, innodb 1837560785, none 3735928559, stored checksum in field2 0, calculated checksums for field2: crc32 3147805670, innodb 1516354016, none 3735928559, page LSN 0 75860272, low 4 bytes of LSN at page end 0, page number (if stored to page already) 203, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: page type 6 meaning SYS
InnoDB: Page may be a system page
2016-03-03 21:17:08 2260 [ERROR] InnoDB: It is also possible that your operatingsystem has corrupted its own file cache.
2016-03-03 21:17:08 2260 [ERROR] InnoDB: and rebooting your computer removes the error.
2016-03-03 21:17:08 2260 [ERROR] InnoDB: If the corrupt page is an index page you can also try to
2016-03-03 21:17:08 2260 [ERROR] InnoDB: fix the corruption by dumping, dropping, and reimporting
2016-03-03 21:17:08 2260 [ERROR] InnoDB: the corrupt table. You can use CHECK
2016-03-03 21:17:08 2260 [ERROR] InnoDB: TABLE to scan your table for corruption.
2016-03-03 21:17:08 2260 [ERROR] InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html about forcing recovery.
2016-03-03 21:17:08 2260 [ERROR] InnoDB: Ending processing because of a corrupt database page.
2016-03-03 21:17:08 8d4 InnoDB: Assertion failure in thread 2260 in file buf0buf.cc line 4788
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
160303 21:17:08 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 10.1.10-MariaDB
key_buffer_size=1677721600
read_buffer_size=268435456
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 329627 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!my_mb_ctype_mb()
mysqld.exe!??2Geometry@@SAPAXIPAX@Z()
mysqld.exe!??2Geometry@@SAPAXIPAX@Z()
mysqld.exe!?propagate_equal_fields@Item_func_expr_str_metadata@@UAEPAVItem@@PAVTHD@@ABVContext@Value_source@@PAVCOND_EQUAL@@@Z()
mysqld.exe!?propagate_equal_fields@Item_func_expr_str_metadata@@UAEPAVItem@@PAVTHD@@ABVContext@Value_source@@PAVCOND_EQUAL@@@Z()
mysqld.exe!?propagate_equal_fields@Item_func_expr_str_metadata@@UAEPAVItem@@PAVTHD@@ABVContext@Value_source@@PAVCOND_EQUAL@@@Z()
mysqld.exe!?propagate_equal_fields@Item_func_expr_str_metadata@@UAEPAVItem@@PAVTHD@@ABVContext@Value_source@@PAVCOND_EQUAL@@@Z()
mysqld.exe!?propagate_equal_fields@Item_func_expr_str_metadata@@UAEPAVItem@@PAVTHD@@ABVContext@Value_source@@PAVCOND_EQUAL@@@Z()
mysqld.exe!?propagate_equal_fields@Item_func_expr_str_metadata@@UAEPAVItem@@PAVTHD@@ABVContext@Value_source@@PAVCOND_EQUAL@@@Z()
mysqld.exe!?propagate_equal_fields@Item_func_expr_str_metadata@@UAEPAVItem@@PAVTHD@@ABVContext@Value_source@@PAVCOND_EQUAL@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_unlock_list@@YAXPAVTHD@@PAPAUst_plugin_int@@I@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!handle_shutdown()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!my_mb_ctype_mb()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlCheckPortableOperatingSystem()
ntdll.dll!RtlCheckPortableOperatingSystem()
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.
by mvaleriu
03. March 2016 21:12
 
Forum: XAMPP für Windows
Topic: XAMPP Fehlermeldung
Replies: 2
Views: 2218

XAMPP, Mysql Error Shutdown Unexpectedly

Hi, my xampp keeps on giving error by saying this message in red font text whenever i tried to start mysql

Error: MySQL shutdown unexpectedly.
11:14:04 AM [mysql] This may be due to a blocked port, missing dependencies,
11:14:04 AM [mysql] improper privileges, a crash, or a shutdown by another method.
11:14:04 AM [mysql] Press the Logs button to view error logs and check
11:14:04 AM [mysql] the Windows Event Viewer for more clues
11:14:04 AM [mysql] If you need more help, copy and post this
11:14:04 AM [mysql] entire log window on the forums



I have tried many solution such as deleting the ibdata1 file and done lots of other solution found on the internet but the problem still occur


This is my log file during the problem occur

2016-01-11 10:46:49 324 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:46:49 1810 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.
2016-01-11 10:46:49 324 [Note] InnoDB: Started in read only mode
2016-01-11 10:46:49 324 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:46:49 324 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:46:49 324 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:46:49 324 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:46:49 324 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:46:49 324 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:46:49 324 [Note] InnoDB: Disabling background IO write threads.
2016-01-11 10:46:49 324 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:46:49 324 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:46:49 324 [Note] InnoDB: Highest supported file format is Barracuda.
2016-01-11 10:46:49 324 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3460453250 in the ib_logfiles!
2016-01-11 10:46:49 324 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
2016-01-11 10:46:49 324 [ERROR] Plugin 'InnoDB' init function returned error.
2016-01-11 10:46:49 324 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-01-11 10:46:49 324 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-01-11 10:46:49 324 [ERROR] Aborting

2016-01-11 10:46:49 324 [Note] Binlog end
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'partition'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_METRICS'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_CMP'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'INNODB_TRX'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'BLACKHOLE'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'ARCHIVE'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'MRG_MYISAM'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'MyISAM'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'MEMORY'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'CSV'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'sha256_password'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'mysql_old_password'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'mysql_native_password'
2016-01-11 10:46:49 324 [Note] Shutting down plugin 'binlog'
2016-01-11 10:46:49 324 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2016-01-11 10:46:51 2440 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:46:51 12a0 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.
2016-01-11 10:46:51 2440 [Note] InnoDB: Started in read only mode
2016-01-11 10:46:51 2440 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:46:51 2440 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:46:51 2440 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:46:51 2440 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:46:51 2440 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:46:51 2440 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:46:51 2440 [Note] InnoDB: Disabling background IO write threads.
2016-01-11 10:46:51 2440 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:46:51 2440 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:46:51 2440 [Note] InnoDB: Highest supported file format is Barracuda.
2016-01-11 10:46:51 2440 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3460453250 in the ib_logfiles!
2016-01-11 10:46:51 2440 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
2016-01-11 10:46:51 2440 [ERROR] Plugin 'InnoDB' init function returned error.
2016-01-11 10:46:51 2440 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-01-11 10:46:51 2440 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-01-11 10:46:51 2440 [ERROR] Aborting

2016-01-11 10:46:51 2440 [Note] Binlog end
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'partition'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_METRICS'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_CMP'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'INNODB_TRX'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'BLACKHOLE'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'ARCHIVE'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'MRG_MYISAM'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'MyISAM'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'MEMORY'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'CSV'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'sha256_password'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'mysql_old_password'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'mysql_native_password'
2016-01-11 10:46:51 2440 [Note] Shutting down plugin 'binlog'
2016-01-11 10:46:51 2440 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2016-01-11 10:48:39 3472 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:48:39 12a8 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.
2016-01-11 10:48:39 3472 [Note] InnoDB: Started in read only mode
2016-01-11 10:48:39 3472 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:48:39 3472 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:48:39 3472 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:48:39 3472 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:48:39 3472 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:48:39 3472 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:48:39 3472 [Note] InnoDB: Disabling background IO write threads.
2016-01-11 10:48:39 3472 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:48:39 3472 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:48:39 12a8 InnoDB: Operating system error number 2 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
2016-01-11 10:48:39 3472 [ERROR] InnoDB: File C:\xampp\mysql\data\ibdata1: 'open' returned OS error 71. Cannot continue operation
2016-01-11 10:50:15 6188 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:50:15 628 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.
2016-01-11 10:50:15 6188 [Note] InnoDB: Started in read only mode
2016-01-11 10:50:15 6188 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:50:15 6188 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:50:15 6188 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:50:15 6188 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:50:15 6188 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:50:15 6188 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:50:15 6188 [Note] InnoDB: Disabling background IO write threads.
2016-01-11 10:50:15 6188 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:50:15 6188 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:50:15 628 InnoDB: Operating system error number 2 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
2016-01-11 10:50:15 6188 [ERROR] InnoDB: File C:\xampp\mysql\data\ibdata1: 'open' returned OS error 71. Cannot continue operation
2016-01-11 10:50:30 2640 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:50:30 39c 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.
2016-01-11 10:50:30 2640 [Note] InnoDB: Started in read only mode
2016-01-11 10:50:30 2640 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:50:30 2640 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:50:30 2640 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:50:30 2640 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:50:30 2640 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:50:30 2640 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:50:30 2640 [Note] InnoDB: Disabling background IO write threads.
2016-01-11 10:50:30 2640 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:50:30 2640 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:50:30 39c InnoDB: Operating system error number 2 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
2016-01-11 10:50:30 2640 [ERROR] InnoDB: File C:\xampp\mysql\data\ibdata1: 'open' returned OS error 71. Cannot continue operation
2016-01-11 10:50:31 6540 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:50:31 364 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.
2016-01-11 10:50:31 6540 [Note] InnoDB: Started in read only mode
2016-01-11 10:50:31 6540 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:50:31 6540 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:50:31 6540 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:50:31 6540 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:50:31 6540 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:50:31 6540 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:50:31 6540 [Note] InnoDB: Disabling background IO write threads.
2016-01-11 10:50:31 6540 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:50:31 6540 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:50:31 364 InnoDB: Operating system error number 2 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
2016-01-11 10:50:31 6540 [ERROR] InnoDB: File C:\xampp\mysql\data\ibdata1: 'open' returned OS error 71. Cannot continue operation
2016-01-11 10:51:35 5972 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:51:35 16b4 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.
2016-01-11 10:51:35 5972 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:51:35 5972 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:51:35 5972 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:51:35 5972 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:51:35 5972 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:51:35 5972 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:51:35 5972 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:51:35 5972 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:51:35 5972 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2016-01-11 10:51:35 5972 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2016-01-11 10:51:35 5972 [Note] InnoDB: Database physically writes the file full: wait...
2016-01-11 10:51:35 5972 [ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile101
2016-01-11 10:51:35 5972 [ERROR] Plugin 'InnoDB' init function returned error.
2016-01-11 10:51:35 5972 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-01-11 10:51:35 5972 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-01-11 10:51:35 5972 [ERROR] Aborting

2016-01-11 10:51:35 5972 [Note] Binlog end
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'partition'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_METRICS'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_CMP'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'INNODB_TRX'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'BLACKHOLE'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'ARCHIVE'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'MRG_MYISAM'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'MyISAM'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'MEMORY'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'CSV'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'sha256_password'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'mysql_old_password'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'mysql_native_password'
2016-01-11 10:51:35 5972 [Note] Shutting down plugin 'binlog'
2016-01-11 10:51:35 5972 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2016-01-11 10:51:38 6188 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:51:38 b4c 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.
2016-01-11 10:51:38 6188 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:51:38 6188 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:51:38 6188 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:51:38 6188 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:51:38 6188 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:51:38 6188 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:51:38 6188 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:51:38 6188 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:51:38 6188 [Note] InnoDB: Highest supported file format is Barracuda.
2016-01-11 10:51:38 6188 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3460453250 in the ib_logfiles!
2016-01-11 10:51:38 6188 [Note] InnoDB: Database was not shutdown normally!
2016-01-11 10:51:38 6188 [Note] InnoDB: Starting crash recovery.
2016-01-11 10:51:38 6188 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-01-11 10:51:41 2640 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:51:41 d58 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.
2016-01-11 10:51:41 2640 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:51:41 2640 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:51:41 2640 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:51:41 2640 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:51:41 2640 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:51:41 2640 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:51:41 2640 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:51:41 2640 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:51:41 2640 [Note] InnoDB: Highest supported file format is Barracuda.
2016-01-11 10:51:41 2640 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3460453250 in the ib_logfiles!
2016-01-11 10:51:41 2640 [Note] InnoDB: Database was not shutdown normally!
2016-01-11 10:51:41 2640 [Note] InnoDB: Starting crash recovery.
2016-01-11 10:51:41 2640 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-01-11 10:51:43 2640 [Note] InnoDB: Restoring possible half-written data pages
2016-01-11 10:51:43 2640 [Note] InnoDB: from the doublewrite buffer...
2016-01-11 10:51:43 d58 InnoDB: Assertion failure in thread 3416 in file fsp0fsp.cc line 1887
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:51:43 UTC - mysqld got exception 0x80000003 ;
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=262144
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 = 133778 K bytes of memory
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...
127a500 mysqld.exe!my_thread_name()
14b392d mysqld.exe!my_mb_ctype_mb()
135c937 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
132c0f9 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
13db796 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
12f5356 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
12ae22a mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
102a200 mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
106434e mysqld.exe!?plugin_lock_by_name@@YAPAUst_plugin_int@@PAVTHD@@PBUst_mysql_lex_string@@H@Z()
1068a81 mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
10217bb mysqld.exe!?init_common_variables@@YAHXZ()
10224c8 mysqld.exe!?win_main@@YAHHPAPAD@Z()
1022a37 mysqld.exe!?mysql_service@@YAHPAX@Z()
14ae48a mysqld.exe!my_mb_ctype_mb()
74d2338a kernel32.dll!BaseThreadInitThunk()
77079f72 ntdll.dll!RtlInitializeExceptionChain()
77079f45 ntdll.dll!RtlInitializeExceptionChain()
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.
2016-01-11 10:51:59 6804 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:51:59 5c4 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.
2016-01-11 10:51:59 6804 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:51:59 6804 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:51:59 6804 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:51:59 6804 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:51:59 6804 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:51:59 6804 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:51:59 6804 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:51:59 6804 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:51:59 6804 [Note] InnoDB: Highest supported file format is Barracuda.
2016-01-11 10:51:59 6804 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3460453250 in the ib_logfiles!
2016-01-11 10:51:59 6804 [Note] InnoDB: Database was not shutdown normally!
2016-01-11 10:51:59 6804 [Note] InnoDB: Starting crash recovery.
2016-01-11 10:51:59 6804 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-01-11 10:51:59 6804 [Note] InnoDB: Restoring possible half-written data pages
2016-01-11 10:51:59 6804 [Note] InnoDB: from the doublewrite buffer...
2016-01-11 10:51:59 5c4 InnoDB: Assertion failure in thread 1476 in file fsp0fsp.cc line 1887
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:51:59 UTC - mysqld got exception 0x80000003 ;
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=262144
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 = 133778 K bytes of memory
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...
127a500 mysqld.exe!my_thread_name()
14b392d mysqld.exe!my_mb_ctype_mb()
135c937 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
132c0f9 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
13db796 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
12f5356 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
12ae22a mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
102a200 mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
106434e mysqld.exe!?plugin_lock_by_name@@YAPAUst_plugin_int@@PAVTHD@@PBUst_mysql_lex_string@@H@Z()
1068a81 mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
10217bb mysqld.exe!?init_common_variables@@YAHXZ()
10224c8 mysqld.exe!?win_main@@YAHHPAPAD@Z()
1022a37 mysqld.exe!?mysql_service@@YAHPAX@Z()
14ae48a mysqld.exe!my_mb_ctype_mb()
74d2338a kernel32.dll!BaseThreadInitThunk()
77079f72 ntdll.dll!RtlInitializeExceptionChain()
77079f45 ntdll.dll!RtlInitializeExceptionChain()
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.
2016-01-11 10:55:59 5924 [Note] Plugin 'FEDERATED' is disabled.
2016-01-11 10:55:59 1a08 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.
2016-01-11 10:55:59 5924 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-11 10:55:59 5924 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-11 10:55:59 5924 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-11 10:55:59 5924 [Note] InnoDB: Memory barrier is not used
2016-01-11 10:55:59 5924 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-11 10:55:59 5924 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-11 10:55:59 5924 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-01-11 10:55:59 5924 [Note] InnoDB: Completed initialization of buffer pool
2016-01-11 10:55:59 5924 [Note] InnoDB: Highest supported file format is Barracuda.
2016-01-11 10:56:00 5924 [Note] InnoDB: 128 rollback segment(s) are active.
2016-01-11 10:56:00 5924 [Note] InnoDB: Waiting for purge to start
2016-01-11 10:56:00 5924 [Note] InnoDB: 5.6.20 started; log sequence number 3460453250
2016-01-11 10:56:00 5924 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!!
2016-01-11 10:56:00 5924 [Note] Server hostname (bind-address): '*'; port: 3306
2016-01-11 10:56:00 5924 [Note] IPv6 is available.
2016-01-11 10:56:00 5924 [Note] - '::' resolves to '::';
2016-01-11 10:56:00 5924 [Note] Server socket created on IP: '::'.
2016-01-11 10:56:00 5924 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
2016-01-11 10:56:00 5924 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2016-01-11 10:56:00 5924 [ERROR] Aborting

2016-01-11 10:56:00 5924 [Note] Binlog end
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'partition'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_METRICS'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_CMP'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'INNODB_TRX'
2016-01-11 10:56:00 5924 [Note] Shutting down plugin 'InnoDB'
2016-01-11 10:56:00 5924 [Note] InnoDB: FTS optimize thread exiting.
2016-01-11 10:56:00 5924 [Note] InnoDB: Starting shutdown...
2016-01-11 10:56:02 5924 [Note] InnoDB: Shutdown completed; log sequence number 3460453260
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'BLACKHOLE'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'ARCHIVE'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'MRG_MYISAM'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'MyISAM'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'MEMORY'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'CSV'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'sha256_password'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'mysql_old_password'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'mysql_native_password'
2016-01-11 10:56:02 5924 [Note] Shutting down plugin 'binlog'
2016-01-11 10:56:02 5924 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

Hope someone can help me , I am new to this :(
by farhanz95
11. January 2016 04:35
 
Forum: XAMPP for Windows
Topic: XAMPP, Mysql Error Shutdown Unexpectedly
Replies: 3
Views: 4161

Re: Apache keep crashing without any special behavior

You could try disabling all modules you are not using (in apache & php). Did you install any modules that are not shipped with XAMPP? Are you using the ldap or a special database module of php? I think I've had problems like that when using ldap (that was really long ago, can't remember in detail).

2.4.12 is the current stable version, so it is very unlikely that another build (except if you downgrad to an older version) will help.

ntdll is the core api for windows, so unfortunately there is really no easy way to determine which part of Apache or PHP caused this crash.
by glitzi85
28. June 2015 16:52
 
Forum: XAMPP for Windows
Topic: Apache keep crashing without any special behavior
Replies: 5
Views: 6117
Next

Return to advanced search