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

galera_3nodes.galera_vote_rejoin_mysqldump mysql_shutdown failed at line 85:

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Appears on 10.11.8-MariaDB-log source revision dfb8064512ac6d6f1d4bb18022c36861ba8fa2f6 which includes MDEV-24481 fix

      https://ci.mariadb.org/44934/logs/amd64-debian-10-last-N-failed/nm/mysqld.1.err.4

      galera_3nodes.galera_vote_rejoin_mysqldump 'innodb' w4 [ fail ]
      		 
              Test ended at 2024-03-28 05:11:47
      		 
      CURRENT_TEST: galera_3nodes.galera_vote_rejoin_mysqldump
      		 
      mysqltest: In included file "./include/shutdown_mysqld.inc": 
      included from ./include/restart_mysqld.inc at line 10:
      		 
      included from /home/buildbot/amd64-debian-10-last-N-failed/build/mysql-test/suite/galera_3nodes/t/galera_vote_rejoin_mysqldump.test at line 85:
      		 
      At line 50: mysql_shutdown failed

      Attachments

        Issue Links

          is part of

          Task - A task that needs to be done. MDEV-33073 always green buildbot

          • Critical - Crashes, loss of data, severe memory leak.
          • In Progress
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24481 galera_3nodes.galera_vote_rejoin_mysqldump MTR failed: mysql_shutdown failed

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              sysprg Julius Goryavsky
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.