Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-28156

MariaDB crash on SELECT with ORDER



    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.5.12
    • Fix Version/s: None
    • Component/s: Parser
    • Labels:
    • Environment:
      Raspberry PI4 ComputeModule 8GB RAM, raspian running from M2.SSD


      Every Time I make a SELECT query with an ORDER BY xyz, MariaDB crashes.
      SELECT without ORDER works.


      2022-03-23 14:03:42 305 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
      2022-03-23 14:03:42 305 [ERROR] InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation
      220323 14:03:42 [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.5.12-MariaDB-0+deb11u1-log
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 288092 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x2af0978
      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 = 0x93727c34 thread_stack 0x49000
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x2b04728): SELECT * FROM `Datastore`.`Grabenstrasse` ORDER BY `Timestamp` ASC LIMIT 100
      Connection ID (thread ID): 305
      Status: NOT_KILLED
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=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
      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 /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             60613                60613                processes
      Max open files            32768                32768                files
      Max locked memory         65536                65536                bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       60613                60613                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: core
      2022-03-23 14:03:47 0 [Note] InnoDB: Uses event mutexes
      2022-03-23 14:03:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-03-23 14:03:47 0 [Note] InnoDB: Number of pools: 1
      2022-03-23 14:03:47 0 [Note] InnoDB: Using generic crc32 instructions
      2022-03-23 14:03:47 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
      2022-03-23 14:03:47 0 [Note] InnoDB: Using Linux native AIO
      2022-03-23 14:03:47 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
      2022-03-23 14:03:47 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-03-23 14:03:47 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3947674098,3947674098
      2022-03-23 14:03:48 0 [Note] InnoDB: Starting final batch to recover 299 pages from redo log.
      2022-03-23 14:03:49 0 [Note] InnoDB: 128 rollback segments are active.
      2022-03-23 14:03:49 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-03-23 14:03:49 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-03-23 14:03:49 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-03-23 14:03:49 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-03-23 14:03:49 0 [Note] InnoDB: 10.5.12 started; log sequence number 3954941679; transaction id 36687178
      2022-03-23 14:03:49 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-03-23 14:03:49 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-03-23 14:03:49 0 [Note] Server socket created on IP: ''.
      2022-03-23 14:03:49 0 [Note] Reading of all Master_info entries succeeded
      2022-03-23 14:03:49 0 [Note] Added new Master_info '' to hash table
      2022-03-23 14:03:49 0 [Note] /usr/sbin/mariadbd: ready for connections.
      Version: '10.5.12-MariaDB-0+deb11u1-log'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Raspbian 11
      2022-03-23 14:03:49 0 [Note] InnoDB: Buffer pool(s) load completed at 220323 14:03:49




            Unassigned Unassigned
            MichaKC11 Michael Gerber
            0 Vote for this issue
            2 Start watching this issue



                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.