'open' returned OS error 71. Cannot continue operation

[lin]

# innobackupex --host="192.168.1.102" --port="3306" --user=root --password=123456 /backups
170301 03:07:26 innobackupex: Starting the backup operation

IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".

170301 03:07:26 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;host=192.168.1.102;port=3306;mysql_socket=/var/run/mysqld/mysqld.sock' as 'root' (using password: YES).
170301 03:07:31 version_check Connected to MySQL server
170301 03:07:31 version_check Executing a version check against the server...
170301 03:07:31 version_check Done.
170301 03:07:31 Connecting to MySQL server host: 192.168.1.102, user: root, password: set, port: 3306, socket: /var/run/mysqld/mysqld.sock
Using server version 10.1.11-MariaDB-log
innobackupex version 2.4.3 based on MySQL server 5.7.11 Linux (x86_64) (revision id: 6a46905)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: open files limit requested 0, set to 524288
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = .
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
InnoDB: Number of pools: 1
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: File ./ib_logfile0: 'open' returned OS error 71. Cannot continue operation
InnoDB: Cannot continue operation.

[Shahriyar Rzayev (rzayev-sehriyar)]

Hi,
Could you please share your configuration file -> my.cnf?

[lin (kuangtiefeng)]

[mysqld]
user = root
datadir = /var/lib/mysql
port = 3306
log-bin = /var/lib/mysql/mysql-bin

[Shahriyar Rzayev (rzayev-sehriyar)]

Could not reproduce with 2.4.6 version of XB with MariaDB 10.1.21.
Is it possible to upgrade to a newer version and to test if the problem still there?

[luojia (luojia)]

innobackupex version 2.4.7 Linux (x86_64)
i had the same problem：
InnoDB: Apply batch completed
InnoDB: xtrabackup: Last MySQL binlog file position 543213675, file name mysql-bin.059329
InnoDB: Creating shared tablespace for temporary tables
InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
InnoDB: File './ibtmp1' size is now 12 MB.
InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active.
InnoDB: 32 non-redo rollback segment(s) are active.
InnoDB: 5.7.13 started; log sequence number 104048846759038
InnoDB: page_cleaner: 1000ms intended loop took 189568030ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
InnoDB: xtrabackup: Last MySQL binlog file position 543213675, file name mysql-bin.059329

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: File ./database/table.ibd: 'open' returned OS error 71. Cannot continue operation
InnoDB: Cannot continue operation.
InnoDB: 10 threads created by InnoDB had not exited at shutdown!

[Sergei Glushchenko (sergei.glushchenko)]

Can you share some more details? Which server version is it? What command looks like? In original bug report problem occurred during the backup, while yours seems to occur during prepare, so it looks different to me.

[Launchpad Janitor (janitor)]

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1429