Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Hello,
I'm facing the issue of starting a bitnami mariadb service. I got an error.
Please help
Error
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 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
|
/opt/bitnami/mariadb/sbin/mysqld(my_print_stacktrace+0x29)[0x55b05e7ceaa9]
|
/opt/bitnami/mariadb/sbin/mysqld(handle_fatal_signal+0x53d)[0x55b05e35292d]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fb84a715730]
|
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7fb84a5797bb]
|
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7fb84a564535]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x4e3d6b)[0x55b05e0aad6b]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x4e6520)[0x55b05e0ad520]
|
/opt/bitnami/mariadb/sbin/mysqld(+0xa293ca)[0x55b05e5f03ca]
|
/opt/bitnami/mariadb/sbin/mysqld(+0xa2de08)[0x55b05e5f4e08]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x92b1dd)[0x55b05e4f21dd]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x92b3ea)[0x55b05e4f23ea]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x931135)[0x55b05e4f8135]
|
/opt/bitnami/mariadb/sbin/mysqld(+0xa44803)[0x55b05e60b803]
|
/opt/bitnami/mariadb/sbin/mysqld(+0xa941fe)[0x55b05e65b1fe]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x9d7880)[0x55b05e59e880]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7fb84a70afa3]
|
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fb84a63b4cf]
|
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
|
information that should help you find out what is causing the crash.
|
Writing a core file...
|
Working directory at /bitnami/mariadb/data
|
Resource Limits:
|
Fatal signal 11 while backtracing
|
2022-03-14 14:21:46 0 [Note] InnoDB: Using Linux native AIO
|
2022-03-14 14:21:46 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
2022-03-14 14:21:46 0 [Note] InnoDB: Uses event mutexes
|
2022-03-14 14:21:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
|
2022-03-14 14:21:46 0 [Note] InnoDB: Number of pools: 1
|
2022-03-14 14:21:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
|
2022-03-14 14:21:46 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
|
2022-03-14 14:21:46 0 [Note] InnoDB: Completed initialization of buffer pool
|
2022-03-14 14:21:46 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
|
2022-03-14 14:21:46 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=2884091329770
|
2022-03-14 14:21:46 0 [Note] InnoDB: Starting final batch to recover 1022 pages from redo log.
|
2022-03-14 14:21:46 0x7f3a93cfa700 InnoDB: Assertion failure in file /bitnami/blacksmith-sandox/mariadb-10.3.31/storage/innobase/btr/btr0cur.cc line 340
|
InnoDB: Failing assertion: btr_page_get_prev(get_block->frame) == page_get_page_no(page)
|
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/innodb-recovery-modes/
|
InnoDB: about forcing recovery.
|
220314 14:21:46 [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.3.31-MariaDB
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=153
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 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
|
/opt/bitnami/mariadb/sbin/mysqld(my_print_stacktrace+0x29)[0x557b7439baa9]
|
/opt/bitnami/mariadb/sbin/mysqld(handle_fatal_signal+0x53d)[0x557b73f1f92d]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f3b49002730]
|
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f3b48e667bb]
|
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f3b48e51535]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x4e3d6b)[0x557b73c77d6b]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x4e6520)[0x557b73c7a520]
|
/opt/bitnami/mariadb/sbin/mysqld(+0xa293ca)[0x557b741bd3ca]
|
/opt/bitnami/mariadb/sbin/mysqld(+0xa2de08)[0x557b741c1e08]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x92b1dd)[0x557b740bf1dd]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x92b3ea)[0x557b740bf3ea]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x931135)[0x557b740c5135]
|
/opt/bitnami/mariadb/sbin/mysqld(+0xa44803)[0x557b741d8803]
|
/opt/bitnami/mariadb/sbin/mysqld(+0xa941fe)[0x557b742281fe]
|
/opt/bitnami/mariadb/sbin/mysqld(+0x9d7880)[0x557b7416b880]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7f3b48ff7fa3]
|
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f3b48f284cf]
|
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
|
information that should help you find out what is causing the crash.
|
Writing a core file...
|
Working directory at /bitnami/mariadb/data
|
Resource Limits:
|
Fatal signal 11 while backtracing
|