mariabackup.xb_compressed_encrypted fails in buildbot with segmentation fault

mariabackup.xb_compressed_encrypted      w4 [ fail ]

        Test ended at 2017-12-28 10:33:40

CURRENT_TEST: mariabackup.xb_compressed_encrypted

sh: line 1: 22918 Segmentation fault      /usr/bin/mariabackup --innobackupex --apply-log /dev/shm/var/4/tmp/backup 2>&1

mysqltest: At line 28: exec of '/usr/bin/mariabackup --innobackupex --apply-log /dev/shm/var/4/tmp/backup 2>&1' failed, error: 35584, status: 139, errno: 0

Output from before failure:

171228 10:33:40 innobackupex: Starting the apply-log operation

IMPORTANT: Please check that the apply-log run completes successfully.

           At the end of a successful apply-log run innobackupex

           prints "completed OK!".

--innobackupex based on MariaDB server 10.1.30-MariaDB Linux (x86_64) 

mariabackup: cd to /dev/shm/var/4/tmp/backup/

Loading encryption plugin

	 Encryption plugin parameter :  '--file_key_management_encryption_algorithm=aes_cbc'

	 Encryption plugin parameter :  '--file_key_management_filekey='

	 Encryption plugin parameter :  '--file_key_management_filename=/usr/share/mysql-test/std_data/logkey.txt'

	 Encryption plugin parameter :  '--apply-log'

	 Encryption plugin parameter :  '/dev/shm/var/4/tmp/backup'

mariabackup: This target seems to be not prepared yet.

mariabackup: xtrabackup_logfile detected: size=3145728, start_lsn=(22784939)

mariabackup: using the following InnoDB configuration for recovery:

mariabackup:   innodb_data_home_dir = ./

mariabackup:   innodb_data_file_path = ibdata1:12M:autoextend

mariabackup:   innodb_log_group_home_dir = ./

mariabackup:   innodb_log_files_in_group = 1

mariabackup:   innodb_log_file_size = 3145728

mariabackup: using the following InnoDB configuration for recovery:

mariabackup:   innodb_data_home_dir = ./

mariabackup:   innodb_data_file_path = ibdata1:12M:autoextend

mariabackup:   innodb_log_group_home_dir = ./

mariabackup:   innodb_log_files_in_group = 1

mariabackup:   innodb_log_file_size = 3145728

mariabackup: Starting InnoDB instance for recovery.

mariabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: The InnoDB memory heap is disabled

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Compressed tables use zlib 1.2.8

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Using generic crc32 instructions

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Initializing buffer pool, size = 100.0M

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Completed initialization of buffer pool

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Highest supported file format is Barracuda.

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Starting crash recovery from checkpoint LSN=22784939

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

2017-12-28 10:33:40 140258601293696 [Note] InnoDB: Starting final batch to recover 138 pages from redo log

171228 10:33:40 [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.30-MariaDB

key_buffer_size=0

read_buffer_size=131072

max_used_connections=0

max_threads=1

thread_count=0

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5338 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 0x48400

/usr/bin/mariabackup(my_print_stacktrace+0x2b)[0x7f9080c6a46b]

addr2line: '--innobackupex': No such file

/usr/bin/mariabackup(handle_fatal_signal+0x4d5)[0x7f908082add5]

/lib64/libpthread.so.0(+0xf890)[0x7f907fd9f890]

/lib64/libcrypto.so.1.0.0(+0xed6c5)[0x7f907efab6c5]

/lib64/libcrypto.so.1.0.0(lh_delete+0x21)[0x7f907efabb51]

/lib64/libcrypto.so.1.0.0(+0xeffdf)[0x7f907efadfdf]

/lib64/libcrypto.so.1.0.0(ERR_remove_thread_state+0x2d)[0x7f907efaea2d]

/usr/bin/mariabackup(my_aes_crypt_finish+0x24)[0x7f9080c7f694]

/usr/bin/mariabackup(my_aes_crypt+0x95)[0x7f9080c7f745]

/usr/bin/mariabackup(_ZN11MyCTX_nopad6finishEPhPj+0x93)[0x7f9080c7fd13]

/usr/bin/mariabackup(my_aes_crypt_finish+0x19)[0x7f9080c7f689]

/usr/bin/mariabackup(+0x6144ed)[0x7f90807e44ed]

/usr/bin/mariabackup(_Z8do_cryptPKhjPhPjP20st_encryption_schemejjjyi+0x1ad)[0x7f90807e488d]

/usr/bin/mariabackup(encryption_scheme_decrypt+0x2b)[0x7f90807e49ab]

/usr/bin/mariabackup(+0x87a732)[0x7f9080a4a732]

/usr/bin/mariabackup(+0x87a8eb)[0x7f9080a4a8eb]

/usr/bin/mariabackup(+0x820685)[0x7f90809f0685]

/usr/bin/mariabackup(+0x86b6ac)[0x7f9080a3b6ac]

/usr/bin/mariabackup(+0x999860)[0x7f9080b69860]

/lib64/libpthread.so.0(+0x80a4)[0x7f907fd980a4]

/lib64/libc.so.6(clone+0x6d)[0x7f907e1c57fd]

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.

The result from queries just before the failure was:

< snip >

BEGIN

DECLARE CURRENT_NUM INT;

SET CURRENT_NUM = 0;

WHILE CURRENT_NUM < REPEAT_COUNT DO

INSERT INTO t1 VALUES(CURRENT_NUM, concat(uuid(), CURRENT_NUM, repeat('ab', floor(rand()*100) ), uuid()));

SET CURRENT_NUM = CURRENT_NUM + 1;

END WHILE;

END//

COMMIT;

SET AUTOCOMMIT=0;

CALL innodb_insert_proc(50000);

COMMIT;

# xtrabackup backup

drop table t1;