[MDEV-15766] regression with non default innodb_log_buffer_size Created: 2018-04-03  Updated: 2020-03-08

Status: Confirmed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2.14
Fix Version/s: 10.2

Type: Bug Priority: Major
Reporter: VAROQUI Stephane Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

On our docker provisioning system 10.2 stop being provisioned with some crash

/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f7a40e4256e]
/usr/sbin/mysqld(handle_fatal_signal+0x345)[0x7f7a408c1495]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f7a3fe08890]
/usr/sbin/mysqld(+0x86fb59)[0x7f7a40aa8b59]
/usr/sbin/mysqld(+0x92a45c)[0x7f7a40b6345c]
/usr/sbin/mysqld(+0x812329)[0x7f7a40a4b329]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x7f7a408c37e4]
/usr/sbin/mysqld(+0x4ee745)[0x7f7a40727745]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x8aa)[0x7f7a40728e5a]
/usr/sbin/mysqld(+0x44103e)[0x7f7a4067a03e]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x512)[0x7f7a4067f472]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f7a3e17fb45]
/usr/sbin/mysqld(+0x43913d)[0x7f7a4067213d]

I track it down to my payload and was able to get back to normal provisioning when not setting innodb_log_buffer_size

For the reference i was setting
innodb_log_buffer_size = 256M
BP of 256M and innodb_log_file_size of 4x64M

On a VM with 1.5G of memory !

Thanks



 Comments   
Comment by Daniel Black [ 2018-04-06 ]

Requires limit:

$ ulimit -v $(( 1500 * 1024 ))
$ mysql-test/mysql-test-run --verbose --mem --mysqld="--innodb_log_buffer_size=256M --innodb_log_file_size=64M --innodb-log-files-in-group=4" --suite=innodb
...
2018-04-06 16:11:59 139793185294528 [Note] InnoDB: 5.7.21 started; log sequence number 0
2018-04-06 16:11:59 0x7f242326c8c0  InnoDB: Assertion failure in file /home/dan/repos/mariadb-server-10.2/storage/innobase/os/os0thread.cc line 139
InnoDB: Failing assertion: ret == 0
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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/
InnoDB: about forcing recovery.
180406 16:11:59 [ERROR] mysqld got signal 6 ;
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.2.15-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 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...
stack_bottom = 0x0 thread_stack 0x49000
/home/dan/repos/build-mariadb-server-10.2/sql/mysqld(my_print_stacktrace+0x29)[0x56285722e439]
/home/dan/repos/build-mariadb-server-10.2/sql/mysqld(handle_fatal_signal+0x57b)[0x562856d764ab]
sigaction.c:0(__restore_rt)[0x7f2422e831b0]
:0(__GI_raise)[0x7f2420363660]
:0(__GI_abort)[0x7f2420364c41]
ut/ut0ut.cc:207(ut_print_timestamp(_IO_FILE*))[0x562856b57e5a]
os/os0thread.cc:145(os_thread_create_func(void* (*)(void*), void*, unsigned long*))[0x562856f4d2e0]
srv/srv0start.cc:2773(innobase_start_or_create_for_mysql())[0x562856fd5d93]
handler/ha_innodb.cc:4329(innobase_init(void*))[0x562856edb262]
sql/handler.cc:520(ha_initialize_handlerton(st_plugin_int*))[0x562856d784f7]
sql/sql_plugin.cc:1416(plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**, bool))[0x562856c0c780]
sql/sql_plugin.cc:1697(plugin_init(int*, char**, int))[0x562856c0d69a]
sql/mysqld.cc:5270(init_server_components())[0x562856b747aa]
sql/mysqld.cc:5861(mysqld_main(int, char**))[0x562856b7b529]
/lib64/libc.so.6(__libc_start_main+0xea)[0x7f242034ff2a]
/home/dan/repos/build-mariadb-server-10.2/sql/mysqld(_start+0x2a)[0x562856b6f15a]
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.
Writing a core file at /home/dan/repos/build-mariadb-server-10.2/mysql-test/var/install.db/
safe_process[28393]: Got signal 17, child_pid: 28394
safe_process[28393]: Killing child: 28394
safe_process[28393]: Child killed by signal: 6

Comment by Nicolas Richeton [ 2020-03-08 ]

Hello,

I got the same problem on 10.4 and 10.5 on docker . Host : Ubuntu 18.04.4 LTS.

TL DR
Maria suddenly crashes on restart when processing some temporary tables.
versions 10.4, 10.5, even with innodb_force_recovery.
I had to set innodb_buffer_pool_size & innodb_log_buffer_size back to maria defaults from documentation to get a successful restart.

innodb_log_buffer_size=16777216
innodb_buffer_pool_size=134217728

Initial Error with 10.4

2020-03-08 08:17:39+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.4.12+maria~bionic started.
2020-03-08 08:17:39+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2020-03-08 08:17:39+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.4.12+maria~bionic started.
2020-03-08  8:17:40 0 [Note] mysqld (mysqld 10.4.12-MariaDB-1:10.4.12+maria~bionic) starting as process 1 ...
2020-03-08  8:17:40 0 [Note] InnoDB: Using Linux native AIO
2020-03-08  8:17:40 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-08  8:17:40 0 [Note] InnoDB: Uses event mutexes
2020-03-08  8:17:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-03-08  8:17:40 0 [Note] InnoDB: Number of pools: 1
2020-03-08  8:17:40 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-08  8:17:40 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-03-08  8:17:40 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2020-03-08  8:17:40 0 [Note] InnoDB: Completed initialization of buffer pool
2020-03-08  8:17:40 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-08  8:17:40 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=157207710
2020-03-08  8:17:40 0 [Note] InnoDB: Starting final batch to recover 8 pages from redo log.
2020-03-08  8:17:40 0 [ERROR] InnoDB: Trying to load index `unique` for table `jeedom`.`#sql-1_15820`, but the index tree has been freed!
2020-03-08  8:17:40 0 [Note] InnoDB: Index is corrupt but forcing load into data dictionary
2020-03-08  8:17:40 0 [ERROR] InnoDB: Trying to load index `cmd_id_index` for table `jeedom`.`#sql-1_15820`, but the index tree has been freed!
2020-03-08  8:17:40 0 [Note] InnoDB: Index is corrupt but forcing load into data dictionary
200308  8:17:40 [ERROR] mysqld got signal 11 ;
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.4.12-MariaDB-1:10.4.12+maria~bionic
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=102
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760255 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...
stack_bottom = 0x0 thread_stack 0x49000
mysqld(my_print_stacktrace+0x2e)[0x563db64d7c3e]
mysqld(handle_fatal_signal+0x515)[0x563db5f4bcf5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f6699ad6890]
mysqld(+0xbee54b)[0x563db62c554b]
mysqld(+0xbeee71)[0x563db62c5e71]
mysqld(+0xaee273)[0x563db61c5273]
mysqld(+0xa765ae)[0x563db614d5ae]
mysqld(+0xb291da)[0x563db62001da]
mysqld(+0xa1628b)[0x563db60ed28b]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x62)[0x563db5f4ed52]
mysqld(+0x674c09)[0x563db5d4bc09]
mysqld(_Z11plugin_initPiPPci+0x84a)[0x563db5d4cdea]
mysqld(+0x59e3f9)[0x563db5c753f9]
mysqld(_Z11mysqld_mainiPPc+0x566)[0x563db5c7b8d6]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f66983edb97]
mysqld(_start+0x2a)[0x563db5c6f4ea]
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.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             11640                11640                processes 
Max open files            2048                 8192                 files     
Max locked memory         16777216             16777216             bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       11640                11640                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        

Error with 10.4 (innodb_force_recovery=1)

2020-03-08 08:45:06+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.4.12+maria~bionic started.
2020-03-08 08:45:07+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2020-03-08 08:45:07+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.4.12+maria~bionic started.
2020-03-08  8:45:07 0 [Note] mysqld (mysqld 10.4.12-MariaDB-1:10.4.12+maria~bionic) starting as process 1 ...
2020-03-08  8:45:07 0 [Note] InnoDB: Using Linux native AIO
2020-03-08  8:45:07 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-08  8:45:07 0 [Note] InnoDB: Uses event mutexes
2020-03-08  8:45:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-03-08  8:45:07 0 [Note] InnoDB: Number of pools: 1
2020-03-08  8:45:07 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-08  8:45:07 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-03-08  8:45:07 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2020-03-08  8:45:08 0 [Note] InnoDB: Completed initialization of buffer pool
2020-03-08  8:45:08 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-08  8:45:08 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=157207710
2020-03-08  8:45:08 0 [Note] InnoDB: Starting final batch to recover 8 pages from redo log.
2020-03-08  8:45:08 0 [ERROR] InnoDB: Trying to load index `unique` for table `jeedom`.`#sql-1_15820`, but the index tree has been freed!
2020-03-08  8:45:08 0 [Note] InnoDB: Index is corrupt but forcing load into data dictionary
2020-03-08  8:45:08 0 [ERROR] InnoDB: Trying to load index `cmd_id_index` for table `jeedom`.`#sql-1_15820`, but the index tree has been freed!
2020-03-08  8:45:08 0 [Note] InnoDB: Index is corrupt but forcing load into data dictionary
200308  8:45:08 [ERROR] mysqld got signal 11 ;
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.4.12-MariaDB-1:10.4.12+maria~bionic
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=102
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760255 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...
stack_bottom = 0x0 thread_stack 0x49000
mysqld(my_print_stacktrace+0x2e)[0x5617d77d0c3e]
mysqld(handle_fatal_signal+0x515)[0x5617d7244cf5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f3d68912890]
mysqld(+0xbee54b)[0x5617d75be54b]
mysqld(+0xbeee71)[0x5617d75bee71]
mysqld(+0xaee273)[0x5617d74be273]
mysqld(+0xa765ae)[0x5617d74465ae]
mysqld(+0xb291da)[0x5617d74f91da]
mysqld(+0xa1628b)[0x5617d73e628b]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x62)[0x5617d7247d52]
mysqld(+0x674c09)[0x5617d7044c09]
mysqld(_Z11plugin_initPiPPci+0x84a)[0x5617d7045dea]
mysqld(+0x59e3f9)[0x5617d6f6e3f9]
mysqld(_Z11mysqld_mainiPPc+0x566)[0x5617d6f748d6]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f3d67229b97]
mysqld(_start+0x2a)[0x5617d6f684ea]
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.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             11640                11640                processes 
Max open files            2048                 8192                 files     
Max locked memory         16777216             16777216             bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       11640                11640                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        

Error with 10.5 (innodb_force_recovery=1 & innodb_log_buffer_size=16777216)

2020-03-08 08:58:15+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.1+maria~bionic started.
2020-03-08 08:58:17+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2020-03-08 08:58:17+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.1+maria~bionic started.
2020-03-08  8:58:18 0 [Note] mysqld (mysqld 10.5.1-MariaDB-1:10.5.1+maria~bionic) starting as process 1 ...
2020-03-08  8:58:18 0 [Note] InnoDB: Using Linux native AIO
2020-03-08  8:58:18 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-08  8:58:18 0 [Note] InnoDB: Uses event mutexes
2020-03-08  8:58:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-03-08  8:58:18 0 [Note] InnoDB: Number of pools: 1
2020-03-08  8:58:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-08  8:58:18 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-03-08  8:58:18 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
2020-03-08  8:58:18 0 [Note] InnoDB: Completed initialization of buffer pool
2020-03-08  8:58:18 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-08  8:58:18 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=157207710
2020-03-08  8:58:18 0 [Note] InnoDB: Starting final batch to recover 8 pages from redo log.
2020-03-08  8:58:19 0 [Note] InnoDB: Resizing redo log from 2*50331648 to 1*100663296 bytes; LSN=157210980
2020-03-08  8:58:21 0 [Note] InnoDB: Starting to delete and rewrite log files.
2020-03-08  8:58:21 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 100663296 bytes
2020-03-08  8:58:21 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2020-03-08  8:58:21 0 [Note] InnoDB: New log files created, LSN=157210980
2020-03-08  8:58:21 0 [Note] InnoDB: 128 rollback segments are active.
2020-03-08  8:58:21 0 [ERROR] InnoDB: Trying to load index `unique` for table `jeedom`.`#sql-1_15820`, but the index tree has been freed!
2020-03-08  8:58:21 0 [Note] InnoDB: Index is corrupt but forcing load into data dictionary
2020-03-08  8:58:21 0 [ERROR] InnoDB: Trying to load index `cmd_id_index` for table `jeedom`.`#sql-1_15820`, but the index tree has been freed!
2020-03-08  8:58:21 0 [Note] InnoDB: Index is corrupt but forcing load into data dictionary
200308  8:58:21 [ERROR] mysqld got signal 11 ;
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.5.1-MariaDB-1:10.5.1+maria~bionic
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=102
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760270 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...
stack_bottom = 0x0 thread_stack 0x49000
mysqld(my_print_stacktrace+0x2e)[0x55ae6831379e]
Printing to addr2line failed
mysqld(handle_fatal_signal+0x515)[0x55ae67d573c5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f108818f890]
mysqld(+0xd53e33)[0x55ae681eee33]
mysqld(+0xd54741)[0x55ae681ef741]
mysqld(+0xc5028b)[0x55ae680eb28b]
mysqld(+0xc8866f)[0x55ae6812366f]
mysqld(+0xb7bd12)[0x55ae68016d12]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x66)[0x55ae67d5a146]
mysqld(+0x6dc309)[0x55ae67b77309]
mysqld(_Z11plugin_initPiPPci+0x87a)[0x55ae67b7852a]
mysqld(+0x603559)[0x55ae67a9e559]
mysqld(_Z11mysqld_mainiPPc+0x4dc)[0x55ae67aa41ac]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f1087482b97]
mysqld(_start+0x2a)[0x55ae67a985da]
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.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             11640                11640                processes 
Max open files            6535                 6535                 files     
Max locked memory         16777216             16777216             bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       11640                11640                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        
Core pattern: |/usr/share/apport/apport %p %s %c %d %P

Success with 10.5 (innodb_force_recovery=1 & innodb_log_buffer_size=16777216 & innodb_buffer_pool_size=134217728)

2020-03-08 08:58:24+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.1+maria~bionic started.
2020-03-08 08:58:24+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2020-03-08 08:58:24+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.1+maria~bionic started.
2020-03-08  8:58:25 0 [Note] mysqld (mysqld 10.5.1-MariaDB-1:10.5.1+maria~bionic) starting as process 1 ...
2020-03-08  8:58:25 0 [Note] InnoDB: Using Linux native AIO
2020-03-08  8:58:25 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-08  8:58:25 0 [Note] InnoDB: Uses event mutexes
2020-03-08  8:58:25 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-03-08  8:58:25 0 [Note] InnoDB: Number of pools: 1
2020-03-08  8:58:25 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-08  8:58:25 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-03-08  8:58:25 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
2020-03-08  8:58:25 0 [Note] InnoDB: Completed initialization of buffer pool
2020-03-08  8:58:25 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-08  8:58:25 0 [Note] InnoDB: The log sequence number 157210980 in the system tablespace does not match the log sequence number 157211148 in the ib_logfiles!
2020-03-08  8:58:25 0 [Note] InnoDB: 128 rollback segments are active.
2020-03-08  8:58:25 0 [Note] InnoDB: Deleting ./jeedom/#sql-1_15820.ibd
2020-03-08  8:58:25 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-03-08  8:58:25 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-03-08  8:58:25 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-03-08  8:58:25 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-03-08  8:58:25 0 [Note] InnoDB: 10.5.1 started; log sequence number 157211148; transaction id 179646
2020-03-08  8:58:25 0 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!!
2020-03-08  8:58:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-03-08  8:58:25 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2020-03-08  8:58:26 0 [Note] Server socket created on IP: '::'.
2020-03-08  8:58:26 0 [Note] Reading of all Master_info entries succeeded
2020-03-08  8:58:26 0 [Note] Added new Master_info '' to hash table
2020-03-08  8:58:26 0 [Note] mysqld: ready for connections.
Version: '10.5.1-MariaDB-1:10.5.1+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution

Note:
I have a backup of the data which causes this, I can do some testing if required.

Thanks,

Nicolas

Generated at Thu Feb 08 08:23:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.