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

after update not starting

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.1.27
    • 10.1.28
    • Galera
    • None
    • Ubuntu 16.04.3 LTS

    Description

      Description: Ubuntu 16.04.3 LTS
      Kernel: linux-image-4.11.0-14-generic
      Repo: mariadb.org/repo/10.1/ubuntu xenial main

      mysql-error-log

      ...
      		 
      2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
      		 
      Version: '10.1.27-MariaDB-1~xenial'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
      		 
      170926 10:20:44 [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.1.27-MariaDB-1~xenial
      		 
      key_buffer_size=1073741824
      		 
      read_buffer_size=2097152
      		 
      max_used_connections=0
      		 
      max_threads=4002
      		 
      thread_count=65
      		 
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K  bytes of memory
      		 
      Hope that's ok; if not, decrease some variables in the equation.
      		 
       
      		 
      Thread pointer: 0x0
      		 
      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 0x40000
      		 
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
      		 
      /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
      		 
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
      		 
      /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
      		 
      /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
      		 
      /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
      		 
      /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
      		 
      /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
      		 
      /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
      		 
      /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
      		 
      /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
      		 
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
      		 
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
      		 
      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.

      syslog

      kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]

      other Kernel ( linux-image-4.10.0-35-generic ) the same

      kernel: [   34.915202] mysqld[3700]: segfault at 950 ip 00005650bbc7fea8 sp 00007f4191bf9830 error 4 in mysqld[5650bb746000+f0b000]

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13787 Crash in persistent stats wsrep_on (thd=0x0)

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13908 10.1.27 Segfaulting

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            tdworak Thorsten Dworak created issue -
            tdworak Thorsten Dworak made changes -
            Field Original Value New Value
            Description
            {code:java}
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            		Description: Ubuntu 16.04.3 LTS,


            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            tdworak Thorsten Dworak made changes -
            Description Description: Ubuntu 16.04.3 LTS,


            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            		Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic


            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            tdworak Thorsten Dworak made changes -
            Description Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic


            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            		Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            serg Sergei Golubchik made changes -
            Affects Version/s 10.1.27 [ 22609 ]
            serg Sergei Golubchik made changes -
            Environment Ubuntu 16.04.3 LTS
            tdworak Thorsten Dworak made changes -
            Description Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            		Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            syslog
            {noformat}
            kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]
            {noformat}
            tdworak Thorsten Dworak made changes -
            Description Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            syslog
            {noformat}
            kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]
            {noformat}
            		Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            syslog
            {noformat}
            kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]
            {noformat}
            other Kernel ( linux-image-4.10.0-35-generic ) the same
            {noformat}

            {noformat}
            tdworak Thorsten Dworak made changes -
            Description Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            syslog
            {noformat}
            kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]
            {noformat}
            other Kernel ( linux-image-4.10.0-35-generic ) the same
            {noformat}

            {noformat}
            		Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            syslog
            {noformat}
            kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]
            {noformat}
            other Kernel ( linux-image-4.10.0-35-generic ) the same
            {noformat}
            kernel: [ 34.915202] mysqld[3700]: segfault at 950 ip 00005650bbc7fea8 sp 00007f4191bf9830 error 4 in mysqld[5650bb746000+f0b000]
            {noformat}
            tdworak Thorsten Dworak added a comment -

            I downgrade to V10.1.26 and the service is starting

            aptitude install mariadb-server-10.1=10.1.26+maria-1~xenial
            		 
            aptitude install mariadb-server-core-10.1=10.1.26+maria-1~xenial
            		 
            aptitude install mysql-common=10.1.26+maria-1~xenial

            tdworak Thorsten Dworak added a comment - I downgrade to V10.1.26 and the service is starting aptitude install mariadb-server- 10.1 = 10.1 . 26 +maria- 1 ~xenial aptitude install mariadb-server-core- 10.1 = 10.1 . 26 +maria- 1 ~xenial aptitude install mysql-common= 10.1 . 26 +maria- 1 ~xenial
            tdworak Thorsten Dworak made changes -
            Description Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            {code:java}
            ...
            2017-09-26 10:20:40 140472521582336 [Note] WSREP: Member 2.0 (node03.c0.db.heg.systems) synced with group.
            WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20170926 10:20:40.807)
            WSREP_SST: [INFO] Galera co-ords from recovery: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770 0 (20170926 10:20:40.809)
            WSREP_SST: [INFO] Total time on joiner: 0 seconds (20170926 10:20:40.811)
            WSREP_SST: [INFO] Removing the sst_in_progress file (20170926 10:20:40.813)
            2017-09-26 10:20:40 140474915764480 [Note] WSREP: SST complete, seqno: 327527770
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Compressed tables use zlib 1.2.8
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using Linux native AIO
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Using SSE crc32 instructions
            2017-09-26 10:20:41 140474915764480 [Note] InnoDB: Initializing buffer pool, size = 50.0G
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Completed initialization of buffer pool
            2017-09-26 10:20:42 140474915764480 [Note] InnoDB: Highest supported file format is Barracuda.
            2017-09-26 10:20:43 140472529975040 [Note] WSREP: (3f588d65, 'tcp://10.80.18.137:4567') turning message relay requesting off
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: 128 rollback segment(s) are active.
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Waiting for purge to start
            2017-09-26 10:20:43 140474915764480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 707658974520
            2017-09-26 10:20:44 140412165519104 [Note] InnoDB: Dumping buffer pool(s) not yet started
            2017-09-26 10:20:44 140474915764480 [Note] Plugin 'FEEDBACK' is disabled.
            2017-09-26 10:20:44 140474915764480 [Note] Server socket created on IP: '0.0.0.0'.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: Signalling provider to continue.
            2017-09-26 10:20:44 140474915764480 [Note] WSREP: SST received: 4aa12d31-ec51-11e6-95dc-6ab39447627b:327527770
            2017-09-26 10:20:44 140474915489536 [Note] WSREP: Receiving IST: 44651 writesets, seqnos 327527770-327572421
            2017-09-26 10:20:44 140474915764480 [Note] Reading of all Master_info entries succeded
            2017-09-26 10:20:44 140474915764480 [Note] Added new Master_info '' to hash table
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            syslog
            {noformat}
            kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]
            {noformat}
            other Kernel ( linux-image-4.10.0-35-generic ) the same
            {noformat}
            kernel: [ 34.915202] mysqld[3700]: segfault at 950 ip 00005650bbc7fea8 sp 00007f4191bf9830 error 4 in mysqld[5650bb746000+f0b000]
            {noformat}
            		Description: Ubuntu 16.04.3 LTS
            Kernel: linux-image-4.11.0-14-generic
            Repo: mariadb.org/repo/10.1/ubuntu xenial main

            mysql-error-log
            {code:java}
            ...
            2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
            Version: '10.1.27-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
            170926 10:20:44 [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.1.27-MariaDB-1~xenial
            key_buffer_size=1073741824
            read_buffer_size=2097152
            max_used_connections=0
            max_threads=4002
            thread_count=65
            It is possible that mysqld could use up to
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 K bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.

            Thread pointer: 0x0
            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 0x40000
            /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
            /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
            /usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
            /usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
            /usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
            /usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
            /usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
            /usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
            /usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
            /usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
            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.

            {code}
            syslog
            {noformat}
            kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]
            {noformat}
            other Kernel ( linux-image-4.10.0-35-generic ) the same
            {noformat}
            kernel: [ 34.915202] mysqld[3700]: segfault at 950 ip 00005650bbc7fea8 sp 00007f4191bf9830 error 4 in mysqld[5650bb746000+f0b000]
            {noformat}
            anikitin Andrii Nikitin (Inactive) made changes -
            Assignee Andrii Nikitin [ anikitin ]
            anikitin Andrii Nikitin (Inactive) added a comment -

            This is very likely duplicate of MDEV-13787 . Yes it is better to stay on 10.1.26 until fix is released or try workaround innodb_stats_persistent=0

            anikitin Andrii Nikitin (Inactive) added a comment - This is very likely duplicate of MDEV-13787 . Yes it is better to stay on 10.1.26 until fix is released or try workaround innodb_stats_persistent=0
            anikitin Andrii Nikitin (Inactive) made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            Component/s Galera [ 10124 ]
            Fix Version/s N/A [ 14700 ]
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik added a comment -

            This is probably a duplicate of MDEV-13908

            serg Sergei Golubchik added a comment - This is probably a duplicate of MDEV-13908
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Fix Version/s 10.1.28 [ 22610 ]
            Fix Version/s N/A [ 14700 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 82785 ] MariaDB v4 [ 152888 ]

            People

              anikitin Andrii Nikitin (Inactive)
              tdworak Thorsten Dworak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.