Search found 92 matches: ntdll.dll

Searched query: +ntdll +dll

Return to advanced search

Re: Apache not work: SSL:warn

I run xampp-control and i press start and xampp logs;

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

And apache error.logs;

[Mon Dec 17 10:14:30.442142 2018] [ssl:warn] [pid 14628:tid 676] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 17 10:14:30.465081 2018] [core:warn] [pid 14628:tid 676] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Dec 17 10:14:30.466078 2018] [ssl:warn] [pid 14628:tid 676] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name

Windows event viewer;

- System
- Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2018-12-17T07:21:08.023272000Z
EventRecordID 45898
Channel Application
Computer DESKTOP-35CJMCM
Security
- EventData
httpd.exe
2.4.37.0
5bc8a3ef
ntdll.dll
10.0.17134.471
fe852bc4
c0000005
00043654
2d10
01d495d913e98db4
C:\xampp\apache\bin\httpd.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
ca149450-a4ee-48e4-866e-bb8e2bee34a3


*****

Faulting application name: httpd.exe, version: 2.4.37.0, time stamp: 0x5bc8a3ef
Faulting module name: ntdll.dll, version: 10.0.17134.471, time stamp: 0xfe852bc4
Exception code: 0xc0000005
Fault offset: 0x00043654
Faulting process id: 0x5780
Faulting application start time: 0x01d495d9158a9df0
Faulting application path: c:\xampp\apache\bin\httpd.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

apache dont start. What is my problem, how can i find problem ?
*My ports are open for 80.

If i can press start button 8-9 times apache work, but Why doesn't it work the first time ?
by baskiki
17. December 2018 08:25
 
Forum: XAMPP for Windows
Topic: Apache not work: SSL:warn
Replies: 2
Views: 96

Unable to keep MySQL running on new install

I installed Xampp (for the 3rd time) and made sure that there were no conflicting ports before installing. I installed it to my P:/XAMPP folder and it claims to have installed without error.

I launch Apapche..no problems.
I launch MySQL and no problems at first, then it shuts down 20 seconds later and tells me to post this error log here:
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-11-13 01:30:14 93c 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-11-13 1:30:14 2364 [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-11-13 1:30:14 2364 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:30:14 2364 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:30:14 2364 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:30:14 2364 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:30:14 2364 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:30:14 2364 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:30:14 2364 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:30:14 2364 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:30:15 93c InnoDB: Operating system error number 6 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 close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:30:15 2364 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:30:15 [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.36-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 = 787136 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!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
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-11-13 01:30:59 5078 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-11-13 1:30:59 20600 [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-11-13 1:30:59 20600 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:30:59 20600 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:30:59 20600 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:30:59 20600 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:30:59 20600 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:30:59 20600 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:30:59 20600 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:30:59 20600 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:30:59 5078 InnoDB: Operating system error number 6 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 close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:30:59 20600 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:30:59 [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.36-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 = 787136 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!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
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-11-13 01:35:15 31f8 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-11-13 1:35:15 12792 [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-11-13 1:35:15 12792 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:35:15 12792 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:35:15 12792 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:35:15 12792 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:35:15 12792 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:35:15 12792 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:35:15 12792 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:35:15 12792 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:35:15 31f8 InnoDB: Operating system error number 6 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 close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:35:15 12792 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:35:15 [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.36-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 = 787136 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!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
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-11-13 01:35:46 1f3c 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-11-13 1:35:46 7996 [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-11-13 1:35:46 7996 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:35:46 7996 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:35:46 7996 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:35:46 7996 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:35:46 7996 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:35:46 7996 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:35:46 7996 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:35:46 7996 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:35:46 1f3c InnoDB: Operating system error number 6 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 close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:35:46 7996 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:35:46 [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.36-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 = 787136 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!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
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-11-13 01:36:38 29b4 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-11-13 1:36:38 10676 [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-11-13 1:36:38 10676 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:36:38 10676 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:36:38 10676 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:36:38 10676 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:36:38 10676 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:36:38 10676 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:36:38 10676 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:36:38 10676 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:36:39 29b4 InnoDB: Operating system error number 6 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 close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:36:39 10676 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:36:39 [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.36-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 = 787136 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!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
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.
---------------------------------------------------------

one thing I notices was this line in the innodb section: d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493

needless to say I don't have a d:\win32-packages\... file so perhaps thats the problem.

How do I fix it?

Steps taken: Installed MySQL Community server--didn't help. Uninstalled, Uninstalled XAMPP.
Reinstalled XAMPP - same problem
checked ports again
UNINSTALLED XAMPP AGAIN
reinstalled XAMPP - same problem.

I notice the build date on the control panel was 2015, is XAMPP dead or just old?

I'm going to try installing an even older version of XAMPP that worked previously. Perhaps that will solve it, but if anyone knows what the problem is, let me know. Thanks.
by jaseinatl
13. November 2018 07:48
 
Forum: XAMPP for Windows
Topic: Unable to keep MySQL running on new install
Replies: 0
Views: 275

Re: Unable to Start Apache Server

Same happen to me now.
This is from system log:
Bad application name: httpd.exe, version: 2.4.29.0, timestamp: 0x59ec685f
Name of the wrong module: ntdll.dll, version: 10.0.17134.376, time stamp: 0x4358e406
Exception code: 0xc0000005
Error shift: 0x00042144
Bad process ID: 0x13c0
Run Time for the Bad Application: 0x01d46eebe335b7a1
The path to the wrong application: C: \ xampp \ apache \ bin \ httpd.exe
The path to the failing module: C: \ WINDOWS \ SYSTEM32 \ ntdll.dll
Message ID: 69d0086d-ef3c-4147-adb8-a35c405ef208
Full name of the missing package:
Application ID related to the wrong package:
by strom
28. October 2018 20:01
 
Forum: XAMPP for Windows
Topic: Unable to Start Apache Server
Replies: 1
Views: 434

mysql stoppt

Hi myspl startet kurz und stoppt dann . Hinweis das evtl ports verweise etc nicht stimmen. Kann hier jemand helfen dies einzugrenzen?
Danke und Gruß.

mysqld.exe!my_parameter_handler()
mysqld.exe!?eq_cmp_result@Item@@UBE?AW4cond_result@1@XZ()
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!?std@field_str@@UAEPAVString@@PAV2@_K@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!?eq_cmp_result@Item@@UBE?AW4cond_result@1@XZ()
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-10-10 13:53:20 346c 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-10-10 13:53:20 13420 [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-10-10 13:53:20 13420 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-10-10 13:53:20 13420 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-10 13:53:20 13420 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-10-10 13:53:20 13420 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-10-10 13:53:20 13420 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-10 13:53:20 13420 [Note] InnoDB: Using generic crc32 instructions
2018-10-10 13:53:20 13420 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-10-10 13:53:20 13420 [Note] InnoDB: Completed initialization of buffer pool
2018-10-10 13:53:20 13420 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-10 13:53:20 13420 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number 560200424 in the ib_logfiles!
2018-10-10 13:53:20 13420 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mydb/matchscore uses space ID: 38 at filepath: .\mydb\matchscore.ibd. Cannot open tablespace plants/planta which uses space ID: 38 at filepath: .\plants\planta.ibd
InnoDB: Error: could not open single-table tablespace file .\plants\planta.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.
181010 13:53: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.33-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!?eq_cmp_result@Item@@UBE?AW4cond_result@1@XZ()
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()
by Karle
10. October 2018 13:51
 
Forum: XAMPP für Windows
Topic: mysql stoppt
Replies: 0
Views: 326

Fehlermeldung "mysqld funktioniert nicht mehr" - Ursache?

Ich knabber mich seit etwa 4 Wochen am mysql Dienst fest. Die installierte Version 3.2.2 von XAMPP auf einem Windows 7 Ultimate 32bit hatte immer funktioniert. Es gibt keinen nachvollziehbaren Grund, weshalb der Dienst nicht mehr funktioniert. Andere Datenbank-Anwendungen funktionieren problemlos, die Dienste werden ALLE (FireBird Datenbank für eine Buhl Data Büroanwendung) vorher deaktiviert und beendet.

Einen Fehler konnte ich beheben - in der my.ini waren die Pfade von XAMPP und mysql nicht korrekt. da hatte sich der Fehlerteufel eingeschlichen. Das habe ich korrigiert. Nun startet mysql, beendet sich aber nach ca. 10 Sekunden wieder. Ich habe von den Fehlermeldungen jeweils einen Screenshot gemacht.

Image

Image


Dazu hab ich noch das Logfile was mir aber auch nicht weiterhilft. Wahrscheinlich seh ich die Syntax vor lauter Codezeilen nicht mehr..... :mrgreen:

2018-09-16 13:47:06 1eec 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-09-16 13:47:06 7916 [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-09-16 13:47:06 7916 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-09-16 13:47:06 7916 [Note] InnoDB: The InnoDB memory heap is disabled
2018-09-16 13:47:06 7916 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-09-16 13:47:06 7916 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-09-16 13:47:06 7916 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-09-16 13:47:06 7916 [Note] InnoDB: Using generic crc32 instructions
2018-09-16 13:47:06 7916 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-09-16 13:47:06 7916 [Note] InnoDB: Completed initialization of buffer pool
2018-09-16 13:47:06 7916 [Note] InnoDB: Highest supported file format is Barracuda.
2018-09-16 13:47:06 7916 [Note] InnoDB: The log sequence number 1840393569 in ibdata file do not match the log sequence number 1840393579 in the ib_logfiles!
2018-09-16 13:47:10 7916 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace projekt_manager/FTS_0000000000000100_DELETED uses space ID: 243 at filepath: .\projekt_manager\fts_0000000000000100_deleted.ibd. Cannot open tablespace systemhausshop/s_emarketing_partner which uses space ID: 243 at filepath: .\systemhausshop\s_emarketing_partner.ibd
InnoDB: Error: could not open single-table tablespace file .\systemhausshop\s_emarketing_partner.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.
180916 13:47:10 [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.25-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 = 787107 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!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?fix_length_and_dec@subselect_partial_match_engine@@UAEXPAPAVItem_cache@@@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!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.


Hoffe auf eure Hilfe

Danke
by djmugge
16. September 2018 12:50
 
Forum: XAMPP für Windows
Topic: Fehlermeldung "mysqld funktioniert nicht mehr" - Ursache?
Replies: 0
Views: 335

Error: MySQL shutdown unexpectedly. Please Help

4:40:23 AM [main] Initializing Control Panel
4:40:23 AM [main] Windows Version: Windows 7 Ultimate SP1 64-bit
4:40:23 AM [main] XAMPP Version: 5.5.19
4:40:23 AM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
4:40:23 AM [main] Running with Administrator rights - good!
4:40:23 AM [main] XAMPP Installation Directory: "d:\xampp\"
4:40:23 AM [main] Checking for prerequisites
4:40:23 AM [main] All prerequisites found
4:40:23 AM [main] Initializing Modules
4:40:23 AM [Apache] Initializing module...
4:40:23 AM [Apache] Checking for module existence...
4:40:23 AM [Apache] Checking for required tools...
4:40:23 AM [Apache] Checking for service (name="Apache2.4"): Service not installed
4:40:23 AM [Apache] Service Path: Service Not Installed
4:40:23 AM [Apache] Checking default ports...
4:40:23 AM [mysql] Initializing module...
4:40:23 AM [mysql] Checking for module existence...
4:40:23 AM [mysql] Checking for required tools...
4:40:23 AM [mysql] Checking for service (name="mysql"): Service not installed
4:40:23 AM [mysql] Service Path: Service Not Installed
4:40:23 AM [mysql] Checking default ports...
4:40:23 AM [filezilla] Initializing module...
4:40:23 AM [filezilla] Checking for module existence...
4:40:23 AM [filezilla] Checking for required tools...
4:40:23 AM [filezilla] Checking for service (name="FileZillaServer"): Service not installed
4:40:23 AM [filezilla] Service Path: Service Not Installed
4:40:23 AM [filezilla] Checking default ports...
4:40:23 AM [mercury] Initializing module...
4:40:23 AM [mercury] Checking for module existence...
4:40:23 AM [mercury] Checking for required tools...
4:40:23 AM [mercury] Checking default ports...
4:40:23 AM [Tomcat] Initializing module...
4:40:23 AM [Tomcat] Checking for module existence...
4:40:23 AM [Tomcat] Checking for required tools...
4:40:23 AM [Tomcat] Checking for service (name="Tomcat7"): Service not installed
4:40:23 AM [Tomcat] Service Path: Service Not Installed
4:40:23 AM [Tomcat] Checking default ports...
4:40:23 AM [main] Starting Check-Timer
4:40:23 AM [main] Control Panel Ready
4:41:12 AM [mysql] Checking default ports...
4:41:12 AM [mysql] Attempting to start MySQL app...
4:41:12 AM [mysql] Executing ""d:\xampp\mysql\bin\mysqld.exe" --defaults-file="d:\xampp\mysql\bin\my.ini" --standalone"
4:41:12 AM [mysql] Return code: 0
4:41:13 AM [mysql] Status change detected: running
4:41:17 AM [mysql] Status change detected: stopped
4:41:17 AM [mysql] Error: MySQL shutdown unexpectedly.
4:41:17 AM [mysql] This may be due to a blocked port, missing dependencies,
4:41:17 AM [mysql] improper privileges, a crash, or a shutdown by another method.
4:41:17 AM [mysql] Press the Logs button to view error logs and check
4:41:17 AM [mysql] the Windows Event Viewer for more clues
4:41:17 AM [mysql] If you need more help, copy and post this
4:41:17 AM [mysql] entire log window on the forums


mysql_error.log

2018-09-14 04:44:24 4748 [Note] Plugin 'FEDERATED' is disabled.
2018-09-14 04:44:24 f7c 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-09-14 04:44:24 4748 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-09-14 04:44:24 4748 [Note] InnoDB: The InnoDB memory heap is disabled
2018-09-14 04:44:24 4748 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-09-14 04:44:24 4748 [Note] InnoDB: Memory barrier is not used
2018-09-14 04:44:24 4748 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-09-14 04:44:24 4748 [Note] InnoDB: Not using CPU crc32 instructions
2018-09-14 04:44:24 4748 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-09-14 04:44:24 4748 [Note] InnoDB: Completed initialization of buffer pool
2018-09-14 04:44:24 4748 [Note] InnoDB: Highest supported file format is Barracuda.
2018-09-14 04:44:24 4748 [Note] InnoDB: Log scan progressed past the checkpoint lsn 83106559
2018-09-14 04:44:24 4748 [Note] InnoDB: Database was not shutdown normally!
2018-09-14 04:44:24 4748 [Note] InnoDB: Starting crash recovery.
2018-09-14 04:44:24 4748 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-09-14 04:44:24 4748 [Note] InnoDB: Restoring possible half-written data pages
2018-09-14 04:44:24 4748 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 83106569
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 2220288
2018-09-14 04:44:24 4748 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2018-09-14 04:44:24 714 InnoDB: Rolling back trx with id 2197486, 0 rows to undo
2018-09-14 04:44:24 714 InnoDB: Assertion failure in thread 1812 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.
2018-09-14 04:44:24 4748 [Note] InnoDB:02:44:24 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.
WWe 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.

akey_buffer_size=16777216
iread_buffer_size=262144
tmax_used_connections=0
imax_threads=151
nthread_count=0
gconnection_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
fHope that's ok; if not, decrease some variables in the equation.

oThread pointer: 0x0
rAttempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
purge to start
2018-09-14 04:44:24 4748 [Note] InnoDB: 5.6.21 started; log sequence number 83106569
2018-09-14 04:44:24 4748 [Note] Server hostname (bind-address): '*'; port: 3306
14ac7c0 mysqld.exe!my_thread_name()
16e79ed mysqld.exe!my_mb_ctype_mb()
15fd2f6 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
1516177 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
2018-09-141600383 mysqld.exe!0?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()4
:44:24 4748 [Note] IPv6 is1544d19 mysqld.exe!a?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()v
ailable.
1547488 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
1547528 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
2018-09-14 04:44:1584713 2mysqld.exe!4?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
4748 [Note] - '::' 15856b7 rmysqld.exe!e?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()s
olves to '::';
1585802 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
2018-09-14 04:44:24 4748 [Note] Server socket created on IP: '::'.
158594c mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
779c97f2 ntdll.dll!RtlInitializeExceptionChain()
779c97c5 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.
2018-09-14 04:44:25 4748 [Note] Event Scheduler: Loaded 0 events
2018-09-14 04:44:25 4748 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.21' socket: '' port: 3306 MySQL Community Server (GPL)
by Hazm91
14. September 2018 03:48
 
Forum: XAMPP for Windows
Topic: Error: MySQL shutdown unexpectedly. Please Help
Replies: 0
Views: 445

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: 539

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: 962

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: 2557

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: 2190

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: 2534

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: 1089

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: 1414

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: 2534

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: 2711
Next

Return to advanced search