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

STOP SLAVE or slave errors (ex 1062, 1032) constantly crash MariaDB server



    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.6.1, 10.5.15
    • N/A
    • Compiling, Replication
    • None
    • Ubuntu 21.10 / Ubuntu 22.04


      I've set-up replication between a galera cluster connecting to one node, and each time I stop the slave the slave server crashes immediately.

      I upgraded to 22.04 and replication stopped working but the crash still occured. I reverted back to 21.10, still getting the crash but replication is still not working so trying to play with settings slave position, etc is just a pain while the server is constantly crashing on me.

      I've setup replication back in january and the problem was already there, running 10.4 I believe at the time.

      Any help would be greatly appreciated.

      2022-06-25 9:55:09 35 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.012160', position 19131057; GTID position 300-3-522464027,100-1-102978519
      2022-06-25 9:55:09 35 [Note] master was xxxxx:3306
      220625 9:55:09 [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.5.15-MariaDB-0ubuntu0.21.10.1-log
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 11273904 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
      2022-06-25 9:55:09 0 [Note] InnoDB: FTS optimize thread exiting.
      2022-06-25 9:55:09 0 [Note] InnoDB: Buffer pool(s) load aborted due to user instigated abort at 220625 9:55:09
      2022-06-25 9:55:09 0 [Note] InnoDB: Dumping of buffer pool not started as load was incomplete
      2022-06-25 9:55:09 0 [Note] InnoDB: Starting shutdown...
      2022-06-25 9:55:09 0 [Note] InnoDB: Dumping of buffer pool not started as load was incomplete
      ??:0(wsrep_write_dummy_event_low(THD*, char const*))[0x55f97fe6754a]
      ??:0(wsrep::wsrep_provider_v26::status() const)[0x55f98076065f]


        Issue Links



              danblack Daniel Black
              ccounotte COUNOTTE CEDRIC
              0 Vote for this issue
              2 Start watching this issue



                Git Integration

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