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

Crash when MariaDB is replica of MySQL 8.0

    XMLWordPrintable

    Details

      Description

      Configure MySQL to use non-default settings:

      character_set_server = 'utf8mb4'
      collation_server='utf8mb4_unicode_520_ci'
      character_set_client_handshake=0
      binlog_checksum=0
      

      Configure MariaDB with skip-slave-start

      Connect to MySQL:

      MariaDB [(none)]> system truncate -s0 /var/lib/mysql/mg.err
      MariaDB [(none)]> set global replicate_wild_do_table='test.%';
      Query OK, 0 rows affected (0.001 sec)
       
      MariaDB [(none)]> change master to master_host='mysql8', master_user='replica', master_password='SDfkhskj53!';
      Query OK, 0 rows affected (0.008 sec)
       
      MariaDB [(none)]> start slave io_thread;
      Query OK, 0 rows affected (0.001 sec)
       
      MariaDB [(none)]> stop slave;
      ERROR 2013 (HY000): Lost connection to server during query
      

      2022-09-14  5:09:20 4 [Note] Slave I/O thread: Start asynchronous replication to master 'replica@mysql8:3306' in log '' at position 4
      2022-09-14  5:09:20 4 [ERROR] Slave I/O: error connecting to master 'replica@mysql8:3306' - retry-time: 60  maximum-retries: 100000  message: Access denied for user 'replica'@'104.130.132.75' (using password: YES), Internal MariaDB error code: 1045
      2022-09-14  5:09:27 4 [Note] Slave I/O thread killed while connecting to master
      2022-09-14  5:09:27 4 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4, master mysql8:3306
      220914  5:09:27 [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.7.5-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=1
      max_threads=153
      thread_count=2
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467995 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fe11c0009b8
      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 = 0x7fe15869aa70 thread_stack 0x49000
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x5574175f047e]
      /usr/sbin/mariadbd(handle_fatal_signal+0x307)[0x55741705edf7]
      sigaction.c:0(__restore_rt)[0x7fe17235b630]
      /usr/sbin/mariadbd(+0x9ea8f7)[0x5574170318f7]
      /usr/sbin/mariadbd(mysql_close+0x22)[0x557417034eb2]
      /usr/sbin/mariadbd(handle_slave_io+0x887)[0x557416d7e857]
      /usr/sbin/mariadbd(+0xc3b8ac)[0x5574172828ac]
      nptl/pthread_create.c:307(start_thread)[0x7fe172353ea5]
      x86_64/clone.S:113(__clone)[0x7fe17186eb0d]
       
      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
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Elkin Andrei Elkin
              Reporter:
              mg MG
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.