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

[ERROR] mysqld got signal 11

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Incomplete
    • Affects Version/s: 10.6.4
    • Fix Version/s: N/A
    • Component/s: OTHER
    • Labels:
    • Environment:
      OpenBSD 7.0 GENERIC.MP#1 amd64

      Description

      Hi,

      I'm running mariadb-client-10.6.4v1 and mariadb-server-10.6.4p2v1 installed from the packages on OpenBSD 7.0 which I just upgraded.
      I'm also trying to upgrade multiple wikis to MediaWiki 1.37.0. All databases combined are around 800 MB. When updating the smaller wikis I have no issues. However, when running the update script on the biggest wiki, the following error shows up:

      Beginning migration of log_search
      ... target_author_id, ls_value=1 ls_log_id=94785
      Wikimedia\Rdbms\DBQueryDisconnectedError from line 1807 of /path/to/project/de/w/includes/libs/rdbms/database/Database.php: A connection error occurred during a query.
      Query: SELECT  ls_value,ls_log_id,actor_id  FROM `log_search` LEFT JOIN `actor` ON ((actor_user = CAST( ls_value AS SIGNED )))   WHERE ls_field = 'target_author_id' AND (ls_value > '1' OR ls_value = '1' AND (ls_log_id > '94785'))  ORDER BY ls_value,ls_log_id LIMIT 100
      Function: MigrateActors::migrateLogSearch
      Error: 2006 MySQL server has gone away (127.0.0.1)
      

      I also tried this:

      MariaDB [dewiki]> select * from log_search where ls_log_id = 94785;
      ERROR 2006 (HY000): Server has gone away
      No connection. Trying to reconnect...
      Connection id:    2216
      Current database: dewiki
       
      +---------------------+----------+-----------+
      | ls_field            | ls_value | ls_log_id |
      +---------------------+----------+-----------+
      | log_id              | 93322    |     94785 |
      | target_author_actor | 1        |     94785 |
      | target_author_id    | 1        |     94785 |
      +---------------------+----------+-----------+
      3 rows in set (0.002 sec)
      

      My log file looks like this:

      211120  9:34:08 [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.6.4-MariaDB-log
      key_buffer_size=104857600
      read_buffer_size=2621440
      max_used_connections=30
      max_threads=153
      thread_count=31
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1281306 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x5a866a4c018
      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 = 0x5a8a20bbed8 thread_stack 0x49000
      ??:0(my_print_stacktrace)[0x5a65fad84bb]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x5a88bb75030): SELECT /* MigrateActors::migrateLogSearch user@project... */  ls_value,ls_log_id,actor_id  FROM `log_search` LEFT JOIN `actor` ON ((actor_user = CAST( ls_value AS SIGNED )))   WHERE ls_field = 'target_author_id' AND (ls_value > '1' OR ls_value = '1' AND (ls_log_id > '94785'))  ORDER BY ls_v
      alue,ls_log_id LIMIT 100
       
      Connection ID (thread ID): 204864
      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,parti
      al_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,orderb
      y_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.
      2021-11-20  9:34:08 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2021-11-20  9:34:08 0 [Note] InnoDB: Number of pools: 1
      2021-11-20  9:34:08 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2021-11-20  9:34:08 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
      2021-11-20  9:34:08 0 [Note] InnoDB: Completed initialization of buffer pool
      2021-11-20  9:34:08 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1256130111787,1256130114039
      2021-11-20  9:34:08 0 [Note] InnoDB: Transaction 4832069210 was in the XA prepared state.
      2021-11-20  9:34:08 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
      2021-11-20  9:34:08 0 [Note] InnoDB: Trx id counter is 4832069211
      2021-11-20  9:34:08 0 [Note] InnoDB: Starting final batch to recover 76 pages from redo log.
      2021-11-20  9:34:09 0 [Note] InnoDB: Last binlog file './mysql-bin.000317', position 20068278
      2021-11-20  9:34:09 0 [Note] InnoDB: 128 rollback segments are active.
      2021-11-20  9:34:09 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
      2021-11-20  9:34:09 0 [Note] InnoDB: Rollback of non-prepared transactions completed
      2021-11-20  9:34:09 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
      2021-11-20  9:34:09 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2021-11-20  9:34:09 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2021-11-20  9:34:09 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2021-11-20  9:34:09 0 [Note] InnoDB: 10.6.4 started; log sequence number 1256130420821; transaction id 4832069212
      2021-11-20  9:34:09 0 [Note] InnoDB: Loading buffer pool(s) from /var/mysql/ib_buffer_pool
      2021-11-20  9:34:09 0 [Note] Plugin 'FEEDBACK' is disabled.
      2021-11-20  9:34:09 0 [Note] Recovering after a crash using mysql-bin
      2021-11-20  9:34:09 0 [Note] Starting table crash recovery...
      2021-11-20  9:34:09 0 [Note] InnoDB: Starting recovery for XA transactions...
      2021-11-20  9:34:09 0 [Note] InnoDB: Transaction 4832069210 in prepared state after recovery
      2021-11-20  9:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows
      2021-11-20  9:34:09 0 [Note] InnoDB: 1 transactions in prepared state after recovery
      2021-11-20  9:34:09 0 [Note] Found 1 prepared transaction(s) in InnoDB
      2021-11-20  9:34:09 0 [Note] Crash table recovery finished.
      2021-11-20  9:34:09 0 [Note] InnoDB: Buffer pool(s) load completed at 211120  9:34:09
      2021-11-20  9:34:09 0 [Note] Server socket created on IP: '127.0.0.1'.
      2021-11-20  9:34:09 0 [Note] /usr/local/libexec/mariadbd: ready for connections.
      Version: '10.6.4-MariaDB-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  OpenBSD port: mariadb-server-10.6.4p2v1
      

      I already increased key_buffer_size, read_buffer_size and sort_buffer_size but the error still occurs.

      The same error also appeared when I tried to make a backup via mysqldump but TRUNCATE TABLE objectcache fixed this.

      I already performed mariadb-upgrade. I also uninstalled and reinstalled mariadb-client-10.6.4v1 and mariadb-server-10.6.4p2v1 but the error still occurs. I don't really know what to do anymore so any help is more than appreciated!

      Thanks and cheers,

      Till

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            Till Kraemer Till Kraemer
            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.