innobackupex permission error; --defaults-extra-file ignored?

Bug #1511451 reported by Jeroen Pulles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
High
Sergei Glushchenko
2.3
Fix Released
High
Sergei Glushchenko

Bug Description

Upgraded percona-xtrabackup to 2.3.2-1.trusty from 2.2.12-1.trusty.

Backup now fails.

The error notice below gives the impressions that " --defaults-extra-file=/etc/mysql/debian.cnf" is ignored. That's the file where debian/ubuntu keep the maintainer authentication credentials.

innobackupex --no-timestamp --compress --defaults-extra-file=/etc/mysql/debian.cnf --defaults-group=client --incremental-basedir /mysql-backup/005 --incremental /mysql-backup/006
151029 17:13:03 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!".

151029 17:13:03 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;port=3306;mysql_socket=/var/run/mysqld/mysqld.sock' as 'mysql' (using password: NO).
Failed to connect to MySQL server: DBI connect(';mysql_read_default_group=xtrabackup;port=3306;mysql_socket=/var/run/mysqld/mysqld.sock','mysql',...) failed: Access denied for user 'mysql'@'localhost' (using password: NO) at - line 1314.
151029 17:13:03 Connecting to MySQL server host: localhost, user: mysql, password: not set, port: 3306, socket: /var/run/mysqld/mysqld.sock
Failed to connect to MySQL server: Access denied for user 'mysql'@'localhost' (using password: NO).

Revision history for this message
Jeroen Pulles (jeroen-pulles) wrote :

i'm using http://repo.percona.com/apt

I notice I can't revert to 2.2.12-1.trusty; That version seems to have been pulled from the repo.

Instead I've installed percona-xtrabackup-22, which works for me, for now...

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

The caveat when using --defaults-file or --defaults-extra-file is that you should specify them first on the command line. Xtrabackup does check for --defaults-file to be specified first, but lacks the same check for --defaults-extra-file.

Xtrabackup 2.2 passed defaults-file as 'mysql_read_default_file=...' to DBD::mysql and it was not always handled correctly. Now when we rewrote everything in cli semantic has changed and we need

1. check that --defaults-extra-file is the first option on the command line
2. document new behavior

Changed in percona-xtrabackup:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Jeroen Pulles (jeroen-pulles) wrote :

> The caveat when using --defaults-file or --defaults-extra-file is that you should specify them first on the command line.

Moved the --defaults* arguments to be the first arguments and things start working again. No authentication failures.

Thanks,
J

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.