Innobackupex can't parse "set-variable" lines from my.cnf

Bug #1108709 reported by Miguel Angel Nieto
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Triaged
Low
Unassigned
2.0
Won't Fix
Low
Unassigned
2.1
Triaged
Low
Unassigned
2.2
Triaged
Low
Unassigned
2.3
Triaged
Low
Unassigned

Bug Description

If I use "set-variable = something = value" on the my.cnf, innobackup can't parse it. For example:

set-variable = innodb_log_file_size=536870912

this is the log of the backup:

InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 536870912 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
innobackupex: Error: ibbackup child process has died at /usr/bin/innobackupex line 381.

set-variable = innodb_log_file_size=536870912

to

innodb_log_file_size=536870912

it will work.

Revision history for this message
Alexey Kopytov (akopytov) wrote :

Note that the set-variable syntax is deprecated and removed in MySQL 5.5.3 according to http://dev.mysql.com/doc/refman/5.5/en//program-variables.html

But still have to support it as long as we support 5.1.

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-91

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.