Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Incomplete
-
11.3.2
-
None
-
Arch Linux for ARM 6.6.30-4-rpi (Raspberry Pi 3)
Description
running "SHOW GLOBAL STATUS" results in mariadbd crashing from a SIGBUS error. This is problematic as a SQL manager I would like to use always opens sessions with "SHOW GLOBAL STATUS."
Crash log from journalctl:
May 19 09:55:11 washu-chan mariadbd[2530]: Sorry, we probably made a mistake, and this is a bug.
|
May 19 09:55:11 washu-chan mariadbd[2530]: Your assistance in bug reporting will enable us to fix this for the next release.
|
May 19 09:55:11 washu-chan mariadbd[2530]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
May 19 09:55:11 washu-chan mariadbd[2530]: We will try our best to scrape up some info that will hopefully help
|
May 19 09:55:11 washu-chan mariadbd[2530]: diagnose the problem, but since we have already crashed,
|
May 19 09:55:11 washu-chan mariadbd[2530]: something is definitely wrong and this may fail.
|
May 19 09:55:11 washu-chan mariadbd[2530]: Server version: 11.3.2-MariaDB source revision: 068a6819eb63bcb01fdfa037c9bf3bf63c33ee42
|
May 19 09:55:11 washu-chan mariadbd[2530]: key_buffer_size=134217728
|
May 19 09:55:11 washu-chan mariadbd[2530]: read_buffer_size=131072
|
May 19 09:55:11 washu-chan mariadbd[2530]: max_used_connections=1
|
May 19 09:55:11 washu-chan mariadbd[2530]: max_threads=153
|
May 19 09:55:11 washu-chan mariadbd[2530]: thread_count=1
|
May 19 09:55:11 washu-chan mariadbd[2530]: It is possible that mysqld could use up to
|
May 19 09:55:11 washu-chan mariadbd[2530]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466639 K bytes of memory
|
May 19 09:55:11 washu-chan mariadbd[2530]: Hope that's ok; if not, decrease some variables in the equation.
|
May 19 09:55:11 washu-chan mariadbd[2530]: Thread pointer: 0xae713358
|
May 19 09:55:11 washu-chan mariadbd[2530]: Attempting backtrace. You can use the following information to find out
|
May 19 09:55:11 washu-chan mariadbd[2530]: where mysqld died. If you see no messages after this, something went
|
May 19 09:55:11 washu-chan mariadbd[2530]: terribly wrong...
|
May 19 09:55:11 washu-chan mariadbd[2530]: stack_bottom = 0x98f3624c thread_stack 0x49000
|
May 19 09:55:36 washu-chan mariadbd[2530]: /usr/bin/mariadbd(my_print_stacktrace+0x34)[0x10e3d44]
|
May 19 09:55:36 washu-chan mariadbd[2530]: /usr/bin/mariadbd(handle_fatal_signal+0x338)[0xbfa750]
|
May 19 09:55:36 washu-chan mariadbd[2530]: /usr/lib/libc.so.6(__default_sa_restorer+0x0)[0xb63d3be0]
|
May 19 09:55:36 washu-chan mariadbd[2530]: Trying to get some variables.
|
May 19 09:55:36 washu-chan mariadbd[2530]: Some pointers may be invalid and cause the dump to abort.
|
May 19 09:55:36 washu-chan mariadbd[2530]: Query (0x98ecf168): show global status
|
May 19 09:55:36 washu-chan mariadbd[2530]: Connection ID (thread ID): 3
|
May 19 09:55:36 washu-chan mariadbd[2530]: Status: NOT_KILLED
|
May 19 09:55:36 washu-chan mariadbd[2530]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=on,cset_narrowing=off,sargable_casefold=on
|
May 19 09:55:36 washu-chan mariadbd[2530]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
|
May 19 09:55:36 washu-chan mariadbd[2530]: information that should help you find out what is causing the crash.
|
May 19 09:55:36 washu-chan mariadbd[2530]: Writing a core file...
|
May 19 09:55:36 washu-chan mariadbd[2530]: Working directory at /var/lib/mysql
|
May 19 09:55:36 washu-chan mariadbd[2530]: Resource Limits:
|
May 19 09:55:36 washu-chan mariadbd[2530]: Limit Soft Limit Hard Limit Units
|
May 19 09:55:36 washu-chan mariadbd[2530]: Max cpu time unlimited unlimited seconds
|
May 19 09:55:36 washu-chan mariadbd[2530]: Max file size unlimited unlimited bytes
|
May 19 09:55:36 washu-chan mariadbd[2530]: Max data size unlimited unlimited bytes
|
May 19 09:55:36 washu-chan mariadbd[2530]: Max stack size 8388608 unlimited bytes
|
May 19 09:55:36 washu-chan mariadbd[2530]: Max core file size unlimited unlimited bytes
|
May 19 09:55:36 washu-chan mariadbd[2530]: Max resident set unlimited unlimited bytes
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max processes 5230 5230 processes
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max open files 32768 32768 files
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max locked memory 524288 524288 bytes
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max address space unlimited unlimited bytes
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max file locks unlimited unlimited locks
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max pending signals 5230 5230 signals
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max msgqueue size 819200 819200 bytes
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max nice priority 0 0
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max realtime priority 0 0
|
May 19 09:56:21 washu-chan mariadbd[2530]: Max realtime timeout unlimited unlimited us
|
May 19 09:56:21 washu-chan mariadbd[2530]: Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
|
May 19 09:56:21 washu-chan mariadbd[2530]: Kernel version: Linux version 6.6.30-4-rpi (builduser@leming) (armv7l-unknown-linux-gnueabihf-gcc (GCC) 14.1.1 20240507, GNU ld (GNU Binutils) 2.42.0) #1 SMP Wed May 15 08:33:05 MDT 2024
|