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

mysqld got signal 6 ;

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not a Bug
    • 10.3.36
    • N/A
    • Linux 4.19.0-21-amd64 #1 SMP Debian 4.19.249-2 (2022-06-30) x86_64 GNU/Linux

    Description

      Hi,

      I am newbie in the matter so first of all my apology if I got some of the tags wrong, and if my description is incomplete.

      My database randomly stopped working without me doing something different than what I regularly do. I killed a python script that was sending queries to it, maybe that's what caused the issue, I can't tell for sure.

      My main ask is for you to help me recover it fully, or at least some of the tables/schema, if you have the time for it of course

      Below are two block of texts, the first is the result of `systemctl status mariadb`, the second is the content of `/var/log/mysql/error.log` :

       mariadb.service - MariaDB 10.3.36 database server
         Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
         Active: activating (auto-restart) (Result: signal) since Sun 2022-12-18 16:19:40 CET; 2s ago
           Docs: man:mysqld(8)
                 https://mariadb.com/kb/en/library/systemd/
        Process: 18940 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
        Process: 18941 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
        Process: 18943 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $?
        Process: 19101 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
        Process: 19140 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
        Process: 19143 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
       Main PID: 19101 (code=killed, signal=ABRT)
         Status: "Taking your SQL requests now..."
       
      Dec 18 16:19:40 v2202207179557195704 systemd[1]: mariadb.service: Failed with result 'signal'.
      
      

      2022-12-18 16:22:26 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:22:26 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:22:26 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:22:26 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:22:26 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:22:26 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:22:27 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:22:27 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:22:27 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:22:27 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:22:27 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:22:28 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:22:28 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:22:28 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:22:28 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:22:28 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:22:28 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017226827; transaction id 7589834735
      2022-12-18 16:22:28 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:22:28 0x7f154f36b700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:22:28 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=4
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f1540000c08
      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 = 0x7f154f36ad58 thread_stack 0x49000
      2022-12-18 16:22:28 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:22:28 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:22:28 0 [Note] Starting crash recovery...
      2022-12-18 16:22:28 0 [Note] Crash recovery finished.
      2022-12-18 16:22:28 0 [Note] Server socket created on IP: '::'.
      2022-12-18 16:22:28 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:22:28 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:22:28 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x562047420bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x562046f490bd]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f1a9d1b9730]
      linux/raise.c:51(__GI_raise)[0x7f1a9d01e8eb]
      stdlib/abort.c:81(__GI_abort)[0x7f1a9d009535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x562046c87ddb]
      /usr/sbin/mysqld(+0x4e690b)[0x562046c8490b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x5620471b9cd1]
      /usr/sbin/mysqld(+0xa1c112)[0x5620471ba112]
      /usr/sbin/mysqld(+0xa0819b)[0x5620471a619b]
      nptl/pthread_create.c:487(start_thread)[0x7f1a9d1aefa3]
      x86_64/clone.S:97(clone)[0x7f1a9d0e006f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 1
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      2022-12-18 16:22:31 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:22:31 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:22:31 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:22:31 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:22:31 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:22:31 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:22:31 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:22:32 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:22:32 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:22:32 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:22:32 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:22:32 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:22:32 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:22:32 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:22:32 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:22:32 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:22:32 0 [Note] InnoDB: Waiting for purge to start
      2022-12-18 16:22:32 0x7f21fa023700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:22:32 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=4
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f21ec000c08
      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 = 0x7f21fa022d58 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55a4d6516bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55a4d603f0bd]
      2022-12-18 16:22:32 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017228253; transaction id 7589834746
      2022-12-18 16:22:32 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:22:32 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:22:32 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:22:32 0 [Note] Starting crash recovery...
      2022-12-18 16:22:32 0 [Note] Crash recovery finished.
      2022-12-18 16:22:32 0 [Note] Server socket created on IP: '::'.
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f2747776730]
      2022-12-18 16:22:32 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:22:32 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:22:32 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      linux/raise.c:51(__GI_raise)[0x7f27475db8eb]
      stdlib/abort.c:81(__GI_abort)[0x7f27475c6535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x55a4d5d7dddb]
      /usr/sbin/mysqld(+0x4e690b)[0x55a4d5d7a90b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x55a4d62afcd1]
      /usr/sbin/mysqld(+0xa1c112)[0x55a4d62b0112]
      /usr/sbin/mysqld(+0xa0819b)[0x55a4d629c19b]
      nptl/pthread_create.c:487(start_thread)[0x7f274776bfa3]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f274769d06f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 1
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      2022-12-18 16:22:39 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:22:39 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:22:39 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:22:39 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:22:39 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:22:39 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:22:39 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:22:39 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:22:39 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:22:39 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:22:39 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:22:40 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:22:40 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:22:40 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:22:40 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:22:40 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:22:40 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017229454; transaction id 7589834756
      2022-12-18 16:22:40 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:22:40 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:22:40 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:22:40 0 [Note] Starting crash recovery...
      2022-12-18 16:22:40 0 [Note] Crash recovery finished.
      2022-12-18 16:22:40 0x7f1d4336b700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:22:40 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=5
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f1d34000c08
      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 = 0x7f1d4336ad58 thread_stack 0x49000
      2022-12-18 16:22:40 0 [Note] Server socket created on IP: '::'.
      2022-12-18 16:22:40 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:22:40 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:22:40 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x558f6c856bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x558f6c37f0bd]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f2291114730]
      linux/raise.c:51(__GI_raise)[0x7f2290f798eb]
      stdlib/abort.c:81(__GI_abort)[0x7f2290f64535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x558f6c0bdddb]
      /usr/sbin/mysqld(+0x4e690b)[0x558f6c0ba90b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x558f6c5efcd1]
      /usr/sbin/mysqld(+0xa1c112)[0x558f6c5f0112]
      /usr/sbin/mysqld(+0xa0819b)[0x558f6c5dc19b]
      nptl/pthread_create.c:487(start_thread)[0x7f2291109fa3]
      x86_64/clone.S:97(clone)[0x7f229103b06f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 1
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      2022-12-18 16:22:46 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:22:46 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:22:46 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:22:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:22:46 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:22:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:22:46 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:22:47 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:22:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:22:47 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:22:47 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:22:47 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:22:47 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:22:47 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:22:47 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:22:47 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:22:47 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017229454; transaction id 7589834756
      2022-12-18 16:22:47 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:22:47 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:22:47 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:22:47 0 [Note] Starting crash recovery...
      2022-12-18 16:22:47 0 [Note] Crash recovery finished.
      2022-12-18 16:22:47 0x7fcce9dc2700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:22:47 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=5
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fccdc000c08
      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 = 0x7fcce9dc1d58 thread_stack 0x49000
      2022-12-18 16:22:47 0 [Note] Server socket created on IP: '::'.
      2022-12-18 16:22:47 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:22:47 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:22:47 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5617ae3f8bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x5617adf210bd]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fd2376b2730]
      linux/raise.c:51(__GI_raise)[0x7fd2375178eb]
      stdlib/abort.c:81(__GI_abort)[0x7fd237502535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x5617adc5fddb]
      /usr/sbin/mysqld(+0x4e690b)[0x5617adc5c90b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x5617ae191cd1]
      /usr/sbin/mysqld(+0xa1c112)[0x5617ae192112]
      /usr/sbin/mysqld(+0xa0819b)[0x5617ae17e19b]
      nptl/pthread_create.c:487(start_thread)[0x7fd2376a7fa3]
      x86_64/clone.S:97(clone)[0x7fd2375d906f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 1
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      2022-12-18 16:22:54 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:22:54 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:22:54 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:22:54 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:22:54 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:22:54 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:22:54 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:22:54 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:22:54 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:22:55 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:22:55 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:22:56 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:22:56 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:22:56 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:22:56 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:22:56 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:22:56 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017229454; transaction id 7589834756
      2022-12-18 16:22:56 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:22:56 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:22:56 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:22:56 0 [Note] Starting crash recovery...
      2022-12-18 16:22:56 0 [Note] Crash recovery finished.
      2022-12-18 16:22:56 0 [Note] Server socket created on IP: '::'.
      2022-12-18 16:22:56 0x7fe5da901700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:22:56 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=5
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fe5d0000c08
      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 = 0x7fe5da900d58 thread_stack 0x49000
      2022-12-18 16:22:56 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:22:56 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:22:56 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55d4e1ff5bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55d4e1b1e0bd]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7feb289ac730]
      linux/raise.c:51(__GI_raise)[0x7feb288118eb]
      stdlib/abort.c:81(__GI_abort)[0x7feb287fc535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x55d4e185cddb]
      /usr/sbin/mysqld(+0x4e690b)[0x55d4e185990b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x55d4e1d8ecd1]
      /usr/sbin/mysqld(+0xa1c112)[0x55d4e1d8f112]
      /usr/sbin/mysqld(+0xa0819b)[0x55d4e1d7b19b]
      nptl/pthread_create.c:487(start_thread)[0x7feb289a1fa3]
      x86_64/clone.S:97(clone)[0x7feb288d306f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 1
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      2022-12-18 16:23:02 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:23:02 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:23:02 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:23:02 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:23:02 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:23:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:23:02 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:23:02 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:23:02 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:23:02 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:23:02 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:23:03 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:23:03 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:23:03 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:23:03 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:23:03 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:23:03 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017229454; transaction id 7589834756
      2022-12-18 16:23:03 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:23:03 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:23:03 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:23:03 0 [Note] Starting crash recovery...
      2022-12-18 16:23:03 0 [Note] Crash recovery finished.
      2022-12-18 16:23:03 0 [Note] Server socket created on IP: '::'.
      2022-12-18 16:23:03 0x7fe1851b5700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:23:03 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=5
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fe178000c08
      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...
      2022-12-18 16:23:03 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:23:03 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:23:03 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      stack_bottom = 0x7fe1851b4d58 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55eb0ad07bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55eb0a8300bd]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fe6d28c7730]
      linux/raise.c:51(__GI_raise)[0x7fe6d272c8eb]
      stdlib/abort.c:81(__GI_abort)[0x7fe6d2717535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x55eb0a56eddb]
      /usr/sbin/mysqld(+0x4e690b)[0x55eb0a56b90b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x55eb0aaa0cd1]
      /usr/sbin/mysqld(+0xa1c112)[0x55eb0aaa1112]
      /usr/sbin/mysqld(+0xa0819b)[0x55eb0aa8d19b]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7fe6d28bcfa3]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fe6d27ee06f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 2
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      2022-12-18 16:23:10 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:23:10 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:23:10 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:23:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:23:10 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:23:10 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:23:10 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:23:10 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:23:10 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:23:10 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:23:10 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:23:11 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:23:11 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:23:11 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:23:11 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:23:11 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:23:11 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017230203; transaction id 7589834756
      2022-12-18 16:23:11 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:23:11 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:23:11 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:23:11 0 [Note] Starting crash recovery...
      2022-12-18 16:23:11 0 [Note] Crash recovery finished.
      2022-12-18 16:23:11 0 [Note] Server socket created on IP: '::'.
      2022-12-18 16:23:11 0x7fd4ee698700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:23:11 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=6
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fd4e8000c08
      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 = 0x7fd4ee697d58 thread_stack 0x49000
      2022-12-18 16:23:11 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:23:11 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:23:11 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x561544305bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x561543e2e0bd]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fda3c8d0730]
      linux/raise.c:51(__GI_raise)[0x7fda3c7358eb]
      stdlib/abort.c:81(__GI_abort)[0x7fda3c720535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x561543b6cddb]
      /usr/sbin/mysqld(+0x4e690b)[0x561543b6990b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x56154409ecd1]
      /usr/sbin/mysqld(+0xa1c112)[0x56154409f112]
      /usr/sbin/mysqld(+0xa0819b)[0x56154408b19b]
      nptl/pthread_create.c:487(start_thread)[0x7fda3c8c5fa3]
      x86_64/clone.S:97(clone)[0x7fda3c7f706f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 2
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      2022-12-18 16:23:18 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:23:18 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:23:18 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:23:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:23:18 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:23:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:23:18 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:23:18 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:23:18 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:23:18 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:23:18 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:23:19 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:23:19 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:23:19 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:23:19 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:23:19 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:23:19 0 [Note] InnoDB: Waiting for purge to start
      2022-12-18 16:23:19 0x7f38958f0700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:23:19 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=4
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f3844000c08
      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 = 0x7f38958efd58 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5638e1de8bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x5638e19110bd]
      2022-12-18 16:23:19 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017230203; transaction id 7589834756
      2022-12-18 16:23:19 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:23:19 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:23:19 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:23:19 0 [Note] Starting crash recovery...
      2022-12-18 16:23:19 0 [Note] Crash recovery finished.
      2022-12-18 16:23:19 0 [Note] Server socket created on IP: '::'.
      2022-12-18 16:23:19 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:23:19 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:23:19 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f3de3015730]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f3de2e7a8eb]
      linux/raise.c:51(__GI_raise)[0x7f3de2e65535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x5638e164fddb]
      /usr/sbin/mysqld(+0x4e690b)[0x5638e164c90b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x5638e1b81cd1]
      /usr/sbin/mysqld(+0xa1c112)[0x5638e1b82112]
      /usr/sbin/mysqld(+0xa0819b)[0x5638e1b6e19b]
      nptl/pthread_create.c:487(start_thread)[0x7f3de300afa3]
      x86_64/clone.S:97(clone)[0x7f3de2f3c06f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 4
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      2022-12-18 16:23:25 0 [Note] InnoDB: Using Linux native AIO
      2022-12-18 16:23:25 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-12-18 16:23:25 0 [Note] InnoDB: Uses event mutexes
      2022-12-18 16:23:25 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-12-18 16:23:25 0 [Note] InnoDB: Number of pools: 1
      2022-12-18 16:23:25 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-12-18 16:23:25 0 [Note] InnoDB: Initializing buffer pool, total size = 19G, instances = 8, chunk size = 128M
      2022-12-18 16:23:25 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-12-18 16:23:25 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2022-12-18 16:23:26 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3920017074621
      2022-12-18 16:23:26 0 [Note] InnoDB: Starting final batch to recover 23 pages from redo log.
      2022-12-18 16:23:27 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-12-18 16:23:27 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-12-18 16:23:27 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-12-18 16:23:27 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-12-18 16:23:27 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-12-18 16:23:27 0 [Note] InnoDB: Waiting for purge to start
      2022-12-18 16:23:27 0x7f3fae42f700  InnoDB: Assertion failure in file /build/mariadb-10.3-lMTCRk/mariadb-10.3-10.3.36/storage/innobase/trx/trx0purge.cc line 118
      InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
      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.
      221218 16:23:27 [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.36-MariaDB-0+deb10u2
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=10002
      thread_count=4
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22120993 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f3f68000c08
      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 = 0x7f3fae42ed58 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55b979341bde]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55b978e6a0bd]
      2022-12-18 16:23:27 0 [Note] InnoDB: 10.3.36 started; log sequence number 3920017230203; transaction id 7589834756
      2022-12-18 16:23:27 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-12-18 16:23:27 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-12-18 16:23:27 0 [Note] Recovering after a crash using tc.log
      2022-12-18 16:23:27 0 [Note] Starting crash recovery...
      2022-12-18 16:23:27 0 [Note] Crash recovery finished.
      2022-12-18 16:23:27 0 [Note] Server socket created on IP: '::'.
      2022-12-18 16:23:27 0 [Note] Reading of all Master_info entries succeeded
      2022-12-18 16:23:27 0 [Note] Added new Master_info '' to hash table
      2022-12-18 16:23:27 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.36-MariaDB-0+deb10u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f44fc60d730]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f44fc4728eb]
      linux/raise.c:51(__GI_raise)[0x7f44fc45d535]
      /usr/sbin/mysqld(+0x4e9ddb)[0x55b978ba8ddb]
      /usr/sbin/mysqld(+0x4e690b)[0x55b978ba590b]
      /usr/sbin/mysqld(+0xa1bcd1)[0x55b9790dacd1]
      /usr/sbin/mysqld(+0xa1c112)[0x55b9790db112]
      /usr/sbin/mysqld(+0xa0819b)[0x55b9790c719b]
      nptl/pthread_create.c:487(start_thread)[0x7f44fc602fa3]
      x86_64/clone.S:97(clone)[0x7f44fc53406f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 2
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             96301                96301                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       96301                96301                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
       
      Kernel version: Linux version 4.19.0-21-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.249-2 (2022-06-30)
       
      
      

      Thank you

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              Dubois Jean
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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