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

Galera SST crashes on missing credentials for mysqldump

    Details

    • Type: Bug
    • Status: Stalled
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.0.17-galera
    • Fix Version/s: None
    • Component/s: Galera SST
    • Labels:
      None
    • Environment:
      Ubuntu 14.04 LTS trusty amd64 docker container

      Description

      If the donor cannot authenticate to the joiner, this happens:

      150410  8:23:30 [Note] Reading of all Master_info entries succeded
      150410  8:23:30 [Note] Added new Master_info '' to hash table
      150410  8:23:30 [Note] mysqld: ready for connections.
      Version: '10.0.17-MariaDB-1~trusty-wsrep-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3307  mariadb.org binary distribution, wsrep_25.10.r4144
      150410  8:23:32 [Note] WSREP: waiting for client connections to close: 2
      150410  8:23:32 [Note] WSREP: Prepared SST request: mysqldump|192.168.255.99:4568
      150410  8:23:32 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      150410  8:23:32 [Note] WSREP: REPL Protocols: 7 (3, 2)
      150410  8:23:32 [Note] WSREP: Service thread queue flushed.
      150410  8:23:32 [Note] WSREP: Assign initial position for certification: 16953, protocol version: 3
      150410  8:23:32 [Note] WSREP: Service thread queue flushed.
      150410  8:23:32 [Warning] WSREP: Failed to prepare for incremental state transfer: Local state UUID (00000000-0000-0000-0000-000000000000) does not match group state UUID (2645a3fe-d661-11e4-a57d-4aaac1dfb09f): 1 (Operation not permitted)
      	 at galera/src/replicator_str.cpp:prepare_for_IST():456. IST will be unavailable.
      150410  8:23:32 [Note] WSREP: Member 2.0 (node99) requested state transfer from '*any*'. Selected 0.0 (node1)(SYNCED) as donor.
      150410  8:23:32 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 16953)
      150410  8:23:32 [Note] WSREP: Requesting state transfer: success, donor: 0
      150410  8:23:33 [Note] WSREP: (de595892, 'tcp://0.0.0.0:4567') turning message relay requesting off
      150410  8:23:35 [Warning] WSREP: 0.0 (node1): State transfer to 2.0 (node99) failed: -1 (Operation not permitted)
      150410  8:23:35 [ERROR] WSREP: gcs/src/gcs_group.cpp:int gcs_group_handle_join_msg(gcs_group_t*, const gcs_recv_msg_t*)():731: Will never receive state. Need to abort.
      150410  8:23:35 [Note] WSREP: gcomm: terminating thread
      150410  8:23:35 [Note] WSREP: gcomm: joining thread
      150410  8:23:35 [Note] WSREP: gcomm: closing backend
      150410  8:23:35 [Note] WSREP: view(view_id(NON_PRIM,2a70014c,9) memb {
      	de595892,0
      } joined {
      } left {
      } partitioned {
      	2a70014c,0
      	43e868bb,0
      })
      150410  8:23:35 [Note] WSREP: view((empty))
      150410  8:23:35 [Note] WSREP: gcomm: closed
      150410  8:23:35 [Note] WSREP: mysqld: Terminated.
      150410  8:23:35 [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 http://kb.askmonty.org/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.0.17-MariaDB-1~trusty-wsrep-log
      key_buffer_size=134217728
      read_buffer_size=2097152
      max_used_connections=0
      max_threads=102
      thread_count=2
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759892 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      
      Thread pointer: 0x0x0
      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 0x48000
      mysqld(my_print_stacktrace+0x2e)[0x7f37f1f2538e]
      mysqld(handle_fatal_signal+0x457)[0x7f37f1a5cfc7]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f37f0208340]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x297)[0x7f37ef863227]
      /usr/lib/galera/libgalera_smm.so(+0x81547)[0x7f37c1423547]
      /usr/lib/galera/libgalera_smm.so(_Z13gcs_core_recvP8gcs_coreP12gcs_act_rcvdx+0x76b)[0x7f37c152fa9b]
      /usr/lib/galera/libgalera_smm.so(+0x191646)[0x7f37c1533646]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f37f0200182]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f37ef92347d]
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            nirbhay_c Nirbhay Choubey added a comment -

            Though, the joiner node is destined to shut in this case, but it should do so without crashing (signal 11). I tried with no/incorrect credentials and the joiner node aborted in my case. Can you share the donor logs as well as wsrep configuration options ?

            Show
            nirbhay_c Nirbhay Choubey added a comment - Though, the joiner node is destined to shut in this case, but it should do so without crashing (signal 11). I tried with no/incorrect credentials and the joiner node aborted in my case. Can you share the donor logs as well as wsrep configuration options ?

              People

              • Assignee:
                nirbhay_c Nirbhay Choubey
                Reporter:
                kurthuwig Kurt Huwig
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: