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

rpl.rpl_variables failed in buildbot with server crash

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.3
    • N/A
    • Replication, Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/mac-1012-bintar/builds/5687

      10.3 70b226d96698502281cd93581d68f013

      rpl.rpl_variables 'row'                  [ fail ]
              Test ended at 2019-07-22 14:03:11
       
      CURRENT_TEST: rpl.rpl_variables
       
       
      Server [mysqld.1 - pid: 13381, winpid: 13381, exit: 256] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      2019-07-22 14:03:11 9 [Note] Deleted Master_info file '/Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/var/mysqld.1/data/master.info'.
      2019-07-22 14:03:11 9 [Note] Deleted Master_info file '/Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/var/mysqld.1/data/relay-log.info'.
      190722 14:03:11 [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.17-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=4
      max_threads=153
      thread_count=6
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63197 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f898b84b608
      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 = 0x70000b462e60 thread_stack 0x49000
      Fatal signal 4 while backtracing
      ----------SERVER LOG END-------------
      mysqltest failed but provided no output
      The result from queries just before the failure was:
      < snip >
      include/master-slave.inc
      

      Attachments

        Activity

          People

            angelique.sklavounos Angelique Sklavounos (Inactive)
            elenst Elena Stepanova
            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.