IMPORTANT: Please check that the backup run completes successfully.

           At the end of a successful backup run innobackupex

           prints "completed OK!".

171027 13:56:59 Connecting to MySQL server host: localhost, user: root, password: not set, port: not set, socket: /dev/shm/__var0/tmp/mysql.sock.ONIJra

Using server version 5.5.58-MariaDB

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

mariabackup: uses posix_fadvise().

mariabackup: cd to /dev/shm/__var0/var1/data/

mariabackup: open files limit requested 0, set to 1024

InnoDB: The universal page size of the database is set to 8192.

mariabackup: using the following InnoDB configuration:

mariabackup:   innodb_data_home_dir = ./

mariabackup:   innodb_data_file_path = ibdata1:10M:autoextend

mariabackup:   innodb_log_group_home_dir = ./

mariabackup:   innodb_log_files_in_group = 2

mariabackup:   innodb_log_file_size = 50331648

171027 13:56:59 >> log scanned up to (7717114)

2017-10-27 13:56:59 140589288627136 [ERROR] InnoDB: Data file "./ibdata1" uses page size 16384 ,but the start-up parameter is --innodb-page-size=8192 .

mariabackup: Could not open or create data files.

mariabackup: If you tried to add new data files, and it failed here,

mariabackup: you should now edit innodb_data_file_path in my.cnf back

mariabackup: to what it was, and remove the new ibdata files InnoDB created

mariabackup: in this failed attempt. InnoDB only wrote those files full of

mariabackup: zeros, but did not yet use them in any way. But be careful: do not

mariabackup: remove old data files which contain your precious data!

mariabackup: error: xb_load_tablespaces() failed witherror code 11