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

galera_new_cluster fails with mariadb 10.6.25

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.25
    • None
    • Galera
    • Foobar Linux 9 x86_64

    Description

      When testing our new build for mariadb 10.6.25 I found out that galera_new_cluster failed. Tested again with combination of 10.6.25 and galera 26.4.24 and still failed to bootstrap galera cluster. With 10.6.24/26.4.24 combination bootstrap works. Also updating single node to latest versions works.

      This is the hint, logged with 10.6.25 when failing bootsrap:

      Feb 07 11:30:37 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:37 0 [Note] WSREP: gcomm: connecting to group 'foo-db', peer '172.23.50.40:,172.23.50.41:,172.23.50.42:'
      Feb 07 11:30:37 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:37 0 [Note] WSREP: (a9117a8a-b233, 'tcp://0.0.0.0:4567') Found matching local endpoint for a connection, blacklisting address tcp://172.23.50.40:4567
      Feb 07 11:30:37 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:37 0 [Note] WSREP: Failed to establish connection: Connection refused
      Feb 07 11:30:37 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:37 0 [Note] WSREP: Failed to establish connection: Connection refused
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:38 0 [Note] WSREP: EVS version upgrade 0 -> 1
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:38 0 [Note] WSREP: PC protocol upgrade 0 -> 1
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:38 0 [Note] WSREP: No nodes coming from primary view, primary view is not possible
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:38 0 [Note] WSREP: view(view_id(NON_PRIM,a9117a8a-b233,1) memb {
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]:         a9117a8a-b233,0
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: } joined {
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: } left {
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: } partitioned {
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: })
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:38 0 [Note] WSREP: Failed to establish connection: Connection refused
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:38 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.50319S), skipping check
      Feb 07 11:30:38 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:38 0 [Note] WSREP: Failed to establish connection: Connection refused
      Feb 07 11:30:39 foo-db-01.foobar.fi mariadbd[14668]: 2026-02-07 11:30:39 0 [Note] WSREP: Failed to establish connection: Connection refused
      

      That log line about blacklisting own ip is missing in 10.6.24 which manages to connecto to 172.23.50.40.4567 (which is server itself in this case.)

      By blacklisting self bootstrap is not possible.

      Attachments

        Activity

          People

            seppo Seppo Jaakola
            bleve Tuomo Soini
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.