log parameter on mysqld section shouldn't be read by xtrabackup

Bug #1347698 reported by Miguel Angel Nieto on 2014-07-23
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Low
Sergei Glushchenko
2.0
Won't Fix
Undecided
Unassigned
2.1
Fix Released
Low
Sergei Glushchenko
2.2
Fix Released
Low
Sergei Glushchenko

Bug Description

Tested with 2.0.7.

If there is a "log" parameter in my.cnf, xtrabackup will read it and the backup will fail:

xtrabackup_55: ambiguous option '--log=/var/log/mysql/mysql.log' (log-copy-interval, log-stream)
innobackupex: fatal error: no 'mysqld' group in MySQL options

log is deprecated, but it can still be used, so we should support it.

Related branches

tags: added: i44059

Verified with PS 5.5.38 and Xtrabackup 2.0, 2.1 and 2.2 versions. I can able to start MySQL with --log option in my.cnf which was not possible with PS 5.6

For 2.0, getting this error.

/home/nilnandan/Downloads/percona-xtrabackup-2.0.7/bin/xtrabackup: ambiguous option '--log=/var/log/mysql/mysql.log' (log-copy-interval, log-stream)
innobackupex: fatal error: no 'mysqld' group in MySQL options
root@nilnandan-Dell-XPS:/home/nilnandan/Downloads/percona-xtrabackup-2.0.7/bin#

For 2.1 and 2.2, getting this,

Unknown suffix '/' used for variable 'log-copy-interval' (value '/var/log/mysql/mysql.log')
xtrabackup: Error while setting value '/var/log/mysql/mysql.log' to 'log-copy-interval'
innobackupex: Error: no 'mysqld' group in MySQL options at /usr/bin/innobackupex line 4397.

Alexey Kopytov (akopytov) wrote :

The workaround is to use 'general_log' instead of 'log' in my.cnf.

tags: added: i44046

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

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

Duplicates of this bug

Other bug subscribers