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

Regelmäßiger Crash nach ein paar Tagen

Details

    Description

      Auszug aus /var/log/mysql/error.log:

      Server version: 10.11.8-MariaDB-0ubuntu0.24.04.1-log source revision: 3a069644682e336e445039e48baae9693f9a08ee
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=3
      max_threads=12
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 27430 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
      /usr/sbin/mariadbd(my_print_stacktrace+0x34)[0xac8bd07210b8]
      /usr/sbin/mariadbd(handle_fatal_signal+0x520)[0xac8bd025c590]
      addr2line: ‚linux-vdso.so.1‛: Keine solche Datei
      linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xff60f59d08f8]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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        unlimited            unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             31212                31212                processes 
      Max open files            32768                32768                files     
      Max locked memory         524288               524288               bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       31212                31212                signals   
      Max msgqueue size         819200               819200               bytes     
      Max nice priority         0                    0                    
      Max realtime priority     0                    0                    
      Max realtime timeout      unlimited            unlimited            us        
      Core pattern: |/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E
       
      Kernel version: Linux version 6.8.0-51-generic (buildd@bos03-arm64-031) (aarch64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec  5 13:32:09 UTC 2024
       
      2025-01-06 13:39:44 0 [Note] Starting MariaDB 10.11.8-MariaDB-0ubuntu0.24.04.1-log source revision 3a069644682e336e445039e48baae9693f9a08ee as process 1958
      2025-01-06 13:39:44 0 [Note] InnoDB: Compressed tables use zlib 1.3
      2025-01-06 13:39:44 0 [Note] InnoDB: Number of transaction pools: 1
      2025-01-06 13:39:44 0 [Note] InnoDB: Using ARMv8 crc32 + pmull instructions
      2025-01-06 13:39:44 0 [Note] InnoDB: Using liburing
      2025-01-06 13:39:44 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
      2025-01-06 13:39:44 0 [Note] InnoDB: Initialized memory pressure event listener
      2025-01-06 13:39:44 0 [Note] InnoDB: Completed initialization of buffer pool
      2025-01-06 13:39:44 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
      2025-01-06 13:39:44 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3873468873
      2025-01-06 13:39:44 0 [Note] InnoDB: End of log at LSN=3873473740
      2025-01-06 13:39:44 0 [Note] InnoDB: To recover: 15 pages
      2025-01-06 13:39:44 0 [Note] InnoDB: Last binlog file '/var/log/mysql/mysql-bin.000019', position 2260
      2025-01-06 13:39:44 0 [Note] InnoDB: 128 rollback segments are active.
      2025-01-06 13:39:44 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
      2025-01-06 13:39:44 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
      2025-01-06 13:39:44 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
      2025-01-06 13:39:44 0 [Note] InnoDB: log sequence number 3873473740; transaction id 14532
      2025-01-06 13:39:44 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2025-01-06 13:39:44 0 [Note] Plugin 'FEEDBACK' is disabled.
      2025-01-06 13:39:44 0 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
      2025-01-06 13:39:44 0 [Note] Starting table crash recovery...
      2025-01-06 13:39:44 0 [Note] Crash table recovery finished.
      2025-01-06 13:39:44 0 [Note] Server socket created on IP: '0.0.0.0'.
      2025-01-06 13:39:44 0 [Note] Server socket created on IP: '::'.
      2025-01-06 13:39:44 0 [Note] /usr/sbin/mariadbd: ready for connections.
      Version: '10.11.8-MariaDB-0ubuntu0.24.04.1-log'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Ubuntu 24.04
      2025-01-06 13:39:44 0 [Note] InnoDB: Buffer pool(s) load completed at 250106 13:39:44
      200303 14:35:14 [ERROR] mysqld got signal 11 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      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.11.8-MariaDB-0ubuntu0.24.04.1-log source revision: 3a069644682e336e445039e48baae9693f9a08ee
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=3
      max_threads=12
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 27430 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
      /usr/sbin/mariadbd(my_print_stacktrace+0x34)[0xaba9c1ae10b8]
      /usr/sbin/mariadbd(handle_fatal_signal+0x520)[0xaba9c161c590]
      addr2line: ‚linux-vdso.so.1‛: Keine solche Datei
      linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xfc80e727a8f8]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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        unlimited            unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             31212                31212                processes 
      Max open files            32768                32768                files     
      Max locked memory         524288               524288               bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       31212                31212                signals   
      Max msgqueue size         819200               819200               bytes     
      Max nice priority         0                    0                    
      Max realtime priority     0                    0                    
      Max realtime timeout      unlimited            unlimited            us        
      Core pattern: |/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E
       
      Kernel version: Linux version 6.8.0-51-generic (buildd@bos03-arm64-031) (aarch64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec  5 13:32:09 UTC 2024
       
      2025-01-10 14:50:26 0 [Note] Starting MariaDB 10.11.8-MariaDB-0ubuntu0.24.04.1-log source revision 3a069644682e336e445039e48baae9693f9a08ee as process 1969
      2025-01-10 14:50:26 0 [Note] InnoDB: Compressed tables use zlib 1.3
      2025-01-10 14:50:26 0 [Note] InnoDB: Number of transaction pools: 1
      2025-01-10 14:50:26 0 [Note] InnoDB: Using ARMv8 crc32 + pmull instructions
      2025-01-10 14:50:26 0 [Note] InnoDB: Using liburing
      2025-01-10 14:50:26 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
      2025-01-10 14:50:26 0 [Note] InnoDB: Initialized memory pressure event listener
      2025-01-10 14:50:26 0 [Note] InnoDB: Completed initialization of buffer pool
      2025-01-10 14:50:26 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
      2025-01-10 14:50:26 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3873468889
      2025-01-10 14:50:26 0 [Note] InnoDB: End of log at LSN=3873576917
      2025-01-10 14:50:26 0 [Note] InnoDB: To recover: 147 pages
      2025-01-10 14:50:26 0 [Note] InnoDB: Last binlog file '/var/log/mysql/mysql-bin.000020', position 21148
      2025-01-10 14:50:26 0 [Note] InnoDB: 128 rollback segments are active.
      2025-01-10 14:50:26 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
      2025-01-10 14:50:26 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
      2025-01-10 14:50:26 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
      2025-01-10 14:50:26 0 [Note] InnoDB: log sequence number 3873576917; transaction id 14652
      2025-01-10 14:50:26 0 [Note] Plugin 'FEEDBACK' is disabled.
      2025-01-10 14:50:26 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2025-01-10 14:50:26 0 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
      2025-01-10 14:50:26 0 [Note] Starting table crash recovery...
      2025-01-10 14:50:26 0 [Note] Crash table recovery finished.
      2025-01-10 14:50:26 0 [Note] Server socket created on IP: '0.0.0.0'.
      2025-01-10 14:50:26 0 [Note] Server socket created on IP: '::'.
      2025-01-10 14:50:26 0 [Note] /usr/sbin/mariadbd: ready for connections.
      Version: '10.11.8-MariaDB-0ubuntu0.24.04.1-log'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Ubuntu 24.04
      2025-01-10 14:50:26 0 [Note] InnoDB: Buffer pool(s) load completed at 250110 14:50:26

      Attachments

        Activity

          serg Sergei Golubchik added a comment - - edited
          • This is Ubuntu-built packages, not official MariaDB .deb packages
          • The stack trace is empty.

          Is there a core dump? Can you try to get one?
          Can you try our build? See repository configuration for 10.11 on Ubunto 24.04

          serg Sergei Golubchik added a comment - - edited This is Ubuntu-built packages, not official MariaDB .deb packages The stack trace is empty. Is there a core dump? Can you try to get one? Can you try our build? See repository configuration for 10.11 on Ubunto 24.04
          Peter Bartelt Peter Bartelt added a comment -

          Thank you for your reply. I will try one or the other, but I don't have time for this in the next 2 months. Maybe I should report this to UBUNTU. So, thanks for your comment about it being an Ubuntu package. It's been a while since I've had anything to do with Linux.

          Peter Bartelt Peter Bartelt added a comment - Thank you for your reply. I will try one or the other, but I don't have time for this in the next 2 months. Maybe I should report this to UBUNTU. So, thanks for your comment about it being an Ubuntu package. It's been a while since I've had anything to do with Linux.

          People

            Unassigned Unassigned
            Peter Bartelt Peter Bartelt
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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