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

Galera cluster handshakes failed when applying new SSL certificate

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5.10, 10.4.26
    • None
    • Galera
    • None
    • Docker image mariadb:10.4.26, mariadb:10.5.10

    Description

      After putting the new SSL certificate in the configured path, I tried to reload the SSL certificate of the MariaDB process using FLUSH SSL; with root user.

      According to MDEV-25470, the command also triggers `socket.ssl_reload`. But I still receive the errors below when restarting the mariadb process:

      WSREP: Handshake failed: tlsv1 alert unknown ca
      WSREP: Handshake failed: tlsv1 alert unknown ca
      WSREP: Handshake failed: tlsv1 alert unknown ca
      WSREP: Handshake failed: tlsv1 alert unknown ca
      WSREP: /home/buildbot/buildbot/build/gcs/src/gcs_core.cpp:gcs_core_open():221: Failed to open backend connection: -110 (Connection timed out)
      WSREP: gcs connect failed: Connection timed out
      

      I also tried to set `socket.ssl_reload` dynamically with `SET GLOBAL wsrep_provider_options='socket.ssl_reload=1';`. But I cannot find that option after setting with `SHOW GLOBAL VARIABLES LIKE 'wsrep_provider_options';`. And the errors still happened when I restarted the mariadb process.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ttnhan1806 Trung-Nhan Truong
            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.