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

Mysqld got signal 11 after search replace

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.3.23
    • None
    • None
    • None
    • Linux Debian 10 on a server with 8G RAM

    Description

      Hello,

      after performing a search replace with wp-cli on a large database (lot of tables), mysql got signal 11 :

      200928 16:33:43 [ERROR] mysqld got signal 11 ;
      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.23-MariaDB-0+deb10u1-log
      key_buffer_size=268435456
      read_buffer_size=1048576
      max_used_connections=46
      max_threads=502
      thread_count=52
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1301524 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f595c007aa8
      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 = 0x7f5974988dd8 thread_stack 0x49000
      *** buffer overflow detected ***: /usr/sbin/mysqld terminated
      Fatal signal 6 while backtracing
      2020-09-28 16:33:48 0 [Note] InnoDB: Using Linux native AIO
      2020-09-28 16:33:48 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2020-09-28 16:33:48 0 [Note] InnoDB: Uses event mutexes
      2020-09-28 16:33:48 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-09-28 16:33:48 0 [Note] InnoDB: Number of pools: 1
      2020-09-28 16:33:48 0 [Note] InnoDB: Using generic crc32 instructions
      2020-09-28 16:33:48 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
      2020-09-28 16:33:48 0 [Note] InnoDB: Completed initialization of buffer pool
      2020-09-28 16:33:48 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2020-09-28 16:33:48 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=269557888141781
      2020-09-28 16:33:48 0 [Note] InnoDB: Starting final batch to recover 8 pages from redo log.
      2020-09-28 16:33:48 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2020-09-28 16:33:48 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2020-09-28 16:33:48 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2020-09-28 16:33:48 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2020-09-28 16:33:48 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2020-09-28 16:33:48 0 [Note] InnoDB: Waiting for purge to start
      2020-09-28 16:33:48 0 [Note] InnoDB: 10.3.23 started; log sequence number 269557888147361; transaction id 3317646164
      2020-09-28 16:33:48 0 [Note] Plugin 'FEEDBACK' is disabled.
      2020-09-28 16:33:48 0 [Note] Recovering after a crash using tc.log
      2020-09-28 16:33:48 0 [Note] Starting crash recovery...
      2020-09-28 16:33:48 0 [Note] Crash recovery finished.
      2020-09-28 16:33:48 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2020-09-28 16:33:48 0 [Note] Server socket created on IP: '::'.
      2020-09-28 16:33:48 0 [Note] Reading of all Master_info entries succeeded
      2020-09-28 16:33:48 0 [Note] Added new Master_info '' to hash table
      2020-09-28 16:33:48 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.23-MariaDB-0+deb10u1-log'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 10
      2020-09-28 16:33:48 0 [Note] InnoDB: Buffer pool(s) load completed at 200928 16:33:48
      

      Thanks for answering.

      Best regards,
      Olivier.

      Attachments

        Activity

          People

            Unassigned Unassigned
            webtech Olivier
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.