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.35-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...
|
2018-10-05 18:34:39 20f4 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-05 18:34:39 8436 [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-05 18:34:39 8436 [Note] InnoDB: Using mutexes to ref count buffer pool pages
|
2018-10-05 18:34:39 8436 [Note] InnoDB: The InnoDB memory heap is disabled
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
|
2018-10-05 18:34:39 8436 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Compressed tables use zlib 1.2.3
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Using generic crc32 instructions
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Initializing buffer pool, size = 16.0M
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Completed initialization of buffer pool
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Highest supported file format is Barracuda.
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Starting crash recovery from checkpoint LSN=58688853
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
|
2018-10-05 18:34:39 8436 [Note] InnoDB: Starting final batch to recover 19 pages from redo log
|
2018-10-05 18:34:39 ff4 InnoDB: Assertion failure in thread 4084 in file rem0rec.cc line 581
|
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.
|
181005 18:34: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.35-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...
|
2018-10-05 18:34:39 1994 2018-10-05 18:34:42 18b8 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-05 18:34:42 6328 [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-05 18:34:42 6328 [Note] InnoDB: Using mutexes to ref count buffer pool pages
|
2018-10-05 18:34:42 6328 [Note] InnoDB: The InnoDB memory heap is disabled
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
|
2018-10-05 18:34:42 6328 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Compressed tables use zlib 1.2.3
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Using generic crc32 instructions
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Initializing buffer pool, size = 16.0M
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Completed initialization of buffer pool
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Highest supported file format is Barracuda.
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Starting crash recovery from checkpoint LSN=58688853
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
|
2018-10-05 18:34:42 6328 [Note] InnoDB: Starting final batch to recover 19 pages from redo log
|
2018-10-05 18:34:42 1d8c InnoDB: Assertion failure in thread 7564 in file rem0rec.cc line 581
|
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.
|
181005 18:34:42 [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.35-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...
|
Bug
Major
