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.
Error: MySQL shutdown unexpectedly.
1 post
• Page 1 of 1
Error: MySQL shutdown unexpectedly.
by BrinkBoef » 09. June 2018 20:34
- BrinkBoef
- Posts: 1
- Joined: 09. June 2018 20:28
- XAMPP version: v3.2.2
- Operating System: Windows 10
1 post
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 133 guests