MYSQL shutdown unexpectedly in Window10

Problems with the Windows version of XAMPP, questions, comments, and anything related.

MYSQL shutdown unexpectedly in Window10

Postby dgupta330 » 15. March 2018 06:00

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
dgupta330
 
Posts: 1
Joined: 15. March 2018 05:55
XAMPP version: 3.2.2
Operating System: Window 10

Re: MYSQL shutdown unexpectedly in Window10

Postby mgsmus » 19. March 2018 08:29

Remove innodb_additional_mem_pool_size in my.ini
mgsmus
 
Posts: 2
Joined: 19. March 2018 08:14
XAMPP version: 7.2.3
Operating System: Windows 10 64bit


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 51 guests