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

mariadb crashes and cannot resync - [ERROR] mysqld got signal 11 ;

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.5.10
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:
      debian linux 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux

      Description

      Once every ~20 days, an active node in a galera cluster crashes, always at ~ the same time (0:06) although no cron job run at that time. Server has 32Gg RAM and has enough resources.

      Log shows:
      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.5.10-MariaDB-1:10.5.10+maria~buster-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=26
      max_threads=122
      thread_count=32
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 399625 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f10b42c31d8
      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 = 0x7f153cfc5d58 thread_stack 0x30000
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x5559a6bd34ee]
      /usr/sbin/mariadbd(handle_fatal_signal+0x485)[0x5559a665cca5]
      2021-06-18 0:08:29 7792507 [Warning] Aborted connection 7792507 to db: 'sentry' user: 'sentry' host: 'sentry.lan.zetescards.be' (Lock wait timeout exceeded; try restarting transaction)

      then all transactions fall in timeout until
      2021-06-18 7:45:04 0 [Warning] Aborted connection 0 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Too many connections)
      The 2 other nodes in the galera continue to work.
      After reboot, running glera_recover, setting number in grastate.dat, mariadb always tell wsrep has not been prepared for application use.
      Node cannot resync:
      2021-06-18 10:27:11 3 [Note] WSREP: SST succeeded for position 8ef7bece-c55f-11e8-8e85-1a29ec51b021:839632536
      2021-06-18 10:27:11 0 [Note] WSREP: Joiner monitor thread ended with total time 1 sec
      2021-06-18 10:27:11 2 [Note] WSREP: Installed new state from SST: 8ef7bece-c55f-11e8-8e85-1a29ec51b021:839632536
      2021-06-18 10:27:11 2 [Note] WSREP: Receiving IST: 432 writesets, seqnos 839632537-839632968
      2021-06-18 10:27:11 0 [Note] WSREP: ####### IST applying starts with 839632537
      2021-06-18 10:27:11 0 [Note] WSREP: ####### IST current seqno initialized to 839632537
      2021-06-18 10:27:11 0 [Note] WSREP: Receiving IST... 0.0% ( 0/432 events) complete.
      2021-06-18 10:27:11 0 [Note] WSREP: Service thread queue flushed.
      2021-06-18 10:27:11 0 [Note] WSREP: ####### Assign initial position for certification: 00000000-0000-0000-0000-000000000000:839632536, protocol version: 5
      210618 10:27: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.5.10-MariaDB-1:10.5.10+maria~buster-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=122
      thread_count=5
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 399625 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f23c4000c18
      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 = 0x7f2848150d98 thread_stack 0x30000
      ...
      2021-06-18 10:27:12 0 [Note] WSREP: (f90f0b5e-af4b, 'tcp://0.0.0.0:4567') turning message relay requesting off
      2021-06-18 10:28:19 0 [Note] InnoDB: Buffer pool(s) load completed at 210618 10:28:19
      2021-06-18 10:31:26 0 [Warning] InnoDB: A long semaphore wait:
      --Thread 139810985170688 has waited at lock0lock.cc line 3756 for 255.00 seconds the semaphore:
      Mutex at 0x55dc19ef7f80, Mutex LOCK_SYS created /home/buildbot/buildbot/build/mariadb-10.5.10/storage/innobase/lock/lock0lock.cc:461, lock var 2

      => the only solution found till now is to scratch data folder and make a full sst from another running node.
      Any hint?

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            albourg Alain Bourgeois
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration